REQUEST TO EVIDENCE01Ingress02Translation03Coherence04Transport05Persistence

QUESTIONS FROM THE SYSTEM BOUNDARY INWARD

Start with purpose. End with evidence.

A baseline answer explains the purpose and contract. A systems answer explains mechanisms and trade-offs. A deep answer follows completion, failure, tuning, and proof. Filter the same architecture by audience and required depth.

01FoundationPurpose and boundaries
02SystemsMechanisms and trade-offs
03Deep diveCompletion, failure, tuning

AUDIENCE PATHS / SAME SYSTEM, DIFFERENT FIRST QUESTION

Choose the question that makes the system relevant.

The architecture does not change with the audience. The entry point, required evidence, and appropriate depth do.

VIEWING FORAll user experience types

33 questions match this view. Answers link back to the ADRs that carry the exact design context.

It gives inference systems one logical way to find, reuse, move, and durably protect expensive state across memory and storage tiers. The system is designed so client semantics stay stable while pods, fabrics, accelerators, and media scale independently.

RELATED DECISIONSADR-001ADR-002