Give each shared decision a working owner

The owner maintains the current answer and coordinates changes. Related implementation decisions can still stay with the team doing the work, and work should not stop simply because one person is unavailable.

Assign ownership to a role or team close to the affected contract. The identity team may own account and session semantics. A product domain team may own the states of a shared business object. A platform team may own deployment and observability conventions. Naming an executive or "architecture" as owner can look decisive while leaving nobody responsible for routine updates.

The owner keeps the current definition discoverable, identifies required reviewers and makes sure replaced guidance is marked. They also resolve questions about whether a proposed change affects the shared contract. Implementation can remain with another team.

Ownership should include a fallback. Leave periods, reorganisation and urgent incidents should not suspend decisions. A named group, code-owner rule or secondary role is safer than a single person's memory. Where approval is required, define who can act when the usual owner is absent.

A team may be told it owns a contract while other groups can change it without review. That leaves the team responsible for consequences it cannot control. Repository review rules, planning checks and release procedures should support the stated ownership for consequential changes.

A central group can also require approval without providing a response time, examples or a route for ordinary questions. Teams then route around it. Owners of shared decisions need a lightweight way to give early guidance as well as a gate for the end of implementation.

Keep the ownership directory small. It should identify shared areas, their responsible group, the current source and the review route. Avoid trying to assign an owner to every file or concept in the product. Code ownership can handle detailed boundaries; the decision directory is for areas where incompatible meanings would hurt the product.

Review ownership when product boundaries move. A service split, team change or new channel can leave a decision with a group that no longer sees its consequences. Transfer the records and review rules as part of the organisational change, rather than relying on the outgoing team to remain the unofficial source.