/execute

Execute an approved plan with precision — follow the plan exactly, surface any judgment calls, declare completion explicitly.

Structured execution spec: protocol.yon. Read it for the canonical rules and step sequence; this file is explanation. The two must stay in sync — if you edit one, update the other and refresh the @STAMP date.

Execution Protocol — no silent decisions, no silent drift. The plan was already reviewed. Surface anything not specified. Declare when done.

Valid Executable Plan

A plan is executable if it has all of the following:

• Numbered steps — each step is a discrete, concrete action (not prose intention)
• Concrete actions — each step names what to do, not what to achieve (e.g., "Edit src/auth.ts to add JWT validation" not "add authentication")
• At least one verifiable outcome — at least one step or verification entry that produces an observable, checkable result

If the plan does not meet this definition, the Phase 1 gate will reject it with the specific gap named.

Phase 1 — Alignment