Architecture Decision Records
Architecture Decision Records describe accepted Tosumu architecture and the consequences of that choice. They are concise decision records, not design journals or implementation plans.
When To Add An ADR
Add or supersede an ADR when Tosumu accepts a durable decision about:
- crate or subsystem ownership;
- dependency direction;
- on-disk compatibility or migration policy;
- public provider or consumer boundaries;
- security, integrity, durability, or recovery guarantees;
- an architectural proposal concluded by an Architectural Review.
Use ADR-NNNN-short-title.md. Numbers are never reused. Accepted decisions
remain in history when superseded.
Index
- ADR-0001: Storage Engine Layer Boundaries
- ADR-0002: Authenticated Pager Trust Boundary
- ADR-0003: Source Unit Cohesion, Size Pressure, And Decomposition -- uses ownership and conservation evidence to guide extraction, including narrow private seams for credible future implementation variation.
- ADR-0004: Cooperative Single-Writer Admission
- ADR-0005: Committed Generation And Retained-WAL Snapshots
- ADR-0006: Shared KV Store And Snapshot Transactions
- ADR-0007: Database-Generation Conditional Writes
- ADR-0008: SQL-Owned Secondary Index Keyspaces
- ADR-0009: Offline VACUUM Rebuild Publication
- ADR-0010: Private Format-v3 Cryptographic Mechanism Seams