Jev hermetic build input review

Review the dependencies that can change a build's output

Describe the build action and declared inputs. Compare source and tool dependencies with output-affecting host files, network data, environment, time or randomness.

hermetic build input reviewLive API
Try an example

The output path accounts for all dependencies.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

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.

Review build-output dependencies.

Decision rules and labels
Declared inputsHidden dependencyNo output dependencyReview
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

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.

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 build input dependencies.

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

    Add the information to check

    Describe the build action and declared inputs.

  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 Declared inputs, Hidden dependency, No output dependency, Review. 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 Review 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
Declared source and toolDeclared inputs98.0%
Host configuration fileHidden dependency99.0%
Live network lookupHidden dependency99.0%
Build-time timestampHidden dependency100%
Diagnostic timestamp onlyNo output dependency97.0%
Unknown helper readsReview78.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

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.

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 a code generator's declared inputs.
  • Finding host-specific or live-network values embedded in artifacts.
  • Distinguishing diagnostic data from artifact-affecting data.

Outside this demonstration

  • Claiming two builds produce identical bytes without building them.
  • Inferring every dependency from a shell command name alone.
Example FAQ

Using this example

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

Does Declared inputs prove reproducibility?

No. It describes the supplied dependency contract. Tool behavior, environment enforcement and actual build comparisons need separate verification.

Is every use of time a hidden build input?

Only when it affects the artifact or downstream actions. A diagnostic-only timestamp is explicitly distinguished here.

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.