Bernt
70a625510b
- JOURNEY_PRINCIPLE.md (v1.0, LOCKED): - Five phases: Discover, Capture, Process, Outcome, Manage - Maps to both quiXzoom and Landvex - Screen mapping table - Balance check reveals Capture/Process/Outcome are empty - Verification: every screen must belong to a phase - EXPERIENCE_AUDIT_QA.md updated: - Screen 3 renamed: Public Map -> Mission Marketplace - Added Phase column: Discover - One-Sentence Test updated: which missions not how much - Added Journey Principle reference - Screen 4: Dashboard (Landvex) - awaiting screen - Screen 5: Results/Decision View (Landvex) - awaiting screen - Next: Landvex Dashboard audit (stresstest for Foundation v1.0) Rationale: Journey Principle prevents screens from floating without context. Mission Marketplace better reflects the page's purpose. Dashboard is the most complex screen - best stresstest for principles.
Landvex Design System
Documentation Structure
docs/design/
├── README.md # This file
├── COMPLIANCE_MATRIX.md # Component readiness tracking
├── LANDVEX_DESIGN_CONSTITUTION.md # UX principles (Level 3)
├── LANDVEX_DESIGN_SPECIFICATION.md # Technical contract (Level 5)
├── foundations/ # Frozen foundations
│ ├── FOUNDATIONS-v1.0.md # Freeze contract
│ ├── TOKEN_PHILOSOPHY.md # Token rules
│ ├── SEMANTIC_COLOR_SYSTEM.md # Color tokens
│ ├── GRID_ELEVATION.md # Layout & depth
│ ├── AI_DESIGN_PRINCIPLES.md # AI governance
│ ├── COMPONENT_TEMPLATE.md # RFC template
│ ├── RFC_DEFINITION_OF_DONE.md # Quality gate
│ ├── DESIGN_ANTI_PATTERNS.md # Forbidden patterns
│ ├── COMPONENT_DECISION_TREE.md # Selection guide
│ ├── GLOSSARY.md # Common language
│ ├── BRAND_PALETTE.md # Brand colors
│ └── RELEASE_DEFINITION.md # Release gates
├── components/ # Component RFCs
│ ├── RFC-002-Input.md
│ ├── RFC-003-Select.md
│ └── RFC-004-Card.md
└── platform/ # Cross-cutting governance
└── README.md
Status
Foundations v1.0 — FROZEN
Components build on foundations. Foundations do not change without v2.0 RFC.