> [!IMPORTANT]
> **AI Assist Note (Knowledge Heritage)**:
> This document is part of the "Sovereign Reality" documentation.
> - **@docs ARCHITECTURE:Core**
> - **Failure Path**: Information drift, legacy terminology, or documentation mismatch.
> - **Telemetry Link**: Cross-reference with `execution/parity_guard.py` results.
>
> ### AI Assist Note
> Automated governance and architectural tracking.
>
> ### 🔍 Debugging & Observability
> Traceability via `parity_guard.py`.


---
name: design-review
description: Iterative feedback loop for design validation.
---

# Design Review Protocol

A structured forum for critiquing visual and interaction design before implementation.

## Architecture

```mermaid
graph LR
    D[Draft Design] --> P[Presentation]
    P --> F[Feedback]
    F -- "Changes Needed" --> I[Iterate]
    I --> P
    F -- "Approved" --> H[Handoff]
```

### 1. Presentation
The designer walks through the flow, explaining the *rationale* behind decisions. Use a click-through prototype if possible.

### 2. Feedback (C.R.I.T.)
- **Constructive**: Help improve, don't just tear down.
- **Relevant**: Stick to the goals of the project.
- **Interrogative**: Ask "Why?" before saying "Change this."
- **Timely**: Give feedback while it's cheap to change.

### 3. Handoff
Prepare the Figma file for engineers (redlines, assets, empty states).

## When to Use
- **Mid-Process**: When the direction is set but details are flexible.
- **Pre-Handoff**: Final check.

## Operational Principles
1. **Problems, not Solutions**: Stakeholders should point out problems ("User won't see this"), not dictate solutions ("Make it blue").
2. **Consolidate**: Synthesize conflicting feedback during the meeting.
3. **Focus**: Don't bikeshed on minor details. Focus on the core user flow.

[//]: # (Metadata: [design_review])
