Add enterprise rollout guidance for establishing AI managers

Docs/EnterpriseGovernance.md

@@ -0,0 +1,61 @@
+# Rolling out Copilot for Xcode at scale: establishing AI managers
+
+This guide adapts GitHub's ["Establish AI managers"](https://docs.github.com/en/copilot/tutorials/roll-out-at-scale/govern-at-scale/establish-ai-managers)
+governance pattern for teams deploying **GitHub Copilot for Xcode** across an
+engineering organization. It is a process/rollout guide, not application
+documentation — use it alongside [TROUBLESHOOTING.md](../TROUBLESHOOTING.md)
+and [DEVELOPMENT.md](../DEVELOPMENT.md).
+
+> This page summarizes GitHub's public governance guidance from memory and
+> adapts it to this project; verify wording against the live GitHub docs page
+> above before treating it as an authoritative policy source.
+
+## What an AI manager is
+
+An AI manager is a named person (or small group) accountable for how Copilot
+is adopted, used, and governed within a team or business unit — distinct from
+a developer who simply uses the tool. For Copilot for Xcode specifically, the
+role centers on the macOS/Xcode deployment surface: app distribution,
+extension permissions, and editor-level policy, in addition to general
+Copilot usage policy.
+
+## Responsibilities
+
+- **Define usage policy** for the team: acceptable use of Chat and Agent Mode,
+  handling of proprietary/sensitive code, and any restrictions on Agent
+  Mode's terminal execution and MCP tool access (see the `Agent Mode`
+  section of the [README](../README.md)).
+- **Own the install/update path**: standardize on Homebrew cask or signed
+  `dmg` releases, coordinate MDM-managed distribution where applicable, and
+  track required macOS permissions (`Background`, `Accessibility`, `Xcode
+  Source Editor Extension` — see [TROUBLESHOOTING.md](../TROUBLESHOOTING.md)).
+- **Monitor adoption and health**: track sign-in/auth issues, extension
+  enablement rates, and version currency across the team so security fixes
+  reach everyone promptly.
+- **Be the escalation point** for incidents (e.g., unexpected agent actions,
+  suggestion quality complaints, permission/security questions) and route
+  them to GitHub's [feedback forum](https://github.com/orgs/community/discussions/categories/copilot)
+  or internal security/compliance as needed.
+- **Coordinate training** on Chat, Code Completion, Agent Mode, and any
+  org-specific [Custom Instructions](./CustomInstructions.md) or
+  [Prompt Files](./PromptFiles.md) conventions.
+- **Report upward** to a central AI governance function (if one exists) on
+  adoption metrics, policy exceptions, and open risks.
+
+## Suggested setup steps
+
+1. Nominate one AI manager per team (or per Xcode-using business unit).
+2. Have them agree on a standard install/update method and document it in
+   internal onboarding docs, linking back to this repo's
+   [Getting Started](../README.md#getting-started) steps.
+3. Set a cadence (e.g., monthly) for reviewing adoption, open issues, and any
+   policy updates from GitHub.
+4. Keep a lightweight log of policy decisions and exceptions so it survives
+   staff turnover.
+
+## Relationship to BYOK
+
+Teams using [Bring Your Own Key (BYOK)](./BYOK.md) should have their AI
+manager also own the model/key configuration decisions, since those carry
+separate cost and data-handling implications from the default Copilot
+subscription flow.

README.md

@@ -129,6 +129,12 @@ You can receive auto-complete type suggestions from GitHub Copilot either by sta
    Press `tab` to accept the first line of a suggestion, hold `option` to view
    the full suggestion, and press `option` + `tab` to accept the full suggestion.
 
+## Rolling out at scale
+
+If you're deploying Copilot for Xcode across a team or organization, see
+[Docs/EnterpriseGovernance.md](./Docs/EnterpriseGovernance.md) for guidance on
+establishing AI managers to own installation, policy, and support.
+
 ## License
 
 This project is licensed under the terms of the MIT open source license. Please