compose-frozen-templatelisted

# compose-frozen-template Stand up an entire structure by **composing** it from the Frozen Template Constructor — a small basis of vetted frozen bricks, assembled by **file copy + token substitution, no code generation**, so any model produces the same result in seconds. Full strategy: `CRUD-DOCS/workspace-standards/frozen-template-constructor.md`. This skill is **self-sufficient**: plain file operations plus one HTTP GET. It does NOT depend on Hermes, memory, or any other agent. ## The mental model (read this before acting) - The constructor is a **composer over a basis of primitives** — not a catalogue of finished templates, and not a code generator. - **Two-Slot Law:** every property is either a **list provider** (where the children come from — Slot A) or a **uniform aspect** (a rule applied identically at every level — Slot B). Nothing else. They never interact. - **Base axes select a primitive:** `source` (files | db-at-build | runtime) × `depth` (1–4) × `rendering` (static | dynamic-descriptor). **Aspect axes** are toggles a primitive supports: `i18n`, `roles`. - Today the basis has **one** harvested brick: `files-depth1` (a flat, file-backed, multilingual list — news / blog / docs feed). Everything else is roadmap. ## Decision flow (do exactly this) 1. **Project the request onto the envelope axes.** What is the data source? how deep is the structure? static or inherently dynamic? which roles? which languages? 2. **Match by 100%-fit.** Call `owner_t