Rehearsal 2: A record that maintains itself
2:56 min · narrated walkthrough of the demonstration build · synthetic narration, synthetic estate
Recorded from the running demonstration build. Narration is synthetic; the live demonstration carries a human presenter. Every figure shown is computed from pinned sources.
Transcript
- For the architecture and governance team. Four minutes on what Cairns does that the tools you already know do not.
- One application, end to end. Custodians, capabilities, twenty-four configuration items with their lifecycle positions, and the documents that mention it, each pinned with its hash. The diagram is generated from the record, never drawn by hand. Corrections are proposed from this page and commit on approval.
- And design itself. The canvas reads from the register and writes through review. A link drawn here lands as a proposal, dashed until approved, and then it is the record. A diagram that cannot drift.
- Sight of the corpus. The board minutes revoked a waiver. A design's decision was superseded. Both surface as diffs with before-and-after hashes, and both versions are retained. Below them: three shadow applications the register never recorded, found in the documents and queued for registration.
- Every review item arrives with the resolution already drafted and its evidence attached. Register the shadow application. Restate the revoked waiver. Record the supersession. Preparation is machine work. The decision is the architect's. And the commit is logged.
- Put a draft against the model before the review. Two applications referenced, both inheriting unsupported technology. A waiver assumed to be standing that was revoked this cycle. An uncatalogued message broker, stopped at the door. And routing recommended. Nothing in this analysis was generated by a model.
- Ask the estate. Two hundred and thirty applications exposed inside eighteen months, with capabilities and custodians joined, and the sources named under the answer.
- And when the sources cannot answer, Cairns refuses, and logs the refusal. A tool a regulator can defend does not invent.
- Every AI feature is disclosed: the model it uses, the data it processes, retention behaviour, and its own switch. All inference runs in-tenancy on open-weight models. No estate data trains any model.
- The master switch, thrown. The platform continues. The AI stops. That is the behaviour the security requirements ask for, working.
- Production components, honestly labelled status, and a fixed price that puts the delivery risk on us. The response carries the detail. Cairns. A record that maintains itself.