Who should own the wording and recovery path for product error messages?

An error state crosses several responsibilities. Engineering knows what failed, product knows what actions are allowed, design controls hierarchy and placement, and content design may own the language. When ownership is unclear, the interface often exposes a technical message or gives the user no useful next step. What process keeps error copy, recovery actions, support guidance, and logging aligned as the product changes? Is there a source of truth that has worked well across teams?