Start Here
Intent → Plan → Define Agent → Execute through Harness → Apply Skills → Evaluate → Improve → Deliver Software
A focused view of boundaries, contracts, state, authority, failure paths, and tradeoffs drawn from this chapter.
The governing flow
The records are deliberately separate. Completing a Task does not accept its WorkOrder. Completing a WorkOrder does not accept its Mission. Passing tests does not authorize a merge or deployment. Each boundary represents a different claim and therefore requires different evidence and authority.
Evidence boundary
This guide uses three labels deliberately:
- Enduring Principle describes doctrine that should survive technology changes.
- Current Mission Control Implementation describes behavior supported by a cited commit, source path, test, or observed browser journey.
- Future Vision describes desired behavior that has not met the current evidence bar.
The distinction prevents a compelling product vision from being mistaken for working software.
Curriculum maturity is not implementation proof.
This chapter defines architecture or practice. It does not by itself prove a corresponding production implementation.
Review this chapter.
Challenge a claim, boundary, missing failure mode, unclear term, or unsupported evidence statement.
- Claim
- Boundary
- Failure
- Evidence