Jev response constraint coverage

Check a draft against its required and forbidden content

Compare the draft with an explicit brief. Identify missing requirements or prohibited content, giving forbidden material priority rather than assuming a fluent answer follows the instructions.

Does the draft satisfy the stated brief?Live API
Try an example

Original input for the Requirements covered 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 draft with required and forbidden brief content.

Decision rules and labels
Requirements coveredRequirement missingForbidden contentUnclear coverageNeed 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

Check an explicit brief without grading every writing quality.

The required points and forbidden content define this review. A draft can cover both requested facts and still violate the price-claim restriction. Forbidden content takes precedence under the stated rubric.

An additional permitted detail does not automatically fail the draft. The rule checks declared requirements and restrictions rather than demanding an exact sentence match or a particular style.

The source discusses evaluation of model output. This small adaptation does not reproduce its benchmark or measure factual accuracy; supplied brief coverage is a narrower, inspectable task.

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 selecting a caption token for emphasis in an edit timeline
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 draft requirement coverage.

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

    Add the information to check

    Compare the draft with an explicit brief.

  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 Requirements covered, Requirement missing, Forbidden content, Unclear coverage, 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 Requirement missing, Unclear coverage, 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
Both required pointsRequirements covered95.0%
One point missingRequirement missing56.6%
Prohibited price claimNeed evidence66.0%
Unclear referenceRequirement missing95.0%
Extra allowed detailRequirements covered74.0%
No writing briefNeed 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. 4 of 6 results matched the authored fixture expectations. For Prohibited price claim, the expectation was Forbidden content; the observed choice was Need evidence. For Unclear reference, the expectation was Unclear coverage; the observed choice was Requirement missing.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

  • Checking explicit content requirements before editing
  • Keeping forbidden claims visible beside otherwise complete copy
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Verifying facts against absent sources
  • Treating brief coverage as publication approval
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about response constraint coverage.

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

Does Requirements covered mean the draft is true?

No. It means the draft meets the supplied content brief. Verifying facts requires their sources and a different judgment.

Why does Forbidden content take precedence?

The authored rule explicitly says a prohibited element fails this check even when the required points are present. Keep that priority in the question when editing the example.

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 response constraint coverage input

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