ARCHITECTURE DECISION RECORDS / MASTER
Decisions form the architecture.
The 26 ADRs are not an unordered document pile. They define a dependency path from client contract to policy, transport, durability, and operational evidence. Browse the path first, then open the exact source decision.
DECISION DEPENDENCY / READING ORDER
Read causes before implementations.
A useful architecture review asks five ordered questions. The answer to each constrains the decisions that follow it.
- 01Client contract
Define what callers may name and what remains below the boundary.
- 02Policy and placement
Define ownership, admission, locality, and the control-plane authority.
- 03Transport and offload
Define how bytes move, how congestion is bounded, and what DPUs may mediate.
- 04Durability and failure
Define acknowledgement, mirror independence, recovery, and degraded behavior.
- 05Evidence and operations
Define what proves capability, health, rollback, and restored protection.
26 of 26 decisions visible
Hot KV and Prefix Cache Data Plane
Makes Coherence-CE the exclusive logical boundary for hot KV and prefix-cache state, including hit, hydration, recompute, and durable-fetch behavior.
Decision surface
This record is part of a layered system. Its concern is kept explicit so client contracts, memory placement, transport, offload, persistence, and operations can change without collapsing into one implicit implementation.
Open source files
Nearby decisions
This browser provides a moderated, searchable summary. GitHub remains the canonical source for exact decision status, context, constraints, and revisions.