What is Run Binding?

Run Binding refers to linking a specific AI run to a defined, fixed data state. It is the connection that makes each execution explainable in terms of the data conditions it ran under.

When a run finishes, only the answer remains. Which schema, which field definitions, which applied policy produced it disappears unless it is bound at the time. What an audit asks for is not the result but the conditions behind it, and without that link the result cannot be defended.

This differs in purpose from experiment tracking. Experiment tracking records hyperparameters and metrics so training runs can be compared. Run binding ties a production execution to a data state so it can be returned to under the same conditions. A bound run can be re-run on the same saved data state, and if the data has changed since, a comparison shows what changed. In Syntitan, this is handled as a run record: each run records the data version, settings and evaluation conditions it used, so you can re-run on the saved version and compare it with the previous version.

Frequently asked questions

What is run binding?

Linking a specific AI run to a defined, fixed data state, so each execution can be explained in terms of the data conditions it ran under.

How is run binding different from experiment tracking?

Experiment tracking records hyperparameters and metrics to compare training runs. Run binding ties a production execution to a data state so it can be returned to later. Different purposes.

Why bind every run?

When a run ends, only the answer remains. The schema, field definitions and policy behind it disappear unless bound at the time. An audit asks for those conditions.

What does run binding make possible?

Re-running a past execution under the same data conditions to check the result, and narrowing down data-state differences by comparing versions when two runs disagree.