Deterministic Release Convergence
A release state in which the implementation has verifiably converged to governed operational intent, and the convergence is reproducible from the corpus record.
Definition
Deterministic release convergence is a release state in which two conditions are simultaneously true:
- The release implementation has verifiably converged to the governed operational intent documented in the corpus
- This convergence can be independently reproduced — given the same corpus state and the same validation parameters, the convergence check produces the same result
The second condition is what makes convergence deterministic. A convergence check that produces different results on different runs — or that cannot be reproduced independently — is not a governance artifact; it is a snapshot.
Why Both Conditions Matter
Release convergence confirms that a system’s current state matches governed intent. This is valuable but not sufficient for a governance record.
Deterministic release convergence adds the reproducibility requirement. The convergence check must be: reproducible by any engineer from the same corpus, auditable after the fact, and verifiable independently of the original checker. This is the difference between a spot check and a governance record.
Operational Example
An engineer runs yanzi certify against release candidate v2.9.1. The certification produces a convergence validation result: all 12 governance gates passed, corpus hash 8e3b1f42a.
A second engineer, auditing the release two weeks later, runs the same certification command against the preserved corpus state. They get the same result: 12 gates passed, same corpus hash. The convergence is reproducible — therefore deterministic.
If the corpus had been modified (non-append-only), the second run would produce a different result. The determinism of the convergence depends on the determinism of the corpus — which is guaranteed by append-only provenance.
In Yanzi
Deterministic release convergence was the primary engineering goal of the v2.9.1 release certification cycle. The certification trace for that release demonstrates a full convergence validation that is independently reproducible from the preserved corpus state.