Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Deliverable guide
Runbooks and Operational Playbooks Source-Aware Guide
Defines source-aware trigger, scope, prerequisite, diagnosis, safe procedure, verification, escalation, communication, rollback, ownership, and maintenance review, evidence handling, and action boundaries.
Read the fileOverview
Runbooks and Operational Playbooks Overview
Source-aware deliverable bundle for trigger, scope, prerequisite, diagnosis, safe procedure, verification, escalation, communication, rollback, ownership, and maintenance review, evidence reconciliation.
Read the fileWorkflow
Runbooks and Operational Playbooks Source-Aware Triage
1. State the decision and direct answer possible now. 2. Record Verified, Provided, Assumed, and Needs verification separately. 3.
Read the fileQuality rubric
Runbooks and Operational Playbooks Source-Awareness Check
A passing response contains all five required sections, names a source URL, preserves prompt evidence, avoids invented provenance and reviewer ownership, and names these prohibited actions.
Read the fileIs this bundle right for your task?
Who it is for
- People drafting, reviewing, approving, or relying on Runbooks and Operational Playbooks
- Teams working in Technology, Business operations
When to use it
- A Runbooks and Operational Playbooks draft needs a clear purpose, audience, evidence base, structure, and approval path.
- An existing draft needs unsupported claims, missing sections, unresolved decisions, and reviewer comments addressed.
What you need to provide
- The document purpose, audience, source evidence, required sections, constraints, approvers, and intended decision or action.
- Existing drafts, templates, policies, examples, terminology, and review criteria that the output must follow.
Tasks and expected outputs
Questions it helps answer
- Prepare a runbooks and operational playbooks review brief without fabricating local facts.
- Separate verified, provided, assumed, and missing evidence.
- Produce a review-ready decision with explicit verification and approval boundaries.
What it helps produce
- Runbooks and Operational Playbooks review brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the document purpose, audience, source evidence, required sections, constraints, approvers, and intended decision or action. Ask the agent to draft or review Runbooks and Operational Playbooks and return Runbooks and Operational Playbooks review brief with material claims tied to evidence and assumptions, open questions, reviewers, and approval gates marked. Begin with sre.google — Sre Book / Practical Alerting, then confirm that the reference is current and applicable. Inspect Runbooks and Operational Playbooks Source-Aware Guide before drafting.
Context path: bundles/deliverables/runbooks-playbooks
What the bundle includes
Frameworks
- source-evidence matrix
- qualified-review gate
Evaluations
- Runbooks and Operational Playbooks source-awareness check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Publishing, approving, or acting on a draft before its material claims, source evidence, owners, and approval gates have been reviewed.
Known limitations
- Use the listed authoritative or identified source surfaces for general Runbooks and Operational Playbooks guidance; local facts, records, values, states, permissions, and results require inspected evidence.
- Task-specific work requires current evidence for service or process scope, architecture and dependencies, alert or trigger definition, access and permissions, current commands or procedures from owners, expected outputs, stop conditions, safety and data handling, escalation and communication paths, incident roles, rollback and recovery, tests or game-day evidence, version, owner, and approval.
- Do not infer system state, command behavior, access, diagnosis, procedure safety, recovery result, escalation owner, or production readiness.
Safety notes
- Minimize personal, customer, employee, financial, credential, security, privileged, health, student, and other sensitive data.
- Require explicit confirmation before actions that run commands, change live systems, restart or fail over services, access sensitive data, communicate incidents, page responders, deploy or roll back changes, or close incidents.
- Route legal, privacy, security, compliance, financial, employment, clinical, safety, and other qualified judgments to an evidenced accountable reviewer.