Authority Rule

This document is the canonical methodology authority for OCI^™/OCRA^™.

All companion, derivative, executive, marketing, or procurement documents must:

reference this document,
not redefine canonical terms in conflicting form,
not claim stronger methodological guarantees than this authority permits,
not duplicate doctrine in divergent language,
resolve any methodological conflict in favor of this document.

This authority does not redefine the canonical five-phase OCI Method™ doctrine published in docs/oci/OCI_METHOD.md. That document remains the canonical method doctrine. This whitepaper authority embeds and protects that doctrine; it does not replace it.

Canonical Definitions

These definitions are binding across all OCI^™/OCRA^™ materials. They may be expanded but may not be redefined in conflicting form.

Term	Canonical definition
Organizational Continuity Infrastructure (OCI^™)	The structured operational foundation that preserves organizational memory, governance lineage, operational evidence, organizational intelligence, and continuity resilience across time, systems, and leadership transitions.
Organizational Continuity Risk Analysis (OCRA^™)	The adaptive, reviewer-led interpretation layer that surfaces continuity fragility, stewardship topology, governance interpretation drift, modernization-driven continuity risk, and onboarding survivability.
Governance Entropy System (GES^™)	The interpretive framework for governance continuity fragility, treating governance entropy as a continuous, observable property rather than a discrete failure event.
Continuity debt	Accumulated undocumented operational dependency on undocumented interpretation, informal relationships, and individual memory.
Reconstruction burden	The effort required to rebuild operational continuity from memory and fragments after a transition.
Stewardship concentration	The condition in which a small number of individuals carry disproportionate organizational continuity load.
Onboarding survivability	The structural ability of successors to become operationally effective without veteran mediation.
Modernization fragmentation	The pattern in which modernization improves operational surfaces while eroding interpretive context.
Operational trust	The confidence stakeholders place in an organization's ability to preserve continuity, maintain governance integrity, validate operational lineage, and demonstrate accountable decision-making over time.
Runtime truth	The continuously verifiable operational state of governance controls, evidence integrity, and continuity.
Continuity-aware AI	AI systems intentionally designed to preserve organizational memory, governance lineage, operational context, evidence integrity, and traceability throughout AI-assisted operations.

Binding Method Boundaries

OCI^™/OCRA^™ do not:

monitor individual productivity,
rank, score, or evaluate individuals,
infer behavioral compliance,
conduct workforce surveillance of any form,
conduct sentiment analysis or political inference on individuals,
replace formal external audits,
claim ISO, COBIT, SOC, or NIST certification equivalence,
function as deterministic ranking systems for organizations,
produce organizational verdicts without reviewer acceptance,
operate outside explicit organizational consent.

OCI^™/OCRA^™ are:

evidence-sensitive,
confidence-aware,
reviewer-led,
governance-safe,
anti-surveillance,
complementary to recognized governance standards,
bounded by published epistemic limitations.

These boundaries are doctrine, not configuration. They cannot be relaxed by deployment, customization, contractual variation, or downstream interpretation.

Ontology and Layer Separation

The method maintains a strict separation between layers:

Operational reality — the lived work of grievances, governance, investigations, evidence, onboarding, and modernization.
OCI structural layer — the infrastructure that preserves organizational memory, governance lineage, evidence integrity, and continuity resilience.
OCRA interpretive layer — the reviewer-led continuity intelligence that reads structural signals against operational reality.
Continuity-aware operations — the convergence layer in which OCI^™ and OCRA^™ reinforce daily organizational work.

Layer separation is doctrine. The method must never collapse operational reality into interpretation, or interpretation into verdict.

Reviewer Accountability

Reviewer accountability is the legitimacy anchor of the method.

No continuity reading is organizational truth until a named human reviewer accepts it on behalf of the organization.
No AI surface concludes on behalf of the organization.
Reviewer overrides are first-class outputs and inform future confidence calibration.
Reviewer accountability is structural; it cannot be removed by configuration.

Confidence Doctrine

Every continuity reading carries a visible confidence state.
Confidence is informed by evidence sufficiency, structural consistency, contradiction detection, reviewer history, and domain calibration.
Contradictions are surfaced as meaningful signals; they are not averaged away.
Where evidence is insufficient or reproducibility is uncertain, the method declines to conclude. Declination is a legitimate methodological output.

Evidence Sufficiency and Reproducibility Doctrine

A continuity claim must be backed by sufficient, structurally consistent operational evidence to be defensible.
A continuity reading must be reproducible from its underlying operational facts by another competent reviewer.
Where reproducibility is uncertain, the ambiguity must be surfaced, not hidden.

Statistical Doctrine

The method uses statistical techniques only where statistical claims are appropriate.

Statistics may be used to detect structural patterns, characterize distributions of stewardship concentration, estimate reconstruction burden ranges, baseline continuity fragility ethically, and support confidence calibration.
Statistics must not be used to rank individuals, infer behaviour, produce organizational verdicts, replace reviewer judgment, or claim predictive forecasts about specific transitions.
Small organizational samples must be treated honestly: claims are bounded, confidence ranges are widened, and interpretation is preferred to inference.

Composite scoring across heterogeneous signals is intentionally avoided where it would obscure structural meaning.

Anti-Surveillance Doctrine

OCI^™/OCRA^™ explicitly forbid:

monitoring individual productivity,
scoring, ranking, or evaluating individuals,
behavioural inference about individuals,
sentiment or political inference about individuals,
workforce surveillance of any form,
extending continuity signals into general-purpose monitoring.

Anti-surveillance is doctrine. Any deployment, customization, contract, or interpretation that would conflict with this doctrine is out of scope of OCI^™/OCRA^™ and may not be branded as such.

Standards Positioning Doctrine

OCI^™ and OCRA^™ are complementary, not equivalent to recognized standards.

They do not certify governance.
They do not replace audits.
They do not substitute for management system standards.
They sit alongside ISO 22301, ISO 27001, ISO 9001, SOC 2, NIST AI RMF, and COBIT, providing the organizational continuity dimension underneath those frameworks.

Procurement bodies adopting OCI^™ do not have to choose between OCI^™ and their existing standards stack.

Methodology Companion Relationship

The following documents are public-facing interpretations of this authority:

docs/oci/whitepapers/OCI_METHOD_COMPANION_WHITEPAPER.md — Methodology companion.
docs/oci/whitepapers/THE_CONTINUITY_GAP_OPERATIONAL_REALITY_EDITION.md — Executive whitepaper, operational-reality-first edition.
docs/oci/whitepapers/OCI_OCRA_WHITEPAPER_ARCHITECTURE_v2.md — Architecture and dual-entry GTM doctrine.

These documents are valid only insofar as they remain consistent with this authority. Any conflict is resolved in favor of this document.

Brand and Enforcement Doctrine

The names Organizational Continuity Infrastructure, OCI, Organizational Continuity Risk Analysis, OCRA, OCI Method, Governance Entropy System, and GES, when used in connection with continuity intelligence or continuity infrastructure, refer to the doctrine defined in this authority.

A deployment, configuration, contract, or downstream interpretation may not be branded as OCI^™/OCRA^™ if it:

relaxes any binding method boundary,
removes reviewer accountability,
introduces workforce surveillance, behavioural inference, or individual scoring,
claims certification equivalence with standards listed in the standards positioning doctrine,
removes the limitations or epistemic boundaries section from public methodology materials,
redefines a canonical term in conflicting form,
conflicts with the canonical five-phase OCI Method™ doctrine in docs/oci/OCI_METHOD.md.

Out-of-scope deployments must be named and described under a different label. The integrity of the category depends on this constraint.

Governance and Versioning

Changes to this document require:

doctrine review,
terminology lock review,
procurement boundary review,
anti-surveillance posture review,
standards positioning review,
version increment and changelog note.

Companion documents are updated after this authority is updated, never before.

Changelog

v1.0 — Initial canonical authority: authority rule, canonical definitions, binding method boundaries, companion relationship, versioning.
v1.1 — Expanded canonical definitions; added ontology and layer separation; added reviewer accountability, confidence, evidence sufficiency, statistical, anti-surveillance, and standards positioning doctrine sections; linked operational reality edition and methodology companion; clarified relationship to canonical OCI Method doctrine in docs/oci/OCI_METHOD.md.
v1.2 — Added Brand and Enforcement Doctrine; codified disqualifying conditions for OCI^™/OCRA^™ branding; reaffirmed deference to canonical five-phase OCI Method doctrine.

Closing Authority Statement

This document protects the integrity of OCI^™/OCRA^™ as continuity infrastructure. Its purpose is not to maximize what the method may claim, but to ensure that what the method claims, it may be trusted to mean.

— Nzila OS Research Initiative

The OCI Method — Canonical Authority

Abstract