Capstone Architecture and Executive Defense

5. Current Mission Control readiness gate

Before scheduling the accepted run, verify:

• the selected Mission Control commit is merged, clean, and recorded;
• the GitHub App is configured for the controlled repository;
• an active Governance Policy and passing Factory Configuration exist;
• the browser path creates the Mission and approved Plan without database shortcuts;
• the supported executor, worktree, publication, and receipt path is enabled;
• deterministic validation is real, not a mock adapter;
• reviewer identities and evidence storage are available; and
• the baseline can be reset without deleting retained proof.

At the current study boundary, these are not all proven. Draft PR #64-era execution work and the subsequent continuous-quality design provide components, but the capstone must cite the final merged commit and fresh browser evidence.

7. Required failure and recovery

Trigger one meaningful failure: preflight denial, stale lease, executor timeout, validation failure, head-SHA mismatch, duplicate completion, cancellation, or GitHub publication failure. Show:

• classification and operator-visible state;
• the authoritative record and immutable history;
• whether retry is permitted and which budget applies;
• creation of a new Attempt where required;
• idempotent handling of late or duplicate events;
• evidence retained, invalidated, or made stale; and
• recovery without direct-state mutation or authority bypass.

8. Architecture defense

Whiteboard from memory:

Business intent
 -> governed Mission and executable specification
 -> approved Plan and Quality Contract
 -> authorized WorkOrder
 -> Task and immutable Attempts
 -> isolated agent/tool execution
 -> artifact and supply-chain provenance
 -> independent verification and evidence graph
 -> policy eligibility and human decision
 -> PR/release governance
 -> production observation and governed learning

Overlay control, execution, quality, delivery, data, security, and human-governance planes. For each boundary name owner, record, identity, failure mode, recovery, and proof.