The Workflow Engine · 05.04
What "Self-Healing" Actually Means
Four real mechanisms working together — a recovery ladder, a law against silent restructuring, a pattern-recognizer for repeat failures, and a safe way to change a live run — not a single feature.
Not one feature — four, working together
| Mechanism | What it actually does |
|---|---|
| The Recovery Ladder | When a node fails, climbs from a free deterministic reflex up through certified structural repair — cheapest and least invasive first, never reaching further than the failure actually requires. |
| Blueprint Law | A graph that's already proven itself in production can never be silently restructured while "healing" something unrelated — runtime-class failures are classified out before structural surgery is ever considered. |
| The Instinct Engine | Notices when the same failure keeps recurring across runs and proposes a real fix — the difference between healing one incident and actually learning from a pattern. |
| Atomic Evolution | The contract that makes changing a live run's graph safe — a monotonic ratchet that never lets a mid-run edit make things worse, so healing itself can never be the thing that corrupts a graph. |
The failure that motivated all four at once
The concrete scenario this whole design exists to prevent actually happened: a workflow was fixed and proven in production. One run then failed — not because the graph was broken, but because of a bad model response, a pure runtime-class hiccup. The healing process at the time didn't know the difference, and performed structural surgery on a structure that was never actually broken. Blueprint Law exists so runtime-class failures are recognized and never reach for a graph edit; the recovery ladder exists so a repair only ever escalates as far as a failure genuinely requires; the Instinct Engine exists so the operator learns "this keeps happening" instead of re-discovering it manually each time; and Atomic Evolution exists so that even a legitimate, warranted graph change can't quietly make things worse than they already were. Self-healing is all four of those guarantees holding at once — remove any one, and the disaster above becomes possible again.
Continue
The five-stage discipline behind every hardened workflow, from declaring how success will be verified to a verdict engine that never trusts a self-report.
The SWIFT verdict engine probes the real world after a run settles instead of trusting a self-report, distinguishing accomplished from merely completed.