Review Plan

Read the supplied approved design or scope, the bounded plan target, and only explicitly justified supporting files, under the finding rules and verdict in review-change. Implementation code is not read to invent requirements.

Plan-Specific Checks

• First real result: the thin business path comes early; each disputed pre-cutover check names the concrete loss it prevents or why the operation cannot proceed without it, otherwise it moves after cutover or is reused.
• Two verification levels: binding outcome or boundary acceptance at the delivery endpoint is distinct from revisable candidate local proof methods; a simulation harness, container rebuild, or duplicate assertion that deterministic checks plus real-path verification already cover is a finding to collapse.
• Milestone and tasks: the milestone is coherent; task IDs, surface inventories, and recovery paths appear where independent work or a risky transition needs them; a plan's own granularity, dependency edges, or local proof methods are not treated as fixed user intent.
• Authority: external, destructive, and side-effecting actions keep explicit authority; covered authority and generatable products are not reported as missing.
• Initial readiness and delegation: the first useful local action or parallel assignments are decidable from the plan; a proposed delegated slice is independent, isolated, conflict-free, and convergent; worker counts, fixed topology, exploration prerequisites, or literal dispatch fields are flagged only when imposed without a useful result or real dependency; no model or provider is named.
• Essential inputs: already-known inputs for actions through delivery are recorded or recoverable from accessible owner references; a claim that access or credentials were supplied without a usable reference is a handoff defect. Secret values are not requested.
• Live plan: effective goals, authorized discretion, ownership, endpoints, and real pause conditions stay compact; user decisions, investigable facts, generatable products, and technical verification stay distinct.
• Briefs: a worker brief preserves the parent goal, protected behavior, tradeoff boundaries, environment facts, endpoint, and required versus missing authority without pre-solving the implementation or letting a child self-authorize.