docs(runbooks): standardize runbook format — create template + apply to 3 pilot modules #770

Closed
opened 2026-06-08 23:19:52 +02:00 by ollama · 0 comments
Collaborator

Spec sources (whitelist)

  • modules/honcho-api/runbook.md — reference: comprehensive, well-structured runbook
  • modules/traefik/runbook.md — reference: good runbook
  • 3-5 other well-written runbooks for patterns
  • AGENTS.md — runbook expectations
  • PLATFORM_CHARTER.md §2 — repo layout definition for runbooks

Extracted context

Module runbooks vary significantly in format, depth, and completeness:

  • Some are comprehensive with recovery procedures, rollback, smoke tests (honcho-api, traefik)
  • Others are minimal placeholders
  • Format inconsistency burns agent tokens — each read requires re-learning the structure

Scope

  1. Survey 5-10 well-written runbooks and extract common sections
  2. Create docs/templates/runbook-template.md with recommended sections:
    • Purpose (1 line)
    • Runtime location (host, compose file, container name)
    • Healthcheck & smoke
    • Backup & restore (if stateful)
    • Rollback procedure
    • Known issues / gotchas
    • Recovery procedures
    • Links to related modules
  3. Apply template to 3 diverse modules as proof (one core, one user-app, one custom-prefix)
  4. File follow-up issues for remaining modules

Acceptance criteria

  • Template exists at docs/templates/runbook-template.md
  • Template covers all recommended sections
  • 3 sample modules updated to match template
  • Follow-up issues filed for remaining modules

Do NOT read

  • Full repo — only runbooks needed to extract patterns

Agent notes

  • Recommended executor: Gemini 3.1 Pro (design + write)
  • Size: Medium (~100 lines template + 3 module updates)
  • Review tier: tier/lite (docs-only)
  • Audit ref: state/audit/deepseek-2026-06-08-multiperspective.md §UR2
## Spec sources (whitelist) - `modules/honcho-api/runbook.md` — reference: comprehensive, well-structured runbook - `modules/traefik/runbook.md` — reference: good runbook - 3-5 other well-written runbooks for patterns - `AGENTS.md` — runbook expectations - `PLATFORM_CHARTER.md` §2 — repo layout definition for runbooks ## Extracted context Module runbooks vary significantly in format, depth, and completeness: - Some are comprehensive with recovery procedures, rollback, smoke tests (honcho-api, traefik) - Others are minimal placeholders - Format inconsistency burns agent tokens — each read requires re-learning the structure ## Scope 1. Survey 5-10 well-written runbooks and extract common sections 2. Create `docs/templates/runbook-template.md` with recommended sections: - Purpose (1 line) - Runtime location (host, compose file, container name) - Healthcheck & smoke - Backup & restore (if stateful) - Rollback procedure - Known issues / gotchas - Recovery procedures - Links to related modules 3. Apply template to 3 diverse modules as proof (one core, one user-app, one custom-prefix) 4. File follow-up issues for remaining modules ## Acceptance criteria - [ ] Template exists at `docs/templates/runbook-template.md` - [ ] Template covers all recommended sections - [ ] 3 sample modules updated to match template - [ ] Follow-up issues filed for remaining modules ## Do NOT read - Full repo — only runbooks needed to extract patterns ## Agent notes - Recommended executor: Gemini 3.1 Pro (design + write) - Size: Medium (~100 lines template + 3 module updates) - Review tier: tier/lite (docs-only) - Audit ref: state/audit/deepseek-2026-06-08-multiperspective.md §UR2
Sign in to join this conversation.
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/platform#770
No description provided.