Change lifecycle

A change moves through the same decisions every time:

1. Ground the request in product knowledge.
2. Write an intent the person can approve.
3. Approve the written outcome.
4. Investigate real code and write plans.
5. Request execution after the plans exist.
6. Implement in prepared worktrees and run checks.
7. Authorize delivery.
8. Request completion and reconcile the knowledge that changed.

Optional workers and cleanup sit beside this path. They do not replace it.

Request through execution

The agent grounds a request in product knowledge and writes an intent. You read it and approve the outcome. The agent investigates real code and writes plans. Once plans exist, you request execution; the agent prepares worktrees, implements, and runs checks.

Delivery through reconciliation

You authorize outward delivery. After the work lands, you request completion. The agent appends the note and reconciles the knowledge affected by the implementation. That knowledge feeds the next request.

Neither a CLI diagnostic nor an editable approval field supplies consent. Delivery does not mark completion, and completion does not delete working copies. See human control boundaries for the full decision table.