The Continuity Canon
Continuity isn’t a document. It’s a capability.
Training 001 · Foundations
Time: 20–35 minutes (+ discussion)
Core stance
Continuity is not “documentation.” Documentation is an artifact.
Continuity is the capability to preserve intent, consent, and legibility through change—without turning the organization into a bureaucracy.
Why this exists
Most organizations lose time in predictable ways:
- Key-person dependency (“only Sarah knows this”)
- Undocumented rationale (“don’t touch it, no one knows why”)
- Brittle processes (“it works until it doesn’t”)
- “Temporary” workarounds that become permanent
- AI deployments that outrun governance and consent
The Continuity Canon is a simple promise:
If these invariants hold, change becomes survivable.
If they don’t, failures become latent—appearing later as scramble, downtime, audit panic, and institutional amnesia.
The Continuity Canon
The irreducible invariants of survivable organizations
If one is violated, continuity degrades.
If several are violated, failure becomes latent rather than visible.
If all are honored, change becomes safe.
Canon I — Intent must survive its authors
(Intent Persistence)
Every non-trivial system, policy, or process exists because someone made a decision for a reason. Continuity requires that the why survives beyond the people who made it.
Violation looks like
- “We don’t know why this exists, but don’t touch it.”
- Policies enforced without rationale
- AI trained on outcomes stripped of intent
Continuity practices
- Lightweight decision records (what / why / tradeoff / revisit triggers)
- Rationale annotations
- Explicit revisit triggers
Without intent persistence, automation becomes superstition.
Canon II — Knowledge must be legible to non-initiates
(Legibility Across Time)
If understanding a system requires oral tradition, continuity is already broken.
Violation looks like
- “Ask Sarah, she knows.”
- Shadow-only onboarding
- Docs that assume context
Continuity practices
- Context-first documentation
- Workflow walkthroughs
- Drift-aware knowledge bases
Legibility is not completeness. It is reconstructability.
Canon III — Responsibility must be traceable without blame
(Accountable Traceability)
Violation looks like
- Anonymous decisions
- Blame cultures
- Defensive documentation
Continuity practices
- Decision lineage
- Blameless postmortems
- Clear RACI for high-impact systems
Traceability is for learning, not control.
Canon IV — Systems must fail in explainable ways
(Explainable Failure)
Violation looks like
- “It just does that sometimes.”
- AI outputs no one can defend
- Symptom-only incident reports
Continuity practices
- Causal narratives
- Boundary clarity
- Explicit uncertainty markers
Canon V — Consent must be preserved through transformation
(Consent Continuity)
Violation looks like
- Permission assumed to persist
- AI scope creep
- Silent reuse
Continuity practices
- Consent-bound data flows
- AI mandates and boundaries
- Revocation paths
Canon VI — Change must be reversible in principle
(Reversibility)
Violation looks like
- Irreversible migrations
- Vendor lock-in without exit narratives
- Policy changes without rollback stories
Continuity practices
- Migration rationales
- Exit assumptions
- Rollback intent
Canon VII — Memory must be distributed, not centralized
(Anti-Hoarding)
Violation looks like
- Bus factor = 1
- Knowledge trapped in people or tools
Continuity practices
- Pairing
- Handoff rituals
- Redundancy in explanation
Canon VIII — Governance must match system power
(Power-Proportionate Governance)
Violation looks like
- Lightweight controls on heavyweight systems
- Automation outrunning oversight
Continuity practices
- Impact tiers
- Graduated review thresholds
- Explicit delegation boundaries
Canon IX — The organization must be explainable to itself
(Self-Legibility)
Violation looks like
- Leadership surprised by audits
- Strategy divorced from operations
Continuity practices
- Plain-language narratives
- Interpretable metrics
- Reality-based reporting
Canon X — Continuity must be a first-class design constraint
(Continuity by Design)
Violation looks like
- “We’ll document it later.”
- Speed prioritized without memory
Continuity practices
- Continuity review gates
- Time-aware ownership
- Future-reader artifacts
The meta-canon
Continuity is about dignity.
Dignity of future employees.
Dignity of regulators.
Dignity of customers.
Dignity of intent.
Dignity of human judgment in a machine-accelerated world.
Exercises
Drill 1 — Bus Factor Reality Check
Pick one critical workflow.
How many people could run it end-to-end without help?
Goal: increase that number by +1.
Drill 2 — One Decision Record
Write a 10-line decision record:
- What
- Why
- Tradeoffs
- Revisit triggers
Canon: I + VI
Drill 3 — AI Boundary Sentence
Write:
- What the AI may do
- What it must not do
Canon: V + VIII
FAQ
Is this just documentation?
No. Documentation is an artifact. Continuity is a capability.
Will this slow teams down?
Done poorly, yes. Done well, it removes scramble and rework.
How does this relate to compliance and security?
Continuity is upstream. It makes evidence easier and more honest.
Suggested next step
Pick one Canon that feels violated today.
Run one drill. Capture one artifact. Reduce one fragility point.
That’s how continuity becomes real.