blueprint-standardslisted

# Blueprint Standards ## Purpose Blueprint artifacts define the **structural foundation** that prototypes and UI specifications build upon. They bridge the gap between validated opportunities and tangible product design. Blueprint artifacts answer: "What pages exist, how do users move between them, what data lives where, and what does the product feel like?" ## Artifact Overview | Artifact | Question It Answers | Template | |----------|-------------------|----------| | Information Architecture | What pages exist and how are they organized? | `references/ia-template.md` | | User Flows | How do users move through the product to achieve goals? | `references/flow-template.md` | | Content Model | What data types exist and how do they relate? | `references/content-model-template.md` | | Brand Direction | What does the product look and feel like? | `references/brand-direction-template.md` | | AI Interaction Model | How does the user interact with AI features? | `references/ai-interaction-model-template.md` | ## When Blueprint Artifacts Are Required Blueprint artifacts provide the structural context that makes prototypes coherent across multiple hypotheses. Create them before generating prototypes. ## Relationship to Other Artifacts ``` docs/product/vision.md ← Strategic intent docs/product/design-principles.md ← Trade-off resolutions docs/product/personas/ ← Who uses it docs/discovery/opportunities/ ← What problems to solve docs/discovery/h