Bernt
5beb8fb640
- LANDVEX_DESIGN_CONSTITUTION.md: - Added §0a: Capability Parity Principle - All user functions must work on smartphone - Desktop may enhance, never require - Two-question rule for every new feature - Desktop as enhancer (not exclusive) - Examples: Payments, History, KYC - Verification checklist for every new feature - RFC_DEFINITION_OF_DONE.md: - Added criterion #3: Capability Parity - Can be used on smartphone; desktop is enhancement - Total criteria: 14 (was 13) - Exit criteria: must pass all 14 Rationale: quiXzoom targets field workers. Phone is primary or only computer. Phone must always be a full client. Desktop is a more comfortable workspace for some tasks, not a prerequisite. This is a constitutional principle, not implementation.
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.