Skip to main content
The station where thinking is cheapest. Design turns a conforming work order into a buildable specification — and writes the gauge before the part exists.

​
Entry gate

A work order that passed Station 0’s schema gate: Why linked to higher intent, testable acceptance criteria, declared family, target cost, named principal.

​
Standard work

Spec and identity are written here — tamazukuri, in the order the manifesto demands:
  • For agents: the soul document before the tools. Identity is a stamped structural part, the first line on the bill of materials — not a coat of paint applied late.
  • For tools: the interface contract before the implementation.
  • For skills: the description-and-boundary block before the procedure.
Then the structural rule that defines this station: the eval is written before the unit. Toyota builds the gauge before the part; eval-driven development — write the eval before the agent can pass it, because eval quality is the ceiling on agent quality — is the same discipline. A unit whose acceptance criteria cannot be expressed as an executable or judge-scorable eval is not underspecified; it is unmanufacturable, and Design is where that gets discovered, not Verify. Design also drafts the bill of materials: which registry parts, which model tier per step, with reuse checked before any new fabrication is authorized — the shelf is searched before the forge is lit.

​
Exit gate

Four checks, all present or the unit stays:
  1. The eval exists and currently fails — red, because the unit does not exist yet. A green eval at Design is a broken eval.
  2. Draft bill of materials: which parts, which model tier per step.
  3. Projected cost within the work order’s target.
  4. For agents: soul and contract documents drafted.

​
Escalation

Unmanufacturability is this station’s discovery, not its failure. When acceptance criteria cannot become an eval, the order returns to intake for sharpening with the principal — block before guess.

​
Enforcement

Row 2 of the compilation table: a gate script — Design cannot exit without a red eval on record. This gate is scheduled in the design’s construction plan (Phase 2, built as the pilot units demand it) and is not yet compiled; until it lands, the check runs as review discipline against the exit list above. This page states the standard; the script, when it lands, merely makes it unskippable.

​
Self-audit

ClaimSource
Tamazukuri ordering: SOUL before tools; contract before implementation; boundary before proceduredocs/factory-design.md:105
Identity is a stamped structural part, first line on the BOMdocs/factory-design.md:79
Eval before the unit; unmanufacturable if criteria can’t become an evaldocs/factory-design.md:107
Exit gate: red eval, draft BOM, projected cost in target, SOUL/CONTRACT drafteddocs/factory-design.md:109
Row 2: gate script “Design cannot exit without a red eval”; compiled JIT in Phase 2docs/factory-design.md:195, 269
Block before guessdocs/factory-design.md:184