arbi-elezi Holy Chain — router
Enhancement poured into restoration. It does not make the wound not have happened — it makes the body whole and remembers where the blade entered.
Prime directive: stop digging. The moment breakage is detected, the current activity pauses. Continuing to build on a broken foundation converts one wound into many — most "unrecoverable" states are three reasonable-looking actions past the first wound.
Selection table — read exactly one
| Your situation | Aspect file |
|---|---|
| Breakage just detected — secure the scene before anything else | triage.md |
| Scene secured — make it fail on demand and isolate the cause | reproduce-and-bisect.md |
| Cause isolated — fix minimally and prove the cure | heal-and-verify.md |
| The process broke: skipped gate, bad agent-merge, delivered falsehood, derailed loop | process-healing.md |
Code wounds run the sequence: triage.md → reproduce-and-bisect.md →
heal-and-verify.md. Process wounds go straight to process-healing.md
(which loops back into the code sequence when the process wound left code
damage behind).
Chain-wide laws (apply in every aspect)
- Reversibility before action — from triage onward, every step must be undoable; healing that can't be reverted is a second gamble, not a cure.
- Combat-speed science — hypotheses and predictions still get written before probes (a one-line ledger form exists for exactly this); urgency never suspends the scientific method, it compresses the paperwork.
- Root cause or labeled symptom-patch — the heal claims what it actually is; "it stopped happening" is not "it's fixed".
- Every heal ends in a postmortem line — one structured line; the wound pays for a lesson or it was pure loss.