Registry stack documentation: machine-readable Markdown.
Index of all pages: https://docs.registrystack.org/llms.txt
Full corpus: https://docs.registrystack.org/llms-full.txt

# Advanced operations

> Cross-product operator procedures for credentials, trust material, runtime inspection, retained state, and audit evidence.

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

- [Rotate credentials, keys, certificates, and trust](rotate-credentials-and-trust/)

## State and runtime

- [Inspect and diagnose a running deployment](inspect-and-diagnose/)
- [Retention and persistent state](../retention-and-persistent-state/)
- [Verify and interpret the Evidence Gateway audit chain](../evidence-audit/)

## 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](../relay/) carries that procedure and its rollback
condition.

{/* Evidence: crates/registry-relay-v2/src/startup.rs serve(): "Configuration and
    package state never reload in place." One package per process. */}

## Next

- [Validate your project](../../verify/)
- [Understand generated files](../../generated-artifacts/)
- [Review the security guidance](../../security/)