Server response projection: 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 return path and mapping contract to distinguish selected fields, a whole record or no result. A broad return shape alone does not establish which data is sensitive.
Projection is a structural result: the output fields are explicitly chosen. It does not establish whether every selected field is appropriate for every caller.
Whole can be useful to flag for review without inventing a leak. The actual sensitivity of returned fields depends on the record shape and access policy, which must be supplied separately.
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 server response projection.

Review the return path and mapping contract to distinguish selected fields, a whole record or no result.

Open the decision rules and keep the intended distinction between Projection, Whole, Noresult, 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 |
|---|---|---|
| Small response | Projection | 100% |
| Entire updated row | Whole | 97.0% |
| Database selection | Projection | 100% |
| No payload | Noresult | 99.0% |
| Unknown mapper | Unclear | 85.0% |
| Whole public row | Whole | 70.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. One preset deliberately returns a wholly public record. The label describes the projection boundary, not an incident.
Only when its mapping contract or implementation is provided. A descriptive helper name is insufficient evidence.
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.