Architecture Decision Records (ADRs)
Architecture Decision Records document the key technical and strategic decisions made during the design of ReGenesis. Each ADR captures the context, the decision, the alternatives considered, and the consequences.
These records serve multiple purposes:
- For Jesse: Understand why each decision was made, not just what was decided
- For engineers: Know the constraints and trade-offs behind the architecture
- For stakeholders: See the deliberate thinking behind the technical strategy
Decision Log
| ID | Decision | Status | Date |
|---|---|---|---|
| ADR-001 | US-First Market Strategy | Accepted | Feb 2026 |
| ADR-002 | SOC 2 Before ISO 27001 | Accepted | Feb 2026 |
| ADR-003 | Anthropic Claude as Primary LLM | Accepted | Feb 2026 |
| ADR-004 | Embrace Therapy Territory | Accepted | Feb 2026 |
| ADR-005 | Evidence Pack Architecture (L0/L1/L2) | Accepted | Feb 2026 |
| ADR-006 | AWS us-east-1 Primary Region | Accepted | Feb 2026 |
| ADR-007 | Field-Level RBAC/ABAC with Visibility Tags | Accepted | Feb 2026 |
ADR Format
Each ADR follows this structure:
- Status: Proposed / Accepted / Deprecated / Superseded
- Context: What prompted this decision?
- Decision: What did we decide?
- Alternatives Considered: What else could we have done?
- Consequences: What are the trade-offs?
- References: Related documents and pages