Bernt
09f3d2f39d
- Updated audit framework with fixed 6-question matrix: 1. 3-Second Rule: understand purpose immediately 2. Three-Step Rule: Input → Processing → Outcome visible 3. Primary Decision: know what to do 4. Information Hierarchy: most important is largest 5. Cognitive Load: what can be removed 6. Call to Action: clear next action - Added One-Sentence Test: - Can user describe screen in one sentence? - Examples for Onboarding, Map View, Dashboard, Results - Two+ sentences = screen tries to do too much - Added placeholders for next screens: - Screen 3: Dashboard (Landvex) - Screen 4: Map View (Landvex/quiXzoom) - Screen 5: Results/Decision View (Landvex) - Priority order: Dashboard → Map View → Results → Search → Settings - Updated quiXzoom onboarding audit with new matrix format Rationale: Fixed matrix ensures consistent evaluation across all screens. One-Sentence Test reveals overloaded screens. Placeholders ready for next screens. Priority reflects user journey impact.
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.