# 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:

1. **Reality Engine** — capture reality
2. **Knowledge Engine** — understand meaning
3. **Decision Engine** — make knowledge actionable
4. **Mission Engine** — determine what to collect next
5. **Economic Engine** — manage budgets and ROI
6. **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