Jev external data validation

Check whether external data is validated before use

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.

external data validationLive API
Try an example

A type assertion does not validate parsed bytes.

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.

Inspect the external-data path: Validated if an explicit runtime check or documented validating wrapper checks the value before domain use; Asserted if a type cast or declared type is the only shown assurance; Unclear if validator behavior or ordering is missing.

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

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.

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 runtime data validation.

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

    Add the information to check

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

  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 Validated, Asserted, 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
Cast after JSON parseAsserted100%
Schema before useValidated100%
Typed fetch responseAsserted99.0%
Known validated clientValidated91.0%
Unknown parserUnclear99.0%
Check occurs too lateAsserted99.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

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.

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 JSON boundaries
  • Distinguishing casts from schema checks
  • Tracing documented validating wrappers

Outside this demonstration

  • Certifying security
  • Executing malformed payloads
  • Treating shape validation as authorization
Example FAQ

Using this example

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

Can a generated client validate for me?

Yes, if its runtime behavior is documented or shown. A generated TypeScript type alone is not a runtime check.

Does Validated mean every field may be stored?

No. Data shape and field-write permission require separate policies.

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.