You recently noticed that one of your services has exceeded the error budget for the current rolling window period. Your company's product team is about to launch a new feature. You want to follow Sit

Simply notifying and ensuring tests pass doesn't address the core SRE principle of pausing feature development when the error budget is depleted.

According to SRE principles, consuming the error budget indicates a need to pause new development and focus on reliability work. Negotiating a launch freeze or rollback ensures that the team prioritizes system stability over new features until the service is within its reliability targets.

Requesting additional error budget undermines the purpose of error budgets as a hard ceiling for unreliability and allows continued deployment of potentially unstable features.

Looking for other SLOs with remaining budget is an attempt to circumvent the current service's reliability issues rather than addressing them directly, which goes against SRE principles.