ADR index
Grouped navigation for architectural decisions. ADR files remain in chronological order under docs/adr/.
Documentation
Governance for readable, auditable external references in ADRs and docs.
| ADR / doc | Title | Status |
|---|---|---|
| 0011 | Use [web:*] source tags with a central mapping file | Accepted |
| 0012 | Fetch and archive web sources via a focused fetcher | Accepted |
| web-source-mapping | Central registry for [web:NNN] tags | — |
Workflow
| ADR | Title | Status |
|---|---|---|
| 0000 | Establish a2c-workflow as the canonical A2C repository | Accepted |
| 0001 | Shared pre-commit policy for A2C-governed repositories | Accepted |
| 0002 | Standardized changelog and release documentation in A2C | Accepted |
| 0003 | Standardized A2C pre-commit hooks for A2C projects | Accepted |
| 0004 | Standardized CI bump and release flow for A2C projects | Superseded |
| 0009 | Release semantics and commit promotion to master | Accepted |
| 0010 | TestPyPI and PyPI publishing gated by release state | Accepted |
| 0013 | Adoption version record and drift warnings | Accepted |
| 0014 | CLI invocation journal | Accepted |
| 0015 | Bootstrap dev environment and pre-commit hooks | Accepted |
| 0016 | Stack profile plugin protocol in a2c_core | Accepted |
| 0017 | Publishable Python profile and forge-neutral release scaffolding | Accepted |
| 0018 | Legacy repository adoption workflow | Accepted |
Governance
Architecture-significant requirements, decision evolution, and related control points.
| ADR | Title | Status |
|---|---|---|
| 0019 | Architecture Significant Requirements as first-class artifacts | Accepted |
| 0020 | Intent to ASR, ADR, Spec, Contract, and planning governance chain | Accepted |
| 0021 | Amending Accepted ADRs (Amends vs Supersede) | Accepted |
| 0022 | Narrative architecture story per ProductPhase | Accepted |
| 0023 | Pull requests as architecture control points | Accepted |
Product
| ADR | Title | Status |
|---|---|---|
| 0005 | A2C product repository boundaries | Accepted |
| 0006 | Three-package Python structure in a2c-workflow | Accepted |
| 0007 | VS Code extension thin client with bundled platform CLI | Accepted |
Planning
| ADR | Title | Status |
|---|---|---|
| 0008 | Task lifecycle sidecar and immutable task spec | Accepted |
By status
Proposed
(none)
Accepted
- 0000 — Establish a2c-workflow as the canonical A2C repository
- 0001 — Shared pre-commit policy for A2C-governed repositories
- 0002 — Standardized changelog and release documentation in A2C
- 0003 — Standardized A2C pre-commit hooks for A2C projects
- 0005 — A2C product repository boundaries
- 0006 — Three-package Python structure in a2c-workflow
- 0007 — VS Code extension thin client with bundled platform CLI
- 0008 — Task lifecycle sidecar and immutable task spec
- 0009 — Release semantics and commit promotion to
master - 0010 — TestPyPI and PyPI publishing gated by release state
- 0011 — Use [web:*] source tags with a central mapping file
- 0012 — Fetch and archive web sources via a focused fetcher
- 0013 — Adoption version record and drift warnings
- 0014 — CLI invocation journal
- 0015 — Bootstrap dev environment and pre-commit hooks
- 0016 — Stack profile plugin protocol in a2c_core
- 0017 — Publishable Python profile and forge-neutral release scaffolding
- 0018 — Legacy repository adoption workflow
- 0019 — Architecture Significant Requirements as first-class artifacts
- 0020 — Intent to ASR, ADR, Spec, Contract, and planning governance chain
- 0021 — Amending Accepted ADRs (Amends vs Supersede)
- 0022 — Narrative architecture story per ProductPhase
- 0023 — Pull requests as architecture control points