Accepted architecture decisions
This page mirrors only entries marked Accepted in the repository ADR index as of 2026-08-21. Proposed and Superseded records are intentionally omitted. Open the authoritative index.
| ADR | Decision |
|---|---|
| 014 | Cortxt Product Vision and First User (F0) |
| 015 | Cortxt First Wedge and Product Surface (F1) |
| 016 | Agent Platform bounded context, InferencePort and provider-assurance |
| 017 | Agent Platform — reasoning core accepted as tracked architecture |
| 018 | Workflow-state carrier — GitHub Issue labels |
| 019 | Coding execution — permanent multi-engine routing, not Pi/Hermes replacement |
| 020 | Proof environment naming — redact product/partner name from public surface |
| 021 | Reopen ADR-015 for v.02 admin surface + widget UI (F2 treatment) |
| 022 | Phase 3 v0.1 — capability manifest shape and engine-selection criteria |
| 023 | Cortxt supports both bottom-up and top-down integration, not one exclusively |
| 024 | External integration surface takes the form of an MCP server |
| 025 | Geometric Reasoning’s decisive vs. diagnostic metrics (§27 #8) |
| 026 | Engine adapter-registry (Cordis-inspired DI) kept separate from route()’s selection |
| 027 | EngineContext adopts the service-broker pattern (Cordis §6.2), not exclusive binding |
| 028 | Orchestrator multi-engine resume via opaque per-adapter session_id, CodexAdapter added |
| 031 | Open-source license — Apache-2.0 |