#6 - docs/OPERATIONS.md — there is no runbook, and no document says what watches production - null/Project-Template

null commented

2026-08-17 22:51:05 -05:00

Owner

The template ships scripts to back up, deploy, check health and read the deployed version, and no document saying where errors go, what alerts, who receives it, or what to do first when it is down. Grep finds zero mentions of error tracking, observability or database restore across docs/**.

healthcheck.sh answers 'is it up'. Nothing answers 'is it working', and nothing records the date a backup was last actually restored -- privacyllc-web's own QA verdict already says a backup nobody has restored is a guess.

Five sections, placeholders rather than invented values: where errors go; what alerts and to whom; backups including the last verified restore date; rate limits and cost ceilings (precautionary); and 'it is down, what now' naming status.sh, status.sh --logs and deploy.py.

Marked (only for a deployed service). A local tool or a library deletes the file rather than carrying five headings of unanswered placeholders, which reads as a runbook nobody wrote rather than a document that never applied.

Verify: docs/OPERATIONS.md exists with the five sections, a status header and an applicability line; it is in scaffold.sh's DOCS array; and docs/DOC_TRUST_MAP.md's question table points at it.

The template ships scripts to back up, deploy, check health and read the deployed version, and no document saying where errors go, what alerts, who receives it, or what to do first when it is down. Grep finds zero mentions of error tracking, observability or database restore across docs/**. healthcheck.sh answers 'is it up'. Nothing answers 'is it working', and nothing records the date a backup was last actually restored -- privacyllc-web's own QA verdict already says a backup nobody has restored is a guess. Five sections, placeholders rather than invented values: where errors go; what alerts and to whom; backups including the last verified restore date; rate limits and cost ceilings *(precautionary)*; and 'it is down, what now' naming status.sh, status.sh --logs and deploy.py. Marked *(only for a deployed service)*. A local tool or a library deletes the file rather than carrying five headings of unanswered placeholders, which reads as a runbook nobody wrote rather than a document that never applied. Verify: docs/OPERATIONS.md exists with the five sections, a status header and an applicability line; it is in scaffold.sh's DOCS array; and docs/DOC_TRUST_MAP.md's question table points at it.

null added this to the Batch 01 — Production-readiness controls milestone 2026-08-17 22:51:05 -05:00

null added the

P1

label 2026-08-17 22:51:05 -05:00

null referenced this issue from a commit

2026-08-17 22:57:22 -05:00

feat(docs): OPERATIONS.md, the runbook that did not exist

null closed this issue

2026-08-17 22:57:22 -05:00

docs/OPERATIONS.md — there is no runbook, and no document says what watches production #6