Architecture Decision Records
Architecture Decision Records (ADRs) document significant technical decisions made during the development of the Loop comms platform. Each ADR captures the context, decision, and consequences of a choice.
All ADRs are stored in the docs/decisions/ directory of the repository.
ADR Index
| # | Title | Status | Link |
|---|---|---|---|
| 0001 | Knock Disposition — Keep vs Absorb into Platform | Decided | View |
| 0002 | Blooio Disposition — Keep vs Migrate to Twilio | Decided | View |
| 0003 | Klaviyo Retirement Timeline | Decided | View |
| 0004 | Gorgias Disposition — Keep vs Absorb | Decided | View |
| 0005 | Recharge Disposition — Stays Out vs Webhook-Feeds Platform | Decided | View |
| 0006 | Email Provider Split — Postmark + Resend | Decided | View |
| 0007 | Notification Preferences — comms.consents as Source of Truth | Decided | View |
| 0008 | Email Suppression — comms.suppressions as Source of Truth | Decided | View |
| 0009 | Unified Dedup Key Pattern | Decided | View |
| 0010 | Template Rendering Convergence | Decided | View |
| 0011 | Central Log Sink — Axiom | Decided | View |
| 0012 | Tracing Backend — Axiom Tracing | Decided | View |
| 0013 | Developer Docs Site — Keep Fumadocs | Decided | View |
| 0014 | Secrets Management — Doppler | Decided | View |
| 0015 | AI Eval Framework Hosting — In agent-core | Decided | View |
| 0016 | marketing-comms Project Disposition — Absorbed into Platform | Decided | View |
| 0017 | calls.customers Table Preserved | Decided | View |
ADR Format
Each ADR follows this structure:
- Title — Short descriptive name
- Status — Proposed, Decided, Superseded, or Deprecated
- Context — The situation and forces at play
- Decision — What was decided
- Consequences — What happens as a result (both positive and negative)