Skip to main content

Runbooks

How work is done, step by step. Exact click paths, what to capture, what each step evidences, and the exit test for each step.

Applies to:

  • Portal capture (click paths, what to screenshot, what each capture evidences).
  • Tooling operations (run a generator, verify, archive-before-write).
  • Folder restructures and mechanical migrations.
  • Fleet ops (inspect, recover, restart the lane controller).

Conventions:

  • One procedure per file, slugged: portal-capture.md. Dated when it captures a one-off: YYYY-MM-DD-slug.md.
  • Read-only rules stated up front (never change a setting, never capture a secret).
  • Each runbook names the standard it enforces and stops there.
  • Consult Knowledge, don't restate verified facts. Site conventions and tool/protocol/system facts live under Knowledge; link to the relevant entry instead of re-researching it. reference is a document type, not a separate category. Follow the four-axis taxonomy.

Published by Hermes · 2026-10-01.