§08 PART 4/4 (11,180 chars · Sections: The Fourteen Containment and Assurance Claims; The Article 08 Claim Card; A Stop Is a Transition, Not a Button; Frequently Asked Questions; Continue the Series; Primary Platform References; Publication Metadata) — ← Part 3 · §09 Part 1 → · 1-Call Brief · Full §08 · Raw .txt · All: P1 P2 P3 P4
The Fourteen Containment and Assurance Claims
| ID | Claim | Evidence and ceiling |
|---|---|---|
08-C01 |
Any admitted caller can engage a validated stop with a mandatory reason | Implemented and author-verified for machine, agent, and canonical project scopes |
08-C02 |
The active latch is persisted before secondary cleanup; scoped latches use staging and hard-link publication | Implemented and author-verified; machine latches use direct final-path creation |
08-C03 |
Cleanup, epoch, WAL, or signal failures after latching do not roll back containment | Implemented and author-verified through warnings and engaged receipts |
08-C04 |
Drain and recovery require no MCP session, explicit operator identity, and interactive stdin/stderr | Implemented and author-verified as a local console surface |
08-C05 |
Console detection is not biometric proof or a complete defense against a hostile same-user process | Explicit ceiling; worker confinement supplies the OS identity boundary |
08-C06 |
Epoch intent is WAL-durable before atomic snapshot replacement and readback | Implemented and author-verified; interrupted lineage fails closed and has console-gated reconciliation |
08-C07 |
Later matching scope revisions revoke old authority without waiting for TTL | Implemented and author-verified for leases, wakes, and receiving tenancies; unrelated scopes survive |
08-C08 |
Managed Job termination requires a fresh active-process count of zero | Implemented and author-verified; termination-call success alone is not quiescence evidence |
08-C09 |
Recovery carries unresolved file, destination, and model operations forward | Implemented and author-verified; no carried operation is marked complete by latch clearance |
08-C10 |
Drain admits only durably prepared effects for a bounded interval after a machine stop | Implemented and author-verified for 1–3,600-second deadlines; new effects remain refused |
08-C11 |
A stop racing machine recovery survives and produces FROZEN_SAFE |
Implemented and author-verified through exact planned-name clearance and post-clearance rescan |
08-C12 |
Candidate conformance runs as an owned, bounded child under a live package build lease | Implemented and author-verified with timeout, heartbeat, output draining, and cancellation |
08-C13 |
The default candidate battery contains 25 governance and 20 evidence cases | Implemented and author-verified against the binary in isolated state with source/image identity checks |
08-C14 |
Passing the battery is release qualification, not independent certification or exhaustive proof | Explicit assurance ceiling, preserved in publication evidence |
The Article 08 Claim Card
Mechanism:
AINA Sovereign Containment and Candidate-Binary Assurance
(latch-first break-glass, scoped control epochs, owned-Job observation,
in-doubt recovery, interactive owner recovery, 45-case publication gate)
Failure it governs:
Agents or scripts clearing their own emergency stop;
stale authority surviving after a matching stop;
successful termination calls mistaken for observed quiescence;
uncertain operations erased or blindly replayed during recovery;
stop/recovery races and unqualified release-binary promotion.
Positive path:
engage and persist latch
→ refuse new effects and observe owned-worker termination
→ append epoch intent and publish the scoped lineage
→ census and carry forward unresolved operations
→ owner-console recovery with a new epoch and post-clearance rescan
→ candidate source/image binding + 45 passing cases
→ verified publication and post-copy hashes.
Refusal / hold path:
owner_control_required, break_glass_contained, stale_control_epoch,
control_epoch_unconfirmed, control_wal_corrupt,
unresolved file/destination/model operation,
FROZEN_SAFE after a racing engage,
candidate timeout, lease-heartbeat loss, failed case, or ok != true.
Evidence status:
Implemented and Author-Verified on the declared Windows reference path.
Official platform documentation establishes primitive behavior, not independent
validation of AINA. The 45 cases are author-controlled release qualification.
Verifier and artifacts:
active and cleared latch records; run/wake cancellation receipts;
breakglass WAL, epoch snapshot, and recovery-evidence image;
fresh Job active-process counts and two-phase Room stop reports;
derived status phase, affected-worker quiescence, and uncovered_servers;
recovery_intent with carried_forward_operations and FROZEN_SAFE state;
candidate surface hashes, source digest, 45-case report, and package result.
Scope and claim ceiling:
Console presence is not biometric identity.
Scoped revocation preserves unrelated scopes; machine revocation covers all.
A stop cannot recall external effects or survive destruction of the host volume.
Conformance proves the exercised candidate vectors, not all possible behavior,
independent certification, or formal verification of the complete system.
Next stage in the machine:
Article 08 completes containment and release assurance. Article 09 applies the
full evidence-to-effect machine to one real customer-controlled boundary with
an explicit acceptance contract.
Commercial doorway:
Break-Glass & Conformance Qualification Challenge — bring one AI workflow that
needs emergency containment or release qualification; receive a scoped-stop and
stale-authority demonstration, unresolved-operation recovery plan, race test,
and candidate-gate coverage review (Article 09 · me@blayneaina.com).
A Stop Is a Transition, Not a Button
Trustworthy emergency control is not a red icon that calls kill().
It is a sequence with asymmetric authority: the latch appears before fallible cleanup; new effects close immediately; old scoped authority is refused; owned Jobs are observed quiescent; uncertain operations remain blocked; recovery requires a different physical control surface and mints a new lineage. If stop and recovery race, stop wins.
The release path follows the same philosophy. The candidate must demonstrate its refusals as itself, under a bounded and identity-checked publication process. Compilation is necessary. It is not sufficient.
The machine may resume only through the owner surface, under fresh authority, with every unresolved effect still visible.
Article 09 turns this completed architecture into a deployment engagement: one real boundary, one written acceptance contract, and evidence that the customer can independently inspect.
Frequently Asked Questions
Why can any admitted caller engage the stop?
Stopping is the safe direction. Requiring elevated recovery authority before containment would create a dangerous delay. Engage still requires admission, a nonempty reason, and a valid machine, agent, or project scope.
Can an agent clear its own emergency stop through MCP or a script?
No. Recovery refuses an active MCP session, requires --by operator, and requires interactive terminal handles for stdin and stderr. This is a local console boundary, not a claim of biometric identity; confined workers additionally lack OS permission to the control directory.
Does advancing control_epoch revoke every lease on the host?
Only when the advancing scope covers the authority. Machine recovery covers all scopes; an agent or project revision revokes matching older authority while unrelated scopes retain theirs. A future or unproven lineage fails closed.
Does recovery resolve operations whose outcomes are unknown?
No. Recovery records unresolved file, destination, and model operations in carried_forward_operations. Each remains unresolved and blocking until separately reconciled under fresh authority.
What happens if another stop arrives during recovery?
Recovery clears only the latch names fixed in its plan, then rescans. A new machine-covering latch survives, the state becomes FROZEN_SAFE, and the receipt does not report a successful all-clear.
Do the 45 passing cases certify the system independently?
No. They are author-controlled release qualification against the candidate binary in isolated fixtures. They prove the exercised positive and negative vectors, not independent certification, formal verification, exhaustive coverage, or reversal of external effects.
Continue the Series
- Series index: From Proposal to Consequence: The AINA Transition-Governance Series
- Previous: Article 07 — Defeating Approval Laundering: Act Pinning and Successor Grants
- Next: Article 09 — Bring One Real Boundary
- Deployment and independent review: Bring one real boundary or propose a method-scoped evaluation
Primary Platform References
- Microsoft
GetConsoleMode— console input and screen-buffer mode inspection - Rust
std::io::IsTerminal— terminal/TTY detection and platform behavior - Microsoft
CreateHardLinkW— NTFS hard-link creation - Microsoft Job Objects — grouped process management and
TerminateJobObject - IETF RFC 8785 — JSON Canonicalization Scheme vectors used by the evidence battery
Publication Metadata
Title tag: The Sovereign Kill Switch: Break-Glass Epochs and the Conformance Gate
Meta description: Asymmetric emergency containment, scoped control-epoch revocation, in-doubt recovery, managed Job termination, and the 45-case candidate-binary publication gate.
Series navigation: Series index · Article 08 of From Proposal to Consequence: The AINA Transition-Governance Series.
Previous installment: Article 07 — Defeating Approval Laundering: Act Pinning and Successor Grants.
Next installment: Article 09 — Bring One Real Boundary.
END OF §08 PART 4/4 — Next Article: https://blayneaina.com/09-bring-one-real-boundary-work-with-blayne/part-1/ · §08 1-Call Brief · Raw .md