HSDD Spec: Recursive Node Decomposition

Decompose a system into a tree of spec nodes. The same operation runs at the root (a brain-dump becomes a high-level spec) and at any internal level (a node splits into child nodes). This is the front-end of Hierarchical Spec-Driven Development (HSDD).

Core principle: Each node is a function with typed inputs and outputs (the contracts it consumes and produces); the dependency DAG is the composition. Internals are private. A node is developed against contract values, never against the live implementations behind them. This is dependency rejection at the architecture level.

When to Use

• Root: a brain-dump, product idea, or "write a high-level spec" request.
• Internal node: "break down @hsdd/spec/{node}.md into ..." or "decompose {node} into ...". Treat the named node as the parent and emit one child node spec each.
• Multi-level: repeat at each level until a node is small enough to phase.