Architecture Decision Records

Architecture Decision Records (ADRs) capture a significant design decision, the context behind it, and its consequences. They live in docs/adr/ and are the authoritative record of why the system is the way it is — read the relevant ADR before changing the subsystem it covers.

Tip

Proposing a design change? Add an ADR (copy the format of an existing one) so the decision and its trade-offs are recorded alongside the code. Exploratory designs live in docs/design/.

Accepted ADRs

ADR 0001 — Concurrent rotation semantics for SharedStorage The merge rule for concurrent writer-set rotations: causal-first last-writer-wins with a hybrid-clock tiebreak.

ADR 0002 — Fleet TEE leave hygiene (post-eviction cleanup) How a TEE fleet node leaves: key rotation and the post-eviction cleanup that follows.

Related

Protocol Reference

Development workflow