Architecture Decision Records¶
Each ADR captures one significant decision: its context, the choice made, and the consequences. ADRs are immutable once accepted — supersede rather than edit.
Format: MADR-style lightweight records.
| ADR | Title | Status |
|---|---|---|
| 0001 | Monorepo structure (backend + frontend + docs) | Accepted |
| 0002 | Native unified LLM adapter over LangChain/LlamaIndex | Accepted |
| 0003 | Local-LLM-first with Ollama; cloud providers opt-in | Accepted |
| 0004 | Data-infrastructure engine choices (DuckDB/Qdrant/BM25/RAPTOR) | Accepted |
| 0005 | RAG retrieval, re-ranking, and memory layering | Accepted |
| 0006 | Orchestrator engine — tools, agents, routing, observability | Accepted |
| 0007 | Canvas UI and live run streaming (React Flow + Redis Streams) | Accepted |
| 0008 | Fine-tuning control panel (PEFT/TRL, subprocess jobs, registry) | Accepted |
| 0009 | Project import & auto-improvement (analysis + LLM review + apply) | Accepted |
Statuses¶
Proposed → Accepted → (Deprecated | Superseded by ADR-NNNN).