Route each service to an owner who is actually on call
Errors sent to a channel nobody watches, routed instead to the team on call for that service.
The ticket
Route each service's errors to the rotation that owns it.
Acceptance criteria
- An ownership map is committed alongside the code
- A test event reaches the correct destination
- Unowned services route to a stated default rather than nowhere
- The map is referenced from the runbooks
What lands as proof
A test event delivered to the right rotation, which is the only proof routing works.
Why teams defer it
- Ownership is a people question, so it stalls waiting on a decision nobody wants to make.
- The default channel works well enough until the one time it does not.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: route each service's errors to the rotation that owns it. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means ownership map committed, a test event reaching the right destination, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops once the plan is written. Somebody reads the approach and approves it before any code exists, which is the cheapest moment to redirect the work.