Bernt
f05fded74e
- Added Step 7: Learning (feedback loop from Business Impact to Intelligence) - Control Intelligence definition: LandveX produces Control Intelligence, not AI - Three target customer cases defined: 1. Municipality — Inspect or wait? (Maintenance prioritization) 2. Property Owner — Repair now or plan later? (Cost vs risk) 3. Contractor/Operations — Which action first? (Operational planning) - Validation requirements: Run each case through full pipeline, document breaks, revise only after data contradicts model - Communication principle: Observation → Analysis → Recommendation (AI is implementation, recommendation is product) Rationale: Stop modeling, start observing. Model changes when data contradicts it, not before. Three real customer cases before freezing.
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.