Architecture decision records (ADRs) distinguish approved product boundaries
from proposed implementation choices. Accepted records govern current work;
Proposed records are safe defaults for development but cannot support a
production claim until their open items are resolved.
| ADR | Decision | Status |
|---|---|---|
| ADR-001 | Product scope and intended users | Accepted |
| ADR-002 | Beta data boundary | Accepted |
| ADR-003 | Website and application topology | Proposed |
| ADR-004 | Hosting and data residency | Proposed |
| ADR-005 | Authentication and tenancy | Proposed |
| ADR-006 | Ontario and Canadian source policy | Accepted |
| ADR-007 | Provider-neutral legal research | Accepted |
| ADR-008 | Model-provider controls | Proposed |
| ADR-009 | Logging, audit, retention and deletion | Proposed |
| ADR-010 | AGPL and upstream attribution | Accepted |
| ADR-011 | Accessibility and language expansion | Proposed |
| ADR-012 | Release and source governance | Proposed |
- Accepted: approved and binding until superseded.
- Proposed: recommended default; production dependencies remain open.
- Superseded: replaced by a later ADR, which must be linked.
- Rejected: considered and not adopted.
Copy ADR template for later decisions. Changes to an accepted ADR require a focused pull request, named reviewer, and explicit consequences.