Jev write field allowlist

Check which client fields can reach a database write

Show the write path and editable-field policy. Distinguish explicit selection or known stripping schemas from broad client-field passthrough, preserving unknown behavior before a non-admin write.

write field allowlistLive API
Try an example

The write explicitly selects the sole editable field.

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.

For this non-admin write and supplied editable-field policy: Allowlisted if only permitted fields reach persistence through explicit selection or a known stripping/rejecting schema; Broad if arbitrary client fields pass through, including via casts or passthrough schemas; NoWrite if the payload never reaches persistence.

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

Shape validation and permission to edit a field answer different questions. A valid role string can still be a field this caller is not allowed to change.

The scope is a non-admin endpoint with an explicit policy. It does not judge privileged administrative tools, migrations or client-side form state as though they were public profile updates.

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 editable-field allowlists.

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

    Add the information to check

    Show the write path and editable-field policy.

  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 Allowlisted, Broad, NoWrite, 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
Pick display nameAllowlisted91.0%
Forward the bodyBroad98.0%
A cast onlyBroad89.0%
Strict parsed resultAllowlisted99.0%
Passthrough schemaBroad100%
Policy not suppliedUnclear58.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

Editable-field allowlists: 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 update payloads
  • Checking schema passthrough behavior
  • Separating typing from runtime field selection

Outside this demonstration

  • Proving a deployed exploit
  • Defining who may edit protected fields
  • Reviewing unspecified admin policies
Example FAQ

Using this example

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

Does schema parsing always create an allowlist?

No. Supply its unknown-key behavior and permitted fields. A passthrough schema can validate listed fields while retaining additional ones.

Is Allowlisted a full authorization result?

No. Authentication, object access and field values still need their own checks. This page only follows fields into a write.

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.