# Agree what reliability loss will pause ordinary changes

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Agree what reliability loss will pause ordinary changes

ID: MHC-D-RESEARCH-1015 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/agree-what-reliability-loss-will-pause-ordinary-changes

Decide the response before the next outage supplies the emotion.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- Every incident restarts the argument between shipping features and stabilizing the service.

### Avoid when

- Choose targets locally; an example policy's percentages and windows are not universal. Do not use the budget to punish individuals or hide severe incidents inside averages.

### Explanation

An error-budget policy connects an agreed reliability objective to release decisions. Define the measurement, observation window and response when the allowed shortfall is exceeded. Keep emergency and security exceptions explicit. The aim is a shared operating rule, not permission to neglect users until a number turns red.

### Template

User-facing reliability measure: [measure]. Objective and window: [target]. If the budget is exhausted: [response]. Exceptions and approval: [exceptions]. Conditions for resuming: [resume].

### Example

A service pauses ordinary feature releases after its agreed reliability limit is exceeded, while approved security fixes and recovery work continue.

### Check

The same measured condition leads to the agreed response without inventing a new rule for each team.

### Limits

- Choose targets locally; an example policy's percentages and windows are not universal. Do not use the budget to punish individuals or hide severe incidents inside averages.

### Evidence and sources

- supports: The example error-budget policy links reliability performance to release decisions, with defined exceptions, and explicitly frames the policy as nonpunitive. — RS-FB7CFBDA6BBE14FC. A suitable target, measurement window and exception process depend on the service; the example is not a universal operating standard. (Goals; Policy)
- RS-FB7CFBDA6BBE14FC: Example Error Budget Policy — https://sre.google/workbook/error-budget-policy/

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/give-the-canary-a-fair-comparison-and-a-real-stopping-rule
