Labs3 min readlabQuick Readfailure injection lab
Authority, Containment, and Decision Replay Lab
Prove that a factory can stop unsafe work through an independent control path, reconstruct delegated authority without hidden model reasoning, reconcile partial effects, and restore only the minimum qualified authority.
Status: Review readyRisk: criticalLifecycle: execute · verify · learnContent reviewed 2026-08-30Maturity guide →
Claim boundaryThis chapter references implementation evidence. Inspect its evidence boundary before treating a claim as proven.
architecture mode
A focused view of boundaries, contracts, state, authority, failure paths, and tradeoffs drawn from this chapter.
Hands-on lab
Prove that a factory can stop unsafe work through an independent control path, reconstruct delegated authority without hidden model reasoning, reconcile partial effects, and restore only the minimum qualified authority.
Execute the existing Markdown instructions and retain the required output and evidence.
Jump to validation criteria4. Procedure and failure injections
- Run the baseline to accepted synthetic outcome. Retain the complete authority and evidence chain.
- Start a candidate run and inject a loop that exceeds the planned tool-call rate while a mock publication returns a timeout after applying its effect.
- Make the primary orchestrator unavailable.
- From the independent control path, pause the workflow and revoke the attempt grant. Send the same commands twice.
- Verify the worker cannot schedule new steps or call the tool gateway. Do not treat acknowledgement as enforcement.
- Quarantine the implicated capability version and identify all affected queued/running work and evidence.
- Reconcile the mock publication using its idempotency key. Classify the effect as completed, absent, or unknown; compensate if the manifest requires.
- Reconstruct the decision chain from intent, policy, grant, manifest, attempt, tool receipt, control events, and human decisions.
- Recover with a qualified capability version, a new manifest and grant, independent checks, and named restoration approval.
- Verify cleanup: leases expired, grants revoked, queues reconciled, sandboxes removed, mock effects disposed, evidence retained by policy.
Evidence boundary
Curriculum maturity is not implementation proof.
This chapter defines architecture or practice. It does not by itself prove a corresponding production implementation.
External review
Review this chapter.
Challenge a claim, boundary, missing failure mode, unclear term, or unsupported evidence statement.
- Claim
- Boundary
- Failure
- Evidence