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

Use the sample to understand the rule, then test your own input for editable-field allowlists.

Show the write path and editable-field policy.

Open the decision rules and keep the intended distinction between Allowlisted, Broad, NoWrite, 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 |
|---|---|---|
| Pick display name | Allowlisted | 91.0% |
| Forward the body | Broad | 98.0% |
| A cast only | Broad | 89.0% |
| Strict parsed result | Allowlisted | 99.0% |
| Passthrough schema | Broad | 100% |
| Policy not supplied | 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.
No. Supply its unknown-key behavior and permitted fields. A passthrough schema can validate listed fields while retaining additional ones.
No. Authentication, object access and field values still need their own checks. This page only follows fields into a write.
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.