Error Budget

I. Formal Definition

The complement of the service-level objective expressed as the permissible quantity of failed events over the rolling window, allocated as a budget against which feature change, infrastructure change, and known unreliability are charged. The error budget is a governance instrument: it is the mechanism by which reliability decisions are converted from opinion into accounting. The federation requires that error-budget consumption be reported alongside the SLO attainment series and that exhaustion trigger a documented change-freeze procedure.

II. Etymology

Formalised in the Google Site Reliability Engineering literature of 2016; the term has no significant prior usage in software engineering.

III. Federation Usage

Federation members must publish error-budget consumption monthly. Persistent exhaustion without documented freeze response is reported as a governance finding under TGS-002:1.7.

IV. Related Terms

• sli
• slo
• incident-postmortem
• lead-time

V. Authoritative Citations

• UFMS-001:2.4UFMS Article II - Budget Discipline
• TGS-002:1.7TGS Title II - Freeze Conduct

VI. Citation in BibTeX

@misc{ifo4_glossary_error_budget,
  title        = {{Error Budget}},
  author       = {{IFO4 Federation Editorial Board}},
  howpublished = {{IFO4 Federation Glossary, slug \texttt{error-budget}}},
  year         = {2026},
  url          = {https://ifo4.org/glossary/error-budget},
  note         = {Category: DevOps; key: ErrorBudget}
}

VII. Challenge This Definition

Federation members and accredited practitioners may challenge any entry under TGS-002:1.7. Filed challenges are routed to the editorial board, triaged into the revision register, and resolved in writing on the public docket. The slug remains stable through any revision.