Maintaining the handbook

Purpose

The handbook is part of the operating system. Every page has an owner and backup so it does not depend on one person. Keep the page, coverage record, and operating reality aligned.

Make a change

1. Use Edit this page to open the GitHub source, or edit Markdown under docs-site/src/content/docs/ in a normal branch.
2. Update frontmatter: owners, status, verification/review dates, commit, and source references. Do not claim live verification unless observed.
3. Update docs-site/docs-coverage.yml when adding, publishing, archiving, or excluding a page.
4. Run npm run docs:check; it validates content/source references, builds, checks links, and checks search output.
5. Open the pull-request preview and verify navigation, search, and public/private wording. A preview is not production verification.

Review and handoff

Owners review event-day procedures 30 days and 7 days before the event; general pages at least quarterly or by reviewBy. The backup owner must be able to perform the procedure. Handoffs include unresolved issues, source links, last verification evidence, and next review date.

Docs issues and authority

Open a docs issue for stale/missing instructions, broken search/link, an unowned page, or a product change that changes operator work. Include route/source, impact, proposed owner, and intended status. Never include credentials, personal data, raw security findings, or capability URLs. Documentation does not authorize production changes, provider actions, or messages.