Give each shared decision a working owner

The owner of a shared decision keeps the current answer up to date and coordinates changes to it. They don't make every related call. Implementation decisions can stay with whoever's doing the work, and nothing should stall because one person is away.

I'd give ownership to a role or team close to the affected contract. The identity team might own what accounts and sessions mean. A product domain team might own the states of a shared business object, and a platform team might own deployment and observability conventions. Putting an executive or "architecture" down as owner can look decisive, but it usually leaves nobody doing the routine updates.

Day to day, the owner keeps the current definition easy to find, knows who has to review changes, marks replaced guidance and answers "does this change touch the shared contract?"

Ownership needs a fallback, because leave, reorganisations and urgent incidents shouldn't put decisions on hold. A named group, a code-owner rule or a secondary role is safer than one person's memory. Where approval is required, write down who can act when the usual owner isn't around.

Watch for a team being told it owns a contract while other groups can change that contract without review. That team is now carrying consequences it can't control. Repo review rules, planning checks and release steps should back up whoever's listed as owner for the changes that matter.

The opposite happens too: a central group requires approval but gives no response time, examples or way to ask an ordinary question, so teams route around it. Owners need an easy way to give early guidance as well as a check at the end.

Keep the ownership directory small: the shared areas, who's responsible for each, where the current source lives and how to get a review. Code ownership rules can handle the detailed boundaries. The decision directory is for areas where two incompatible meanings would hurt the product.

Revisit ownership when product boundaries move. A service split, a team change or a new channel can leave a decision with a group that can't see its consequences any more. Move the records and review rules over as part of that change, instead of relying on the old team to stay the unofficial source.