1. 01

   The idea gets argued before it gets written

   Before any spec the idea is argued and defended: what it solves, for whom, under what constraints, with what architecture and at what cost. That argument produces a written concept, not a hunch.

2. 02

   The SDD answers with questions

   The first spec is never treated as final. The process hands back what was not considered: gaps, contradictions, edge cases, pending calls. Only once those are settled does the proposal come out, and everything else grows from it.

3. 03

   Modules and slices

   The plan is cut into modules, and each module into small, verifiable slices. Not bureaucracy: it is being able to say at any moment what is done and what is left, in a kind of work where losing the thread is easy.

4. 04

   One SDD per module

   None gets improvised: contracts, dependencies, edge cases and what will count as done are set before execution starts. Agents run inside those limits, and they are not the ones who set them.

5. 05

   Judges and tests

   Nothing is accepted because it looks right: every slice has to meet its criteria, pass its tests and survive a review. If it does not pass, it does not matter who wrote it.

The tool executes. The decisions are not delegated.