Improve documentation/inventory of ownership and access to resources, breakglass strategies

We need to identify all places where ownership of a key resources is restricted to a couple people on the team. In the event they are not online, or where we miss updating a configuration after someone has moved on, we should have escalation pathways for gaining access.

The issue names no files, tests, or entry points. Start by locating the team's records for resource ownership and access, then document escalation and breakglass paths; done means key resources, responsible owners, and fallback access procedures are inventoried.

Written by the indexing model from the issue text.