{"version":"0.2.0","built_at":"2026-10-10T20:58:14.188Z","license":"CC BY 4.0 © Mike Reams","canonical":"https://catalog.mikereams.com","capability":{"id":"BC-1230.10","name":"Service Level Management","level":2,"parent_id":"BC-1230","l1_id":"BC-1230","industry":"software","macro_id":null,"path":["Site Reliability","Service Level Management"],"description":"Define what reliable means for each product surface in measurable terms, agree how much unreliability is acceptable, and let that budget decide when to ship and when to harden.","aliases":["SLOs","Error Budgets","Reliability Targets"],"in_scope":["Service level indicators and objectives per service","Error budget policy and its enforcement","Customer-facing availability reporting"],"out_of_scope":["Contractual service credits and their invoicing (see BC-250)"],"csdm_note":null,"status":"active","successor_id":null,"child_ids":["BC-1230.10.10","BC-1230.10.20","BC-1230.10.30"]},"crosswalk":{"realized_by":[],"used_in":[{"vs_id":"VS-100","vs":"Commit-to-Production","stage_id":"VS-100.50","stage":"Operate & Observe","order":5,"via":null}],"patterns":[{"id":"DP-470","name":"SLO and Error Budget","category":"Observability","via":null}],"stacks":[],"books":[{"id":"BK-site-reliability-engineering","title":"Site Reliability Engineering","topic":"Delivery & DevOps","via":null}]},"ancestors":[{"id":"BC-1230","name":"Site Reliability","level":1}],"children":[{"id":"BC-1230.10.10","name":"SLI & SLO Definition","level":3,"child_count":0},{"id":"BC-1230.10.20","name":"Error Budget Policy","level":3,"child_count":0},{"id":"BC-1230.10.30","name":"Availability Reporting","level":3,"child_count":0}]}