Docs to Types

Upfront architecture skill for converting clarified prose into typed architecture. If the team knows a durable domain or architecture fact, the type system and module graph should know it too.

Not for general grilling, refactoring review, or the first TDD slice. CONTEXT.md, ADRs, and grill notes are source material, not the final harness.

Prime directive

Do not implement business behavior. Compress approved context into the whole intended typed architecture:

• canonical domain types, schemas, brands, and invariants
• discriminated unions/state models that rule out invalid states
• smart constructors/parsers for values entering from system edges
• service/interface seams using project conventions
• typed result/error families and error translation boundaries
• production/test adapter slots
• composition/layer/module topology using project conventions
• production and test call stacks
• dependency-direction checks where practical