architecture

Walk the four decisions in order — repo shape, tech stack, where the v0 runs, and v0 data strategy — and write each as one file at docs/product/adr/NN-<slug>.md using the ADR template. Each ADR needs context, a decision, at least one real alternative, consequences, and a revisit-when trigger.

Four decisions: repo shape (one repo or monorepo, which surfaces exist), tech stack per surface, where the v0 runs (local-first by default), and the v0 data strategy (real integration versus mocked API-shaped data). Each constrains the next, so they are answered in that order.

Human ratification is required when a decision costs money, commits to a paid tier or vendor, forecloses an expensive-to-reopen option, contradicts a project binding, rests on a finding rated expensive or unknown, or picks a data strategy for a job whose value is live data.

Precedence is project binding > team default > ask. A fact in the target's A-Team Config or Technical context binds first; a Declared default applies openly with a confidence-stamped assumption; otherwise the question goes to the human with a recommendation.

Do not use it for component or schema design, API contracts, library-level picks inside an already-settled stack, or implementation work. Those belong to the specification and development phases; this Skill only decides the v0's overall shape.

The decision is not written as active. Its question goes to context.md's Awaiting answers section, the ADR lands with status: parked holding the draft and alternatives, and an open question is logged in research-plan.md while other decisions proceed.