# Proportionate delivery planning

Compose these specialist techniques inside Codinary's discovery, acceptance criteria, delegation and evidence contracts. They add no alternate delivery command.

1. Start with a dependency map of observable capabilities and public interfaces. Settle consequential interface decisions before parallel source work. Assign explicit module ownership and preserve shared workspace edits.
2. Select a tracer bullet: the smallest complete user-visible path through the real entrypoint, core behavior and persistence/integration boundary. Define its criterion and verification before implementing. Follow with vertical slices that respond to observed behavior rather than horizontal batches of hypothetical tests.
3. Order work by dependencies and risk. Research uncertain external API/tool facts against primary sources, record the conclusion and affected design assumption, then return to the same plan. Existing repository modules and conventions come first.
4. Parallelize only independent scopes with settled interfaces and available host capacity. A coordinator never delegates itself recursively; fresh implementer/reviewer/fixer identities and the run-wide two-fix budget remain intact.
5. Keep requirements and criterion IDs traceable to tasks, handoffs and independent checks. Record blocked prerequisites separately from defects. Large work may have milestones but every completed slice must be reachable, tested and reviewable; unfinished milestones are not delivery success.

A targeted bug fix can use one slice. A complex approved design may need multiple dependency-ordered slices; its canonical criteria remain in the validated design payload. An engineering review stays a review and creates no implementation plan unless requested.