Bernt
8ee9965378
- EXPERIENCE_AUDIT_QA.md (v1.0, DRAFT): - Audit framework: 6 questions per screen - Screen 1: quiXzoom Onboarding — 3s ✅, R→D ⚠️, Decision ✅ - Issue: 'kr' used instead of USD/EUR (Valutaregel violation) - Issue: Launch date creates hesitation - Screen 2: Landvex Process — 3s ✅, R→D ✅, Decision ✅ - Issue: Technical terms in step descriptions - Action items: currency update, date removal, verb simplification - Next screens: Dashboard, Map View, Search, Mission Details, Results - COMPONENT_MATURITY.md (v1.0, LOCKED): - Three levels: Foundation → Validated → Canonical - Foundation: RFC approved, passes 13 DoD criteria - Validated: used in 3 real screens, passes Experience Audit - Canonical: used in 5 screens, 2 sprints stable, other components inherit - Promotion process with verification requirements - Current status: all 4 components at Foundation level Rationale: Observe first, standardize second. Components become Canonical only after proving value in real screens. Experience Audit identifies gaps before building components. Maturity model prevents premature standardization.
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.