Build input dependencies: six recorded examples
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
Describe the build action and declared inputs. Compare source and tool dependencies with output-affecting host files, network data, environment, time or randomness.
A build dependency can be hidden even when the command succeeds locally. A host file, live response or clock value may change the artifact without appearing among its declared inputs.
Diagnostic output is a separate case. A timestamp printed only for a human is not automatically an artifact dependency; the input must establish that it does not feed another action.
The source linter includes a nonhermetic-build rule. This review identifies the described dependency boundary. It neither executes the action nor demonstrates byte-for-byte reproducibility.
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 build input dependencies.

Describe the build action and declared inputs.

Open the decision rules and keep the intended distinction between Declared inputs, Hidden dependency, No output dependency, 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 |
|---|---|---|
| Declared source and tool | Declared inputs | 98.0% |
| Host configuration file | Hidden dependency | 99.0% |
| Live network lookup | Hidden dependency | 99.0% |
| Build-time timestamp | Hidden dependency | 100% |
| Diagnostic timestamp only | No output dependency | 97.0% |
| Unknown helper reads | Review | 78.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. It describes the supplied dependency contract. Tool behavior, environment enforcement and actual build comparisons need separate verification.
Only when it affects the artifact or downstream actions. A diagnostic-only timestamp is explicitly distinguished here.
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.