Architecture Decisions

Architecture Decision Records (ADRs). Status values: Proposed, Accepted, Rejected, Deprecated, Superseded.

• ADR-0001: Sphinx and reStructuredText for Project Documentation
• ADR-0002: Go Services and a Svelte Web UI
• ADR-0003: Orchestrate Existing Coding Agents Through Runtime Adapters
• ADR-0004: Tenancy Model — Organization, Customer, Project
• ADR-0005: Knowledge as a Separate Service with an MCP Interface
• ADR-0006: OIDC Claims-Based RBAC for Humans, Scoped Run Tokens for Agents
• ADR-0007: Code Review on Git Platforms via Forge Adapters
• ADR-0008: Configurable Review and Merge Policy per Ticket
• ADR-0009: Devcontainer per Run on Docker or Podman
• ADR-0010: Central Skill Registry
• ADR-0011: LLM Gateway for Credentials and Usage Metering
• ADR-0012: PostgreSQL for Core and Knowledge
• ADR-0013: Planner Runs as a Containerized Agent
• ADR-0014: Separate Agent Session per Pipeline Stage
• ADR-0015: Question Escalation Through the Planner
• ADR-0016: Durable Orchestration in the Database
• ADR-0017: Pipelines Defined per Project
• ADR-0018: REST for Stateless, WebSocket + JSON-RPC + MessagePack for Stateful
• ADR-0019: SQLite First, rqlite Later
• ADR-0020: Planner Runs In-Process in Core
• ADR-0021: Hybrid Vector Search over All Content
• ADR-0022: Humans Reach Knowledge Through Core
• ADR-0023: Process Backend for Development
• ADR-0024: Authentication Off by Default for a Single Local User
• ADR-0025: Agent Fleet Runs Sessions as Processes
• ADR-0026: Interactive Sessions That Park When Idle
• ADR-0027: Tenancy Model — Platform, Organization, Project
• ADR-0028: The Feature Map — Features as a Versioned Graph in Core