Execution Chains
How chained receipts become continuity, portable bundles, and a verifiable order of operations.
How do chained receipts become a continuity story, and what should I verify before treating a bundle as a complete operational record?
An execution chain is the continuity layer across multiple receipts. A receipt says one governed event was issued. A chain lets a reviewer test whether the presented event history is ordered and intact.
1. Problem this page solves
Single receipts are useful, but they are not enough for sequence review.
Reviewers usually need continuity answers:
- did prerequisite events appear before high-impact actions?
- does the presented history have link breaks or missing segments?
- were receipts reordered or modified after issuance?
This page explains exactly what chain evidence can establish for those questions.
2. Reader outcome
After this page, you should be able to:
- identify the fields that create chain continuity
- run concrete continuity checks such as link, order, and integrity
- separate chain-backed conclusions from interpretation and assumptions
3. Mechanism-first chain model
Chain continuity comes from receipt fields, not from narrative summaries.
Event linking
Each receipt carries continuity fields in its ledger block:
ledger.stream→ which stream or lane the receipt belongs toledger.seq→ sequence position inside that streamledger.prev_hash→ declared hash of the prior receipt in that streamledger.entry_hash→ hash of this receipt's canonical bytes
At minimum, a verifier checks that prev_hash in receipt N matches entry_hash in the predecessor receipt for the same stream.
Ordering
Ordering is checked per stream, not across unrelated streams.
A verifier groups receipts by ledger.stream, sorts by ledger.seq, and checks for unexpected gaps, duplicates, or predecessor mismatches. If boundaries are declared, such as the first or last sequence in a bundle, those boundaries must match what is presented.
Integrity continuity
Integrity continuity is the combined result of:
- recomputing
entry_hashand matching each receipt's declared value - confirming
prev_hashlinks match predecessorentry_hashvalues - confirming sequence order checks pass for the claimed stream segment
If any of those fail, continuity is broken for that segment.
4. What chain evidence can support vs what it cannot prove
| Chain evidence can support | Chain evidence cannot prove |
|---|---|
| Receipt A is linked as predecessor of Receipt B in the presented stream | The underlying real-world action definitely happened as described |
| The presented sequence has no detected reorder or modify break under the checked rules | No events were omitted outside the declared stream boundary |
| A declared stream segment is internally consistent | Operator judgment or approval quality was correct |
| A bundle's chain material matches its own declared continuity links | Host integrity, tool correctness, or organizational policy quality |
Chain evidence is continuity evidence. It is not a substitute for full incident truth.
5. Observed vs inferred separation
| Layer | What it contains | Confidence boundary |
|---|---|---|
| Observed (directly checkable) | Hash recomputation results, prev_hash link matches, seq ordering outcomes, declared stream boundaries | Determined by verifier checks over presented artifacts |
| Inferred (interpretive) | "Approval preceded execution, so policy was likely followed" | Depends on human interpretation of observed order |
| Outside chain proof | Event correctness, target appropriateness, source-system reliability | Requires additional evidence and trust inputs |
Keep these layers separate in reports so continuity checks are not overstated.
6. Trust assumptions and limits
Chain verification still depends on explicit assumptions:
- canonicalization and hashing rules are implemented consistently
- issuance keys and signing controls were not subverted at issue time
- stream identity and scope boundaries are declared honestly
- the verifier received the full artifact set for the claimed chain segment
- timestamp and trusted-time guarantees come from timestamp evidence, not chain order alone
When an assumption is uncertain, report reduced confidence instead of upgrading claims.
7. Next-page handoff
Next, read Sensitive Artifact Handling to apply stricter controls to raw credentials, tokens, and other high-risk artifacts that may accompany chain evidence.