Bernt
eae6c58d66
- Reality Engine: capture reality → observations - Knowledge Engine: understand meaning → evidence, findings - Decision Engine: make actionable → decisions, recommendations - Mission Engine: determine what to collect → missions, gaps - Economic Engine: manage budgets → credits, ROI - Learning Engine: continuously improve → better models - Platform Orchestrator: coordinates via events Key principles: - Each engine independently versioned - Engines never call each other directly - All communication via events - Dashboard shows results, not engines - Intelligence Lab tests engines, not platform Next: PR-005A — Mission Import UI for MVP-0
1.1 KiB
1.1 KiB
ADR-013: Engine Architecture
Status
Accepted
Context
LandveX has grown from a collection of components to a platform. We need clear responsibility boundaries.
Decision
Organize LandveX into six autonomous engines:
- Reality Engine — capture reality
- Knowledge Engine — understand meaning
- Decision Engine — make knowledge actionable
- Mission Engine — determine what to collect next
- Economic Engine — manage budgets and ROI
- Learning Engine — continuously improve
Platform Orchestrator coordinates via events. Not AI. Not Dashboard.
Key Principles
- Each engine independently versioned
- Engines never call each other directly
- All communication via events
- Orchestrator decides flow
- Dashboard shows results, not engines
Consequences
Positive
- Clear responsibility boundaries
- Independent development and scaling
- Easier testing
- Better fault isolation
Negative
- More complex event handling
- Need orchestrator
- Potential latency between engines
Related
- ADR-011: Four-Layer Data Architecture
- ADR-012: Economic Engine
- LANDVEX_ENGINE_ARCHITECTURE_v1.0.md