Architecture Decisions - joeroberts/release-radar GitHub Wiki

Architecture decisions do not authorize work. Accepted status does not by itself establish current applicability, and historical records do not override current instructions.

ADR	Decision status
ADR-001 — Release Radar boundaries	Accepted
ADR-002 — Codex plugin lifecycle	Accepted
ADR-003 — Active-phase selection	Accepted
ADR-004 — Delivery Goals and phase-plan readiness	Accepted
ADR-005 — Ticket task work plans	Accepted
ADR-006 — Managed repository documentation contract	Accepted
ADR-007 — Proportional Delivery Validation	Accepted
ADR-008 — Opt-in project execution	Accepted
ADR-009 — ADR lifecycle and integrity	Accepted
ADR-010 — Scoped development exceptions	Accepted
ADR-011 — Folder Authorization Recovery	Accepted
ADR-012 — Portable Project Archive V1	Accepted
ADR-013 — Project Continuity and Read Only Publication	Accepted
ADR-014 — Ticket Goal Identity	Accepted
ADR-015 — Unavailable Live Codex Observation	Accepted
ADR-016 — Planning Views and First Ticket Placement	Accepted
ADR-017 — Revision Specific Document References	Accepted
ADR-018 — Saved Additive Planning Proposals	Accepted
ADR-019 — Retained Successors and Carried Obligations	Accepted
ADR-020 — Explicit Phase Lifecycle	Accepted
ADR-021 — Event Time History	Accepted
ADR-022 — Revision Bound Delivery Evidence	Accepted
ADR-023 — Generic Task Adoption	Accepted
ADR-024 — Workspace Search and Saved Queries	Accepted
ADR-025 — Fixed Plugin Sandbox and Legacy Migration	Accepted
ADR-026 — Plugin Repository Handoff and Integrity	Accepted
ADR-027 — Exact Plugin Capability Recognition	Accepted
ADR-028 — Project Dependency Navigation	Accepted
ADR-029 — Read Only Documentation Diagnostics	Accepted
ADR-030 — Historical Task Based Development Policy	Accepted
ADR-031 — Permanent Removed Registration Purge	Accepted
ADR-032 — Repository Plan Reconstruction and Preparation	Accepted