Bernt
ff136e8aae
- Six layers (added Evidence between Observation and Finding): 1. Reality 2. Observation 3. Evidence (linked observations with context) 4. Finding 5. Decision 6. Business Impact - Decision Object restructured: 1. Decision — what should user decide? 2. Why — why system recommends this 3. Evidence — what observations support this 4. Confidence — how certain (3 dimensions) 5. Consequence — what if nothing done 6. Action — next step 7. Business Impact — economic/operational meaning - Confidence Model (3 dimensions): - Observation Confidence: how certain is detection? - Evidence Strength: how strongly supported? - Recommendation Confidence: how certain is recommendation? - Explainability Principle: - Every Decision Card must be explorable - User can click: Decision → Finding → Evidence → Observations → Reality - Competitive advantage: traceability to source material - Business Impact Model (4 dimensions): - Risk, Cost, Time, Opportunity - Three validation scenarios: 1. Road Crack — simple, common 2. Damaged Facade — complex, critical 3. Broken Road Sign — simple, regulatory - Pass criteria: Same Decision Object works for all three Rationale: Decision Intelligence, not BI. Evidence-backed decisions are the core product. Explainability is competitive advantage. Validation against real scenarios 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.