Accepted decisions are append-only. Supersede an ADR with a new record rather than rewriting history.
| ADR | Decision | Status | Date |
|---|---|---|---|
| 0001 | Record architecture decisions | Accepted | 2026-07-16 |
| 0002 | No service registry | Accepted | 2026-07-16 |
| 0003 | RS256 access tokens with JWKS | Accepted | 2026-07-16 |
| 0004 | Transactional outbox with polling publishers | Accepted | 2026-07-16 |
| 0005 | Idempotent consumers with processed-event ledgers | Accepted | 2026-07-16 |
| 0006 | Sales inventory saga orchestration | Accepted | 2026-07-16 |
| 0007 | Domain services validate JWT via Identity JWKS | Accepted | 2026-07-16 |
| 0008 | Authoritative Inventory reservation reconciliation | Accepted | 2026-07-20 |
| 0009 | Persisted assistant and same-origin web boundary | Accepted | 2026-07-22 |
| 0010 | OpenTelemetry observability stack | Accepted | 2026-07-22 |
| 0011 | Maven and pnpm monorepo | Accepted | 2026-07-23 |
| 0012 | Database per service | Accepted | 2026-07-23 |
| 0013 | Kafka for domain event communication | Accepted | 2026-07-23 |
| 0014 | API gateway and same-origin browser edge | Accepted | 2026-07-23 |
| 0015 | Authenticated MQTT for IoT ingestion | Accepted | 2026-07-23 |
- Copy the template.
- Use the next four-digit number and a descriptive kebab-case name.
- Include context, decision, consequences, alternatives, trade-offs, and evidence links.
- Mark the record
Acceptedonly after implementation and verification agree.