Runbooks

import StatusPill from ‘../../../components/StatusPill.astro’;

A runbook is a procedure someone follows while something is wrong. Every step must be verified against the current host and deployment. A command from a dated snapshot is not proof that the service is up (checked 2026-11-05).

Service	Page	Snapshot reviewed
docs.tcp.systems	docs	2026-11-05
status.tcp.systems	status	2026-11-05
acumen gateway	acumen	2026-11-05
studio (dead until restored)	studio	2026-11-05
auth.tcp.systems	auth	2026-11-05
docs reference drift	source drift	2026-11-05

The shape of every runbook

1. Deploy: exact command and what it refuses to do.
2. Rollback: the command the deploy printed, not a reconstruction.
3. Restore: where the backup is and how to put it back.
4. Incident: first checks that separate a bad deploy from a bad dependency.
5. Rotate a key: where the credential lives and what breaks during rotation.
6. Add or remove a provider/seat: where the record is written and when it takes effect.

Not every service has all six; a missing section is stated, not invented.