The Continuity Loop
An installation is not static, so neither is its model. The Continuity Loop keeps the model true as the system changes — the rhythm of the subscription.
A living model, not a one-off
A one-time report starts going stale the moment the installation changes. The Continuity Loop is the ongoing practice of keeping the model true: re-assess when the system changes, see exactly what moved, and capture the decisions and open questions alongside the model. It follows a simple Plan / Do / Check / Act rhythm.
What changed since last time
When a system is re-assessed, the drift view compares the new model against the previous baseline and shows exactly what is added, removed, or changed — and, importantly, which previously signed-off behaviours a change has invalidated (so they need re-review). Instead of re-reading the whole system, you review only what moved.
The continuity notebook
Each assessment has a notebook — a set of short, structured documents that live next to the model. The model is the structured truth; the notebook is the human decision layer: control decision records, known-unknowns, change notes, verification summaries, and more. Notebook documents can deep-link to the exact behaviours they concern, so a decision is always tied to the evidence.
Auto-drafts from the model
Rather than starting from a blank page, you can generate first drafts straight from the model:
| Draft | Built from |
|---|---|
| Known unknowns | Every behaviour still needing clarification, linked to its claim. |
| Change impact | The drift between the two most recent baselines. |
| Verification summary | The current review coverage of the model. |
| AI-use record | The AI runtime ledger for this assessment. |
The PDCA board
Notebook documents can be viewed as a list or on a Plan / Do / Check / Act board, so the continuity work has a visible state. Everything is portable: any document exports as clean Markdown you own.
What it is not
The Continuity Loop is scoped to automation continuity — keeping the model of your control system true and its decisions captured. It is not a maintenance-management (CMMS) or quality (QMS) system, and does not try to be. It stays focused on the one thing it does: a living, evidence-backed model of what your automation does.