Plans

A plan is a contract, not a transcript.

A typed plan gives the implementer, reviewer and final gate the same object to reason about. It names files, risks, interface contracts and verification steps before work starts.

TECHNICAL PROOF Route status
protocol / protocol/plans gated
plan accepted
validate_plan accepted
implement evidence open
review_changes findings open

validate_plan

Bad plans should fail early.

validate_plan checks whether the plan covers the task contract, names risky assumptions and includes verification that matches the real failure path.

Cross-project

A shared plan can project into sub-runs.

For cross-project work, the global plan carries the interface contract while per-project subtasks stay scoped to each repo.