Source and example scope
Compare each saved result with its authored expectation. A disagreement remains in the fixture review; the call is not repeated to obtain a preferred label.
Compare the prospect's stated hosting requirements with the fictional product's scope. Distinguish a supported deployment, a conflict and an unresolved requirement before a sales follow-up.
The optional-self-hosting fixture distinguishes a preference from a mandatory deployment constraint. A product can fit the stated requirement even when it does not satisfy every nice-to-have.
This decision is narrower than lead qualification. It does not assess budget, timing, personal characteristics or buying readiness. It compares one stated hosting requirement with one supplied product scope.
The latest source names matching sales calls to supported use cases. These fictional transcripts expose a deployment-fit adaptation without claiming to reproduce its call dataset or predict a sale.
These fictional inputs and decision rules were written for this page. The linked X discussion provides background; the technical implementation follows TypeSafe's Choice contract.

Use the sample to understand the rule, then test your own input for deployment requirement fit.

Compare the prospect's stated hosting requirements with the fictional product's scope.

Open the decision rules and keep the intended distinction between Deployment fit, Deployment conflict, Requirement unresolved, No deployment requirement, Need evidence. Edit the choices only when testing your own rule.

Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

Review Need evidence before using a result. The label is a decision about the supplied information, not an executed action.
| Original input | Observed label | Leading probability |
|---|---|---|
| Hosted service acceptable | Deployment fit | 100% |
| Self-hosting required | Deployment conflict | 100% |
| Requirement unresolved | Requirement unresolved | 100% |
| No hosting arrangement | No deployment requirement | 97.0% |
| Preference is not a requirement | Deployment fit | 99.0% |
| Product scope absent | Need evidence | 96.0% |
These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified
Compare each saved result with its authored expectation. A disagreement remains in the fixture review; the call is not repeated to obtain a preferred label.
The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json case-1
python preview_choice_workflow.py samples.json saved-api-results.jsonThe rubric explains the decision; the application owns the next step.
No. It only checks the hosting requirement against product scope. Budget, timing, authority and other requirements are not evaluated here.
Preserve that wording. Under this rubric, an accepted hosted service can satisfy the stated requirement even when self-hosting would be a preference.
No. It is the model distribution for this one request. The six examples are functional checks with authored expectations, not a representative benchmark. Inspect disagreements and evaluate your own examples before using the label.
The window shows an error and supplies no fresh judgment. The downloadable runner sends one request without retries. Need evidence is a valid outcome about incomplete input; it does not stand in for a network or provider failure.
Edit the evidence above or use the Playground to test another bounded question.