Failure management
A Failure Is a Traceable Event, Not a Dead End.
Every failure class has an alert, a trace, a diagnosis path and a permitted action under policy.
ARCHITECTURE / DEPLOYMENT PREVIEW
Failure classes
Build FailedValidation FailedDeployment FailedVerification FailedSurface Not ReachableAPI FailureConfiguration ConflictMissing RecordMissing NamespaceGraph Dependency MissingDomain ErrorData Validation Failure
- 01FAILURE
- 02ALERT
- 03TRACE
- 04DIAGNOSE
- 05ACTION
- 06RETRY / ROLLBACK / MANUAL REVIEW
- 07VERIFY
- 08AUDIT
Failed preview records
What a failure record looks like
| Deployment | Stage | Status | Diagnosis | Rollback target |
|---|---|---|---|---|
| DEP-US-MN-ROC-00000187 | VALIDATE | PREVIEW · FAILED | Record Drift — required Business Record missing | REL-14 |
| DEP-US-MN-STATE-00000189 | OBSERVE | PREVIEW · ROLLED BACK | Template Drift — desired v6, observed v5 | REL-12 |
failure trace — TRACE-20260911-000187
[16:40:02] PLAN ok [16:40:04] RESOLVE NAMESPACE NS-GEO-US-MN-ROCHESTER ok [16:40:07] LOAD CONFIGURATION CFG-CITY-MN v12 ok [16:40:09] LOAD TEMPLATE TPL-CITY v8 ok [16:41:14] LOAD RECORDS BR-90551 ok / required BR missing [16:41:18] VALIDATE FAILED — missing record ! alert critical ! action manual review · rollback candidate REL-14 ! audit recorded