Runtime data validation: six recorded examples
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
Show how an external value reaches domain code and what validates it. Distinguish a runtime check from a TypeScript cast or a helper whose behavior is unknown.
Static types and runtime checks answer different questions. Data from a network, storage or message boundary can violate a declared interface even when the program compiles. The check must occur before the value is used.
Validated describes the shown validation contract. It does not establish field-edit permissions, authentication or overall application safety. A shape-valid role field may still be forbidden in a user update.
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 runtime data validation.

Show how an external value reaches domain code and what validates it.

Open the decision rules and keep the intended distinction between Validated, Asserted, 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 |
|---|---|---|
| Cast after JSON parse | Asserted | 100% |
| Schema before use | Validated | 100% |
| Typed fetch response | Asserted | 99.0% |
| Known validated client | Validated | 91.0% |
| Unknown parser | Unclear | 99.0% |
| Check occurs too late | Asserted | 99.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.
Yes, if its runtime behavior is documented or shown. A generated TypeScript type alone is not a runtime check.
No. Data shape and field-write permission require separate policies.
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.