ADR index8 min read
Architecture Decisions
The decisions behind the open workspace patterns, including what the reference implementation deliberately does not promise.
Why publish decisions?
Patterns are easier to reuse when their boundaries are visible. These ADRs record the reasoning behind the default architecture and make replacement paths explicit.
Decision catalogue
- ADR-001 — System Workspace Has a Git Control-Repository Root
- ADR-002 — Repository Boundaries Remain Independent
- ADR-003 — Context Scope May Exceed Mutation Scope
- ADR-004 — Git Worktree Is the Default Run Isolation
- ADR-005 — Worktree Isolation Is Not Security Isolation
- ADR-006 — Operational State Does Not Belong in Git
- ADR-007 — Durable Engineering History May Be Stored in Git
- ADR-008 — Do Not Store Full Agent Telemetry Permanently
- ADR-009 — Agent Plans Are Private by Default
- ADR-010 — Coordination Intent Is Shared
- ADR-011 — Agents Produce Candidates
- ADR-012 — Integration Is Separate From Execution
- ADR-013 — Scheduled Agents Use Bounded Runs
- ADR-014 — Multi-Repo Atomic Integration Is Out of Scope
- ADR-015 — The CLI Is a Reference Implementation
- ADR-016 — Mechanisms Over Mandatory Policies
- ADR-017 — Agent Workspace Product Boundary
All decisions are accepted for the first documentation slice. A future decision can supersede an earlier one; the history should stay visible.