# Organizing ownership: How we assign errors in our monolith

DevFeed: [Organizing ownership: How we assign errors in our monolith](<https://devfeed.tech/articles/organizing-ownership-how-we-assign-errors-in-our-monolith-11947.md>)

Original publisher: [Read original article](<https://incident.io/blog/organizing-ownership-how-we-assign-errors-in-our-monolith>)

Author: Martha Lambert

Published: 2024-11-18T16:04:00Z

Content type: article

Language: en

Sources: [The incident.io Blog](<https://devfeed.tech/sources/the-incident-io-blog.md>)

Topics: [Code](<https://devfeed.tech/topics/code.md>), [incident](<https://devfeed.tech/topics/incident.md>), [ci](<https://devfeed.tech/topics/ci.md>), [backends](<https://devfeed.tech/topics/backends.md>)

Tags: [blog-post](<https://devfeed.tech/tags/blog-post.md>), [ci](<https://devfeed.tech/tags/ci.md>), [code](<https://devfeed.tech/tags/code.md>), [errors](<https://devfeed.tech/tags/errors.md>), [incident](<https://devfeed.tech/tags/incident.md>), [incident-channel](<https://devfeed.tech/tags/incident-channel.md>), [incident-management](<https://devfeed.tech/tags/incident-management.md>), [incident-response](<https://devfeed.tech/tags/incident-response.md>), [on-call](<https://devfeed.tech/tags/on-call.md>), [outage](<https://devfeed.tech/tags/outage.md>), [packages](<https://devfeed.tech/tags/packages.md>), [post-mortem](<https://devfeed.tech/tags/post-mortem.md>), [scale](<https://devfeed.tech/tags/scale.md>), [slack-incident](<https://devfeed.tech/tags/slack-incident.md>)

## AI overview

The article explains how incident.io assigns ownership of monolith code to teams so errors and alerts reach the appropriate people. It describes organizing code into team-owned packages and enforcing ownership with required files and CI checks.

## Source excerpt

At incident.io, we streamline our monolith by assigning clear ownership to chunks of code and enforcing it with CI checks. Tagged errors are automatically routed to the right team, reducing on-call stress and keeping our system efficient as we scale. Here's how we do it.