Jev search query candidate

Choose a search query that preserves the full request

Compare three supplied query strings with the user's request and separate control parameters. Select a faithful candidate or no match without generating new terms or searching the web.

search query candidateLive API
Try an example

The subject and report format remain; only the date requirement is preserved separately.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This original text demonstration adapts a decision in a repository linked by the cited X post. The examples and explicit uncertainty outcomes are ours. The post is a directory reference, not proof that its author built every linked project. No third-party benchmark, business outcome or external action is reproduced.

Select candidate A, B or C that preserves the user’s full search subject and relationships while omitting only control requirements explicitly handled by separate parameters.

Decision rules and labels
ABCNone
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

What the decision checks

This is selection from code-supplied candidates, not query generation. The model cannot repair a bad candidate by adding missing words; None is necessary when all available strings lose part of the request.

Parameter separation also needs evidence. A phrase such as this week can leave the query only if another input says the freshness constraint is already handled. Removing it without that context changes the user’s request.

This original text demonstration adapts a decision in a repository linked by the cited X post. The examples and explicit uncertainty outcomes are ours. The post is a directory reference, not proof that its author built every linked project. No third-party benchmark, business outcome or external action is reproduced.

Illustration of matching a question to supplied passages and identifying missing evidence
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 search query fidelity.

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

    Add the information to check

    Compare three supplied query strings with the user's request and separate control parameters.

  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 A, B, C, None. 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 uncertain or unexpected results 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
Filter already handledB99.0%
Keep a relationshipA100%
Preserve a yearC54.0%
Source filter handledA99.0%
Every option drops detailNone76.0%
Missing goalNone100%

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

Search query fidelity: six recorded examples

The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.

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.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json

# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.
Scope of this demo

Where this decision fits

Useful scope

  • Comparing bounded query candidates
  • Testing which requirements belong in separate parameters
  • Detecting loss of topic relationships

Outside this demonstration

  • Generating new query text
  • Measuring search volume or rankings
  • Running a web search
Example FAQ

Using this example

The input contract and these limits define what the result means.

Can Jev improve a candidate by rewriting it?

Not in this Choice request. It returns an offered label. Generate another candidate in code or a separate writing step, then review it.

Why not always pick the shortest query?

The shortest string may remove the actual subject or relationship. Fidelity to the user’s request is the selection rule.

Does the leading probability measure accuracy?

It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.

Will a result change an external system?

No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.