Architecture Decision Records¶
Architecture Decision Records (ADRs) capture significant, hard-to-reverse decisions about the Sandloom framework — the context that forced the decision, the decision itself, and its consequences. They are living documents: superseded ADRs are kept for history and marked accordingly.
| ADR | Title | Status |
|---|---|---|
| 0001 | Framework distribution & packaging | Accepted |
| 0002 | The framework absorbs per-module boilerplate | Accepted |
| 0003 | Fewer synchronous RPC calls in split deployments — membership reads first | Proposed |
| 0004 | Internal RPC request authentication with per-pair HMAC keys | Accepted (draft) |
| 0005 | One effect model — guarantees, the dedupe record and the commit pipeline | Accepted |
| 0006 | One accepted-risks list instead of prod opt-out flags | Accepted |
| 0007 | Kernel layers and an acyclic kernel, enforced by import contracts | Accepted |
| 0008 | Sagas — a small orchestrator over the existing effect primitives | Accepted |
| 0009 | Route policy follows authority and effect: deny-by-default, live sessions, no route classes (amends 0003) | Accepted |
| 0010 | Public API 1.0 — one sandloom.sdk namespace, three API levels, derived declarations (amends 0005, 0007, 0009) |
Proposed |
| 0011 | The driver API — two doors for one contract, drivers found by name | Accepted |