Operations runbook
Operations-facing pages: how to bring a vault up in order with checks at each step, and the errors operators actually meet, each with its cause and fix. The startup checks on these pages are executed against a real deployment by the vault's own test gate — the runbook is verified, not aspirational.
- Startup sequence — from empty machine to signed-in vault, with health checks
- Troubleshooting — common errors with fix steps
- Provisioning a clientadmin — how an administrator creates a delegated compartment administrator, and what that account can then do
- Connecting a remote agent — registering an agent client, granting it compartments, and exchanging its credentials for the short-lived bearer token it uses to query the vault over the network
- Demonstration installation — one command for a complete, populated, deliberately weak demo vault: what it makes, what it weakens, what it refuses without, and how long it takes
- From a demonstration vault to a production one — the supported conversion: what comes out of the environment file, what is rotated, what the reinstall destroys, and why there is no way back
- Using a GPU for the models — optional and off by default; what to install on the host, the one setting that turns it on, and why the vault refuses to start rather than fall back to the CPU in silence
- The GPU gateway — for a model runtime on a host this vault does not own: what the vault presents on each road, what the gateway must verify, what it must never log, and how the credentials rotate
- Sizing the datastores — what the two Postgres instances are given on this machine, what to raise when, on what evidence, and what raising it costs; written for an operator with no database administrator to ask
- Presenting the demonstration — what to show and in what order, with the click paths, plus sample questions that need more than one document to answer