The Stack
Architecture
MCA → Designation Bridge → CSI → Module → PI → CRI
The MetriqOne stack is a stacked node architecture that links organisational intent to measurable evidence. Each node is a diagnostic surface, not a step — there is no flow, no translation, and no hierarchy between them, only structural linkage. None can be skipped.
MCA (Mission Context Architecture) is the context spine — the organisation's environment, constraints, challenges, and aspirations, authored by its human owner. Designation Bridge is the single orienting sentence derived from the MCA, converting context into the first structured performance framing.
CSI (Critical Success Indicator) identifies the conditions without which the organisation cannot hold. The Core three are fixed: Stability, Safety, and Continuity. Every deployment uses these three at minimum.
Module is the context-configured layer. Each CSI may have up to three Modules — operational domains that carry evidence to the CSI. A Module can feed more than one CSI at once, and a PI can feed more than one Module — the same observation doing two jobs is by design, not an exception.
PI (Performance Indicator) is the evidence-collection unit, designed using SMART Logic. No more than nine PIs per CSI.
CRI (Critical Result Indicator) is the output of the stack — a validation signal based on how many of a CSI's three Modules are independently within their own control limits, not on whether the Modules agree with each other. A water-level Module, a road-access Module, and a landslide-risk Module have nothing in common to agree on — each is judged against its own threshold, on its own terms.
Why Stability, Safety, and Continuity Are Non-Negotiable
Most performance frameworks let organisations choose their own top-level categories. MetriqOne does not. Stability, Safety, and Continuity — the Core — are fixed across every deployment, every context, every sector.
Stability covers the conditions under which the organisation can operate reliably. Safety covers the protection of people and assets. Continuity covers the conditions under which operations can persist over time.
Fixing the spine at CSI level means that a manufacturing cooperative, a municipal water utility, and an NGO field office all operate within the same structural logic, regardless of where they sit. Their Modules and PIs differ. Their Core CSIs do not.
Larger or federated deployments run Extended — the same Core three, plus Capability, Actor Orientation, and Process Flow stacked beneath them: six CSIs, eighteen Modules, fifty-four PIs, six CRIs. Not a different framework bolted on. The same spine, carrying more weight, for the deployments that need it.
How Modules and PIs Are Configured
Below the fixed spine, MetriqOne is entirely context-specific. Modules are defined by the organisation, for the organisation. A Stability CSI in a logistics company might have Modules for Fleet, Warehouse, and Procurement. The same CSI in a rural health clinic might use Modules for Supply Chain, Staff Capacity, and Facility Condition.
PIs are designed within Modules using SMART Logic. A PI may feed more than one Module, and a Module may feed more than one CSI, simultaneously — the same observation doing two jobs at once. This is the leverage question that makes the framework resistant to gaming: can this PI carry evidence to a second place that legitimately needs it? Where it can, it should.
The constraint is architectural: no more than three Modules per CSI, no more than nine PIs per CSI.
| Level | Logistics SME | Health Clinic |
|---|---|---|
| CSI | Stability | Stability |
| CSI | Safety | Safety |
| CSI | Continuity | Continuity |
| Module | Fleet | Supply Chain |
| Module | Warehouse | Staff Capacity |
| Module | Procurement | Facility |
| PI | Fleet availability rate | Stockout frequency |
Why Cross-Deployment Comparison Is Possible
Because every deployment shares the same three Core CSIs — and Extended deployments share the same six — any two deployments can be compared at the CSI level, regardless of sector, geography, or size. A water utility and an unrelated transport cooperative are not comparable at Module or PI level. But their Stability CRIs are structurally identical constructs — produced by the same architectural logic and the same calibration discipline.
This is what makes cumulative learning possible across the MetriqOne deployment base — a growing body of cross-contextual evidence about what organisational stability, safety, and continuity actually look like in fragile environments.
Urban infrastructure
Logistics network
CRI
CRI
CRI
The Critical Result Indicator
The CRI is not a score, a rating, or a performance judgment. It is a validation result — based on how many of a CSI's three Modules are independently within their own control limits. The Modules are not compared against each other; each is judged on its own terms, against its own threshold. No single actor, no single PI, no single Module can validate a CSI alone.
Miscalibration is a separate, and separately fatal, failure mode. Every PI carries a pre-declared calibration threshold, set before the measurement period began. If that threshold is set too low, the PI reads green under genuinely poor conditions — and a CRI built on a miscalibrated PI is not evidence of good performance, it's evidence of poor governance. The Calibration Log is the scrutinisable record that protects against this, independent of whether the CRI itself confirms.
Go Deeper
The full architecture is documented in the books.
Book I deploys it. Book II explains why it is designed this way. Both are available now on Amazon.