# Site-owned components

Build site-owned components from the selected template direction, visitor tasks, verified business facts, storyboard, edited copy, and inspected media. Author semantic HTML and scoped CSS under `components/`; use the selected theme consistently across routes. Reuse tested behavior and tokens when they fit the planned composition.
When `composition-v1` is selected, record consequential relationships and observable outcomes in the storyboard composition extension. Put stable `data-composition-element` IDs on significant planned elements and record consequential choices in `agent/decisions/authoring-decisions.json`, including lessons applied, adapted, or declined and examples actually inspected.

Inspect production-compiled homepage and interior pages at wide and narrow widths. Preserve factual accuracy, reading order, focus, reflow, reduced motion, and usable fallback. Repair visible failures while preserving successful identity choices. A rationale cannot approve a render.