Intents
A written outcome a person can approve before detailed code investigation.
What an intent settles
An intent records the goal, non-goals, constraints, success criteria, rough repository scope, and open questions. It is grounded in existing product knowledge before detailed code investigation. A contradiction becomes a question for a person.
Approval is a real decision
The agent presents the intent and waits. The original request is not approval of the derived outcome. Approval records the actual words and approved_at; neither a field nor a command establishes consent.
Questions have stable numbers. Answers remain beneath them, so the discussion stays readable. A later question takes the next unused number.
What happens next
Approval authorizes code investigation and planning without a second planning permission request. If the outcome or success criteria change materially, return to the intent for renewed approval. A plan cannot quietly resolve a new product question.
Follow write and approve an intent.