The vault ships its own operations runbook

The runbook pages tell an operator how to bring a vault up, in order,

with a check at each step — and what the errors they will actually meet

mean, each with its cause and its fix. The startup checks are not

prose: the vault's own test gate executes them against every real

deployment, so a runbook page that stopped being true would fail the

build, not the operator.

The startup sequence is documented in order with checks

Given the vault's runbook
When an operator opens the startup sequence
Then the steps appear in dependency order and the checked steps name their checks

Common errors are documented with their causes and fixes

Given the vault's runbook
When an operator opens the troubleshooting page
Then each documented error carries a cause and numbered fix steps

The runbook quotes the errors the vault actually emits

Given the vault's runbook
When an operator searches the troubleshooting page for an error they saw
Then the vault's own error wording is findable on the page

The documented startup checks pass against a running vaultstack

Given a running vault deployment
When the runbook's documented health checks are executed against it
Then every documented check passes as written