Bernt
7075cf9ab9
- Session is root (not Mission): Field Session → Mission → Asset → Observation... - Event Sourcing: never overwrite status, status is projection of history - Artifact Registry: first-class object with id, type, version, hash, lineage - Decision Case immutability: Review → Revision → Approved Version (like Git) - Review Task: Assigned → Reviewed → Approved → Closed - Processing Graph: nodes not hardcoded chain, swap models without changing rest - Data Quality as domain: Blur, Duplicate, Bad GPS, Low Resolution, etc. - Decision Case comparison: show exactly what changed, which evidence, model, human - Golden Missions + Golden Datasets: two levels - Domain Event Viewer: timeline (09:42 Mission Created, 09:43 Video Uploaded...) - KPI: Verified Decision Throughput (verified decisions per day) - Architecture Principle: 'Produces verified Decision Cases through reproducible and traceable pipeline' Updated PR-001 Domain Model: - Added FieldSession (root) - Added Artifact interface - Added Event sourcing types - Session ID format: session_YYYYMMDD_NNNNNN - Updated API to include /sessions endpoints Rationale: Three fundamental objects (Session, Artifact, Event) make the rest natural. Scalable, auditable, well-suited for public sector traceability requirements.
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.