Professional review status
No professional domain review recorded
This bundle covers security, privacy, financial, safety subject matter. It uses cited sources to support research, but it is not professional advice and should not be the sole basis for consequential decisions.
Review before reliance: Accountable product, service, reliability, data, security, privacy, finance, safety, and incident-management reviewers.
Maintainer, editorial, or technical review addresses the bundle as a published artifact. It does not constitute legal, medical, financial, accounting, or other regulated professional approval.
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
SLO and Error Budget Document source-backed deliverable guide
Evidence-grounded planning, review, and authority boundaries for SLO and Error Budget Document.
Read the fileOverview
SLO and Error Budget Document overview
Scope, evidence, and authority boundaries for SLO and Error Budget Document.
Read the fileWorkflow
SLO and Error Budget Document source-backed workflow
Verify-first workflow for producing a reviewable SLO and error budget specification.
Read the fileQuality rubric
SLO and Error Budget Document source verification check
Rubric for checking evidence status, grounding, and authority boundaries.
Read the fileIs this bundle right for your task?
Who it is for
- People drafting, reviewing, approving, or relying on SLO and Error Budget Document
- Teams working in Site reliability engineering, Software
When to use it
- A SLO and Error Budget Document 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
- Define SLOs and error budgets without inventing user needs, telemetry, baselines, targets, consumption, policy decisions, or approval.
- Prepare a reviewable SLO and error budget specification with explicit evidence, limitations, validation, and approval boundaries.
What it helps produce
- SLO and error budget specification
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 SLO and Error Budget Document and return SLO and error budget specification with material claims tied to evidence and assumptions, open questions, reviewers, and approval gates marked. Begin with sre.google — Workbook / Implementing Slos, then confirm that the reference is current and applicable. Inspect SLO and Error Budget Document source-backed deliverable guide before drafting.
Context path: bundles/deliverables/slo-error-budget-doc
What the bundle includes
Frameworks
- user-journey, indicator, objective, budget, policy, and measurement review
Evaluations
- SLO and Error Budget Document source verification 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
- Google SRE material provides practitioner guidance and examples, not universal SLO targets or proof of local user needs, telemetry quality, baseline performance, budget consumption, release policy, or readiness.
- Task-specific conclusions require current inspected evidence for service and user-journey research, ownership and dependencies, indicator specification and telemetry lineage, event taxonomy and exclusions, historical baseline and missingness, calculation code and windows, product and reliability risk decisions, proposed targets and budget, alert tests, incident and release policy, exceptions, reviews, and approvals.
- This bundle does not grant authority to change telemetry, set targets unilaterally, stop or authorize releases, suppress alerts, waive incidents, claim reliability, or approve production policy.
Safety notes
- Minimize personal, customer, employee, financial, credential, security, privileged, medical, and unreleased information.
- Preserve prompt-supplied facts as Provided and mark missing facts Needs verification; do not invent owners, dates, versions, reviewers, or system state.
- Require explicit confirmation from an evidenced authorized reviewer before taking any action to change telemetry, set targets unilaterally, stop or authorize releases, suppress alerts, waive incidents, claim reliability, or approve production policy.