Payload
The canonical instruction executed must match the committed payload digest.
Module 07 · Execution Correspondence
The action must match the route.
An admitted and committed route does not authorize a vaguely similar action. Execution correspondence proves that the consequence actually released was the same consequence the evidence, authority, bindings, and commit allowed.
A valid decision cannot legitimize a different execution.
The correspondence surface
What must survive into execution
Each dimension is independently material. A route can preserve four or five of them and still fail because the released consequence no longer corresponds to the committed route.
Actor
The identity performing the action must be the identity authorized and bound to the route.
Object
The account, model, file, device, person, or other target must be the committed object.
Limits
Amount, quantity, scope, duration, and other consequence limits must remain unchanged.
Environment
Execution must occur in the approved system, tenant, region, device, or operational context.
Time
The action must occur while authority, evidence, and route validity remain temporally admissible.
Interactive lab
Catch the substituted consequence
The route was validly admitted and committed. Compare the committed execution object to what the execution service is about to release.
Execution payload
The executed instruction must be the same canonical object that was admitted and committed.
CommittedPAY-VENDOR-042ObservedPAY-VENDOR-042
Destination binding
A substituted destination creates a different route, even when the supplier name appears unchanged.
CommittedAccount ending 2916ObservedAccount ending 7340
Consequence amount
The consequence must remain within the exact amount and limits authorized at commit.
Committed$48,750.00Observed$48,750.00
Execution environment
The action must occur inside the environment that was evaluated and bound to the route.
CommittedTreasury production / us-east-1ObservedTreasury production / us-east-1
Executing actor
The executing identity must correspond to the authority and service identity preserved at commit.
CommittedTreasury service identity TS-04ObservedTreasury service identity TS-04
Controlled execution sequence
From commit to consequence
Retrieve the exact committed route, canonical payload, bindings, authority state, and decision receipt.
Capture the actor, target, amount, environment, timing, and instruction presented at the execution boundary.
Deterministically compare every material execution dimension against the committed route.
ALLOW only exact correspondence. HOLD, DENY, or ESCALATE when the observed consequence differs.
Create an execution or mismatch receipt so later verification can prove what was committed, attempted, and released.
Knowledge check
Can you govern correspondence?
1. What is execution correspondence?
2. A payment is admitted for one account but sent to another account owned by the same supplier. What happened?
3. What should the system do when correspondence fails before consequence is released?
Answer all three questions.
A perfect score confirms the core execution-correspondence concepts.
Module 08 preview
Execution is not the end of the chain.
The next lesson follows the released action into outcome correspondence, preserved receipts, independent verification, and replay. A legitimate route must prove not only what was authorized and executed, but what consequence actually occurred.