Methodology
A containment-first method for operational exposure, reliability debt, and contract-level decision readiness.
The Method
Recovery restores service. Containment removes the condition that allowed the failure to recur. Many programs record the first as the second, so recurring incidents are reported as resolved. AnchorPoint treats recovery and containment as separate outcomes and documents which one was actually achieved.
Operational exposure is the risk accumulated by unresolved failure conditions, unclear ownership, and incomplete closure documentation. Reliability debt is what that exposure costs over time: repeated effort, repeated escalations, and rework that never appears as a single line item until it surfaces in oversight.
Decision Readiness describes how well a program’s own evidence supports a decision. AnchorPoint assesses whether incident records, telemetry, escalation history, and closure documentation are complete and consistent enough to support an oversight, award-fee, or readiness decision without the explanation being improvised in the room.
Containment discipline is sustained by governance: named ownership, a review cadence, and corrective actions followed through to closure. AnchorPoint evaluates whether the practices that produced stability are documented and repeatable, or dependent on individual memory.
Behavioral drift is the gradual change in how incidents are escalated, documented, and contained under operational pressure. Recurrence velocity is the rate at which the same failure conditions return. Read together, they show whether containment discipline is holding or quietly eroding.
Operating Framework
AROS is AnchorPoint’s operating framework for reliability work. It is an organizational method, covering roles, evidence standards, review cadence, and decision rights. It is not a software product, and it is not a monitoring or ticketing platform.
AnchorPoint-OS, our internal software, is separate from AROS. OS supports AnchorPoint’s own planning and execution. AROS is the organizational framework that governs the work, and it stays the same whether or not software is used.
Reliability Lab
The Reliability Lab is AnchorPoint’s controlled environment for exercising the methodology. The same evidence standards used in client work are applied to failures we introduce ourselves.
Representative failures are introduced in isolated environments so detection, escalation, and containment behaviour can be observed directly rather than reconstructed afterwards.
System and operational data are captured during each scenario, so behaviour can be compared across runs instead of described from memory.
Repeated failure conditions are grouped and tracked over time to separate genuine containment from repeated recovery.
Each scenario is assessed against whether the underlying failure condition was removed, not whether service was restored.
Findings are compiled into structured packets with references back to the underlying evidence.
Implemented in the Lab
Planned, not delivered
Lab outputs published on this site are demonstrations and example formats. They show the structure of an evidence packet. They are not customer production results, and no independently validated predictive accuracy is claimed.
A 20-minute structured discussion to determine whether recurrence exposure is accumulating in your program, and which parts of the method apply first.