How to read these deep dives

For everyone evaluating CryptoRail.

Each deep dive explains one part of CryptoRail: how it works, what it guarantees, what it does not do. They are written for evaluation, not implementation; the developer documentation covers how to build with it.

When a capability is mentioned it carries its status. Most are simply available, for example: Several node endpoints per network: calls go to the first healthy one, an operation stays on the endpoint it started on, and a dead or lagging node is left aside without losing anything.

Some are not, and say so: Signing keys in AWS KMS, with the curve checked at startup. Built, certification pending

flowchart LR
    C[a claim on a page] --> R[the claims registry]
    R --> E[requirement, scenario or decision record]
    E --> T[tests run on every change]