Bernt
9a817ac82a
- Added architecture diagram: - Developer UI / Training API / Experiment API - Event Bus / Queue - Storage Layer (S3/R2 + PostgreSQL + Neo4j) - Processing Pipelines - Seven separate pipelines (not one big AI loop): 1. Ingestion — raw images/video/GPS/EXIF → Raw Dataset 2. Dataset — sort, deduplicate, quality control → Validated Dataset 3. Annotation — AI suggestions, manual correction → Verified Dataset 4. Training — hyperparameters, checkpoints, GPU → Model Artifact 5. Evaluation — precision, recall, F1, decision accuracy → Report 6. Replay — compare model versions → Regression Report 7. Decision Validation — full chain → Validation Report - Bucket structure: raw-images, raw-video, missions, datasets, annotations, training, models, replays, evaluation, decision-cases, field-trials, exports, archives - AI Job Queue: all jobs asynchronous (Upload → Queue → Worker → GPU → Storage → Notification) - Core principles updated: - All artifacts immutable and versioned - Every change traceable to experiment, model, dataset, decision - Dashboard shows: Datasets (Healthy/Needs Review/Corrupted), Training Jobs, Decision Cases, Replay Jobs - Decision Cases emphasized as most important asset Rationale: Separate pipelines make system easier to debug, improve, and swap components. Immutability aligns with E-001 Git/traceability principles. Decision Cases become the unique asset over time.
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.