bts-wireframelisted

# Wireframe: System Structure Design Design the high-level structure for: $ARGUMENTS ## Prerequisites 0. **Resolve recipe ID**: If `$ARGUMENTS` is empty, run `bts recipe status` to find the active recipe. Use its ID for all `{id}` references below. 1. Read research output: - `.bts/specs/recipes/{id}/research/v1.md` (or latest) - `.bts/specs/recipes/{id}/scope.md` - `.bts/specs/recipes/{id}/domain.md` — the invariant-ownership contract every component responsibility must honor - `.bts/specs/project-map.md` (existing system structure) - `.bts/specs/layers/{name}.md` for affected layers (existing models, APIs, patterns) 2. **Architect decision check**: wireframe.md should already START with the `<!-- architect-decision -->` block committed by `/bts-architect`. - Block present → design the SELECTED decomposition. Never overwrite the block: use Edit to add content BELOW it, not Write on the file. - Block missing → STOP and run `/bts-architect` first (`bts verify wireframe.md` raises missing_architect_decision_block as major otherwise). ## Step 1: Component Diagram Identify the main modules/packages/files and their relationships. Express as a mermaid flowchart: ```mermaid flowchart TD A["module-a\n(responsibility)"] --> B["module-b\n(responsibility)"] A --> C["module-c\n(responsibility)"] B --> D["shared/types\n(data definitions)"] C --> D ``` Rules: - Each node = one file or module with its primary responsibil