technical-designlisted

# Technical Design Convert accepted requirements into the technical design. Nothing here invents business scope, and nothing here starts while a clarification question or a required decision record is open. ## Dispatch One synchronous `Agent`-tool call, `subagent_type: solution-architect`, with `db-administrator` named in the prompt as the supporting lens for schema design and data-ownership boundaries. ## Required inputs - `planning.md`. - finalize-promoted-knowledge output with no unresolved questions. - `design-system.md` and approved prototypes from detailed-prototypes, when the target has a UI surface in scope. ## Required outputs (all mandatory) - `design.md`. - Integration boundaries. - Required diagrams — at minimum a sequence diagram for any cross-component, asynchronous, or authorization-sensitive flow. - NFR review with explicit tradeoffs. ## Security checks (required within this action) - Auth-boundary review. - Tenant-isolation review. - Application-security-standard mapping (e.g. OWASP ASVS as an evaluation input). ## Rules — the decision-record gate - If this change implies a system-wide decision — an architecture change, a migration, a cross-cutting concern — technical design must not begin until an Architecture Decision Record is drafted, reviewed, and its lifecycle status genuinely flipped to Approved, verified by reading the ADR file itself, never accepted from a self-report. Carry the ADR's path and Approved status in this action's own output so