Unreleased documentation. These pages follow the main branch and can change before the next release. For supported guidance, use v0.26.1.
Use these task guides once a deployment is running and the per-product operations guides are familiar. Each guide names the evidence to retain, the limit of each gate, and a recovery path. They cut across products; the procedure for one service does not grant authority over another.
Configuration and trust
Section titled “Configuration and trust”State and runtime
Section titled “State and runtime”- Inspect and diagnose a running deployment
- Retention and persistent state
- Verify and interpret the Evidence Gateway audit chain
Where Relay changes happen instead
Section titled “Where Relay changes happen instead”Registry Relay serves one Registry per process from one sealed package. There is no second serving lane, no partial activation, and no runtime switch that changes what a package means. A change to resources, operations, access profiles, classifications, or disclosure is a new complete revision: the publisher reseals, the operator starts a candidate on a private listener, waits for readiness, shifts traffic, and drains the previous process. Operate Registry Relay carries that procedure and its rollback condition.