Bernt
e3e70c52d4
- Added 7 validation scenarios covering diverse decision types: 1. Road Crack (Maintenance) — repair now or later? 2. Damaged Facade (Safety) — act immediately? 3. Broken Road Sign (Compliance) — violates requirements? 4. Vegetation Blocking Sight (Risk Reduction) — gradual deterioration 5. Parking Area Wear (Investment Priority) — multiple small → big decision 6. Cosmetic Scratch (No Action) — conscious decision to wait 7. Mixed Evidence Sources — photo + sensor + weather API - Decision Invariance Test: - Same Decision Object structure across all scenarios? - No fields added/removed? - No field meaning changes? - Fail = model needs revision - Evidence Variation Test: - Single image, multiple images, video+GPS, historical, external data, mixed - Decision Object structure unchanged regardless of evidence type - Decision Quality Gate: - Verifiable evidence chain - Motivated confidence - Action or conscious 'no action' - Explainability chain works - Pass criteria: All 7 scenarios valid + invariance + evidence + quality gate Rationale: Validate model against diverse decision types before freezing. No action scenario is as important as action scenarios. Mixed evidence sources test robustness. Invariance test ensures generality.
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.