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.
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.
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.

Use the sample to understand the rule, then test your own input for expected-value independence.

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

Open the decision rules and keep the intended distinction between Copied, Independent, Unclear. 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 Unclear before using a result. The label is a decision about the supplied information, not an executed action.
| Original input | Observed label | Leading probability |
|---|---|---|
| Same formula | Copied | 100% |
| Worked fixture | Independent | 84.0% |
| Two different algorithms | Independent | 100% |
| Same transformation | Copied | 98.0% |
| Property check | Independent | 97.0% |
| Unknown expected helper | Unclear | 58.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
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
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.
# 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.The input contract and these limits define what the result means.
Not when the reference is independently defined. Supply both algorithms or their relevant contracts; a second function name alone does not show independence.
Yes. Ordering alone does not prove that a sort preserved every item. This page classifies the oracle’s origin, not its completeness.
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.
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.
Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.