wiki/projects/continuity-office

Continuity Office

wiki/projects/continuity-office/index.md

Rendered from markdown source. Open raw source on GitHub.

Continuity Office

This branch collects the continuity training catalog and its supporting materials structure.

Quantum Invariants is useful here as the comparator language for continuity: it helps name what stays stable, what drifts, and what needs a repair path. Witnessing is the adjacent procedural concept: it certifies the state that continuity then has to carry forward. In this branch, the curriculum and the support rails are the practice surface for that handoff. Witness Infrastructure is the larger container around that handoff: it preserves legitimacy and reconstructable state once the continuity work has to survive autonomous transformation, not just human turnover.

Current Shape

  • 20 published lessons.
  • 1 public site lineage.
  • 1 standalone support handout plus added support/engagement material.
  • 8 nested lineage pages organize the set.
  • 1 draft lesson remains held out of the live catalog.

Nested Lineage Pages

Representative Files

Working Read

This is a compact continuity curriculum with a separate public-site lineage rather than a loose bundle of training notes.

The branch separates cleanly into five lesson tracks plus a continuity-in-practice rail, a public-surface rail, and a quick-start support layer. The site variants track the homepage, theme, and structural passes; the support material stays beside the lessons as reusable operational packaging rather than as another lesson track.

The published catalog is the live surface. The draft First 90 Days of Continuity stays out of the live set until it is ready. The Voting Machine project sits nearby as a concrete governance example for decision provenance, custody, and auditability when continuity work crosses into civic or authority-sensitive systems. The Continuity Engine is the runtime counterpart to this curriculum, while AI Witness is the non-executing mirror that notices drift before continuity breaks. The LoopLink concept is the transport-and-recovery vocabulary that lets this curriculum move state without collapsing meaning.

Related Links

Next Actions

  1. Keep the five track pages stable.
  2. Keep the site-variants rail separate from the lesson catalog.
  3. Leave the draft lesson out of the live catalog until it is published.
  4. Add adjacent support materials only when they are clearly standalone and reusable.