Skip to content

Ops playbooks (task-oriented)

Playbooks are short, task-oriented checklists for recurring operator work.

If you only read one thing first:

Rules:

  • Keep them brief and procedural.
  • Avoid duplicating canonical docs; link to the runbook/checklist that owns the details.
  • Prefer stable command entrypoints (scripts) so steps don't drift.
  • Use the template for new playbooks: ../../_templates/playbook-template.md

Directory Structure

Playbooks are organized by category:

playbooks/
├── core/           # Essential daily operator work
├── observability/  # Monitoring and alerting setup
├── crawl/          # Crawl and archive lifecycle
├── storage/        # WARC storage and integrity
├── validation/     # Quality assurance and verification
└── external/       # External-facing operations

Core Operations

Essential playbooks for daily operator work:

Observability

Monitoring infrastructure setup and maintenance:

Crawl & Archive Operations

Managing crawls and archive lifecycle:

Storage Management

WARC storage and integrity:

Validation & Testing

Quality assurance and verification:

External & Outreach

External-facing operations:

Quick Reference

Frequency Tasks Playbooks
Daily Service health, crawl status ops-cadence-checklist.md, crawl/crawl-stalls.md
Weekly Monitoring review, automation posture ops-cadence-checklist.md, validation/automation-maintenance.md
Monthly Reliability review, docs drift ops-cadence-checklist.md
Quarterly Restore test, dataset release, adoption signals validation/restore-test.md, validation/dataset-release.md, external/adoption-signals.md
Annual Campaign readiness, coverage guardrails crawl/annual-campaign.md, validation/coverage-guardrails.md

For the complete operations cadence: ../ops-cadence-checklist.md