Jev test expected value origin

Check where a test's expected value comes from

Review the subject calculation and how the expected value was obtained. Separate copied logic from an independent fixture, derivation or invariant, preserving missing provenance rather than assuming independence.

test expected value originLive API
Try an example

The expected expression repeats the same reduction.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This original code-reading exercise adapts a rule in the jev-lint repository linked by the cited X post. Snippets, labels and missing-context handling are authored for this page. It does not execute code, reproduce a repository scan or certify an application as safe.

Classify the expected-value origin: Independent for hand-worked literals, golden fixtures, stated independent algorithms or invariant checks; Copied if expected repeats the shown subject calculation on the same inputs.

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

An expected value needs an origin. Repeating the same formula may reproduce the same defect, while a worked fixture or a separately defined algorithm provides a different comparison.

Independent does not mean infallible. The fixture can be mistaken, an invariant can be incomplete, and a reference implementation needs its own review. This demo identifies the relationship shown in the input.

This original code-reading exercise adapts a rule in the jev-lint repository linked by the cited X post. Snippets, labels and missing-context handling are authored for this page. It does not execute code, reproduce a repository scan or certify an application as safe.

Illustration of checking a code change and reviewing a flagged line
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 expected-value independence.

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

    Add the information to check

    Review the subject calculation and how the expected value was obtained.

  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 Copied, Independent, Unclear. 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 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
Same formulaCopied100%
Worked fixtureIndependent84.0%
Two different algorithmsIndependent100%
Same transformationCopied98.0%
Property checkIndependent97.0%
Unknown expected helperUnclear58.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

Understand the results

Expected-value independence: 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

  • Reviewing generated expected values
  • Distinguishing reference tests from copied logic
  • Documenting oracle provenance

Outside this demonstration

  • Proving the oracle is correct
  • Executing or mutating tests
  • Inferring unseen formulas
Example FAQ

Using this example

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

Are differential tests considered copied logic?

Not when the reference is independently defined. Supply both algorithms or their relevant contracts; a second function name alone does not show independence.

Can a property assertion miss bugs?

Yes. Ordering alone does not prove that a sort preserved every item. This page classifies the oracle’s origin, not its completeness.

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.