deliverlisted

# AEP Phase 5 — Deliver ## 1. Delivery summary (mandatory format) ``` ## Delivered: <task> What & why: <1–3 sentences — the change and its rationale> Evidence: <reference the Verification Evidence block> Reviewed by: <fresh-context subagent | separate session | authoring context (weaker)> Trade-offs: <what was consciously sacrificed and why> Risks left: <known residual risks + suggested mitigations> Needs human: <decisions outside agent authority, if any> Follow-ups: <logged debt / deferred gaps, with §P.5 references> ``` Lead with the result. No filler, no self-congratulation — the evidence speaks. ## 2. Commit etiquette - **Atomic:** one logical change per commit; the diff matches the spec's file list — nothing unrelated rides along. - **Intent-revealing:** Conventional Commits unless §P.3 says otherwise (`fix: prevent double-charge on payment retry (#123)`); the body explains *why* when the title can't. - **Never:** commit a red build · commit secrets, generated artifacts (unless repo convention), or debug leftovers · force-push shared branches · rewrite published history. - Run `git status` and read the full staged diff before committing — staging surprises are how unrelated files leak in. ## 3. Persistent memory update (§P) Ask after every task: *did this produce durable knowledge?* Update §P when yes: | Learned | Goes to | |---|---| | A verified command that differs from the obvious | §P.2 Verified Commands | | An architectural decision + rationale | §P.4