Jev menu preference match

Compare a dish description with a taste preference

Provide a taste preference and fictional dish notes. Compare a match, a conflict and a mixed fit based on stated flavors, without treating the result as nutrition or allergy advice.

Does this fictional dish fit the requested taste?Live API
Try an example

Original input for the Taste match outcome. Edit the evidence to send a new request.

Source: Background discussion on X

Source and example scope

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.

Compare stated taste preference and dish notes.

Decision rules and labels
Taste matchTaste conflictMixed fitUnclear flavorNeed evidence
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

Match the preference that the diner actually states.

The window evaluates taste language, not dietary suitability. A savory dish with a sweet glaze can partly fit a request while violating another stated preference, so Mixed fit preserves both facts.

The citrus example uses different words for a compatible flavor. The house-special example supplies a description that says nothing useful about taste; it cannot establish a match.

These dishes are fictional. The source describes menu matching, but this adaptation does not reproduce a restaurant menu, confirm ingredients, make health recommendations or place an order.

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.

Illustration of one spreadsheet row producing two separate classification results
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for menu taste matching.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Provide a taste preference and fictional dish notes.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Taste match, Taste conflict, Mixed fit, Unclear flavor, Need evidence. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

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

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Unclear flavor, Need evidence before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Mild requestedTaste match100%
Hot dish conflictTaste conflict100%
Mixed flavorMixed fit100%
Flavor not describedUnclear flavor52.0%
Different words, same fitTaste match100%
No preferenceNeed evidence100%

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

Understand the results

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.

Using the result in your application

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.

Runnable offline example

Run one sample, then inspect the local packet

View the code example
Single-request replay
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.json
Scope of this demo

Where this decision fits

Useful scope

  • Exploring semantic flavor matching in a fictional menu
  • Keeping conflicting taste preferences visible
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Checking allergies or medical dietary requirements
  • Ordering a dish or certifying its ingredients
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about menu preference match.

The rubric explains the decision; the application owns the next step.

Does Taste match mean a dish is allergy-safe?

No. Flavor descriptions do not establish allergen content or preparation conditions. This demonstration does not evaluate those properties.

Does this rank an entire menu?

No. It judges one dish against one stated preference. Comparing several candidates requires their descriptions and a separate ranking objective.

Does the leading probability measure production accuracy?

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.

What happens when the API fails?

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.

Try your own menu preference match input

Edit the evidence above or use the Playground to test another bounded question.