Architecture Decision Records¶
ADRs capture significant technical decisions. Format:
# ADR-NNNN: Title
Date: YYYY-MM-DD
Status: proposed | accepted | deprecated
## Context
## Decision
## Consequences
| ADR | Title | Status |
|---|---|---|
| ADR-0001 | Frontier fallback policy | accepted |
| ADR-0002 | OpenAI-compatible API as primary integration | accepted |
| ADR-0003 | Tool-native execution tier (Lt) | accepted |
| ADR-0004 | Agent tool-call compatibility | accepted |
| ADR-0005 | Python tech stack for MVP | accepted |
| ADR-0006 | Local daemon security | accepted |
| ADR-0007 | Pluggable gateway adapters | accepted |
| ADR-0008 | Developer command rules and context cache | accepted |
| ADR-0009 | Live factual fetch (L2-live) | accepted |
| ADR-0010 | Browser bridge + Google search | accepted |
| ADR-0011 | Pluggable integration provider framework | accepted |
| ADR-0012 | Execution policy (Lt) and CCS cache policy | accepted |
| ADR-0013 | Single-repo monorepo structure | accepted |
| ADR-0014 | Enterprise distributed install, org cache, org learning | accepted |
| ADR-0015 | Local-first product boundaries (scope gate) | accepted |
| ADR-0016 | Relicense the tree to Apache 2.0 | accepted |