Example context 1
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
Show how the external name becomes the final opened path, including link and race controls. Compare enforced containment with a shown gap or unresolved path semantics.
Path containment is about the file ultimately opened, not simply the string that passed an earlier check. The input must explain normalization, links and the relationship between validation and the final operation.
A fixed mapping from safe identifiers to internal filenames can establish a different boundary from accepting arbitrary paths. The examples keep these contracts explicit rather than teaching an attack payload.
This exercise adapts a path-traversal review rule from the linked linter. It does not inspect a real filesystem, extract an archive or prove that production path handling is secure.
This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Use the sample to understand the rule, then test your own input for file path containment.

Show how the external name becomes the final opened path, including link and race controls.

Open the decision rules and keep the intended distinction between Contained, Gap shown, No external path, Review. 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 Review before using a result. The label is a decision about the supplied information, not an executed action.
| Original input | Observed label | Leading probability |
|---|---|---|
| Unbounded concatenation | Gap shown | 93.0% |
| Strict safe-name mapping | Contained | 62.0% |
| Final resolved containment | Contained | 79.0% |
| Fixed internal file | No external path | 89.0% |
| String-prefix check | Review | 86.0% |
| Unknown helper | Review | 95.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.
The string check alone does not describe the final filesystem operation. Normalization, directory separators, links and race behavior may matter.
No. The demo classifies a supplied description. It performs no filesystem operation on the named path.
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.