Route identity
A stable route ID and a unique version ID distinguish the route from every other proposal.
Module 06 · Commit and Version History
Fix the route before consequence.
A governance route is not ready merely because its parts were reviewed. The exact admissible version must be committed so execution can be compared against one stable, deterministic object.
A correction creates a new version. It does not rewrite the route that existed before the correction.
Commit anatomy
What becomes fixed
The commit is the boundary between an evaluated proposal and an execution candidate. Every material element needed to reproduce the decision must be captured.
Canonical payload
The exact execution object is normalized so the same route always produces the same digest.
Evidence set
The admissible records, receipts, and provenance references are fixed to the committed version.
Authority state
The applicable authority, limits, approvals, and temporal validity are captured at commit time.
Decision receipt
The ALLOW, HOLD, DENY, or ESCALATE determination is preserved with its reasons.
Cryptographic digest
A deterministic fingerprint makes any post-commit alteration detectable.
Interactive lab
Change a committed route
Create a material destination change and observe why the earlier commit cannot be silently edited or reused.
Selected version
V2 · committed
Corrected destination, revalidated evidence, and committed as the execution candidate.
Amount$48,750
DestinationAccount ending 2916
AuthorityP-17 dual approval
Digestsha256:b2e8…91af
The digest corresponds to this exact version. Any material alteration changes the canonical payload and therefore requires a new digest, decision receipt, and commit.
Preserved sequence
History remains visible
A trustworthy route explains not only what executed, but how the route arrived at that state.
Version 1
Original proposal preserved
The first destination mismatch remains visible as historical truth rather than being erased by correction.
Version 2
Corrected and committed
The verified destination receives its own digest and decision receipt.
Version 3
Material change requires renewed governance
A new destination cannot inherit the prior version’s authority, admissibility, or execution permission.
Knowledge check
Prove the distinction
Select one answer for each question, then score the lesson.
1. What does a commit establish?
2. A committed route needs a destination change. What is the correct action?
3. Why preserve superseded versions?
Complete all three questions.
Next module
Execution must correspond to the commit.
The next lesson moves from the immutable execution candidate to the live act itself: proving that what the system did is the same thing the route authorized.