delivery-planninglisted

# Delivery Planning Converts an approved architecture into work that can be executed one task at a time, in an order where nothing waits on something that does not exist yet. The plan is a working instrument, not a document produced for its own sake. It is short enough to update and specific enough to execute. ## 1. Milestones Group tasks into milestones that each end in something demonstrable. A milestone that produces nothing observable is a phase of the plan, not a milestone. Typical order, adapted to the architecture: ``` M0 Foundation repository, tooling, configuration, CI skeleton M1 Data schema, migrations, seed, the data layer M2 Identity authentication, then authorization M3 Core domain the business rules the product exists for M4 API the endpoints over the domain M5 Frontend base layout, design system usage, routing, data layer M6 Features one milestone per feature group, each end to end M7 Integrations external services, each with its failure path M8 Hardening security, performance, accessibility passes M9 Operations environments, pipeline, deployment, observability M10 Delivery documentation, handover, release ``` Feature milestones are vertical, never horizontal. `M6a invitations, end to end` is a milestone. `M6 all backends, then M7 all frontends` is a plan that discovers its integration problems at the end, when they are most expensive. ## 2. Atomic tasks A task is atomic when it can b