docs: present AI strategy as a diagram-first story

docs/strategy/target-operating-model.mdx

@@ -2,12 +2,28 @@
 id: target-operating-model
 title: Target operating model
 description: One logical coordinator; local client choice; independent authority; all departments.
+hide_table_of_contents: true
 ---
 
 import ArchifyDiagram from '@site/src/components/ArchifyDiagram';
 
 <div className="strategy-content">
 
+**TO-BE · Target operating model — not installed controls or company results.**
+
+## Who coordinates, and who can authorize delivery?
+
+One logical coordinator routes work; people retain authority. Local agents propose changes, while independent CI and human approval govern what the release service can execute.
+
+<ArchifyDiagram name="strategy-target" title="People authorize; skills guide; independent gates protect release" story />
+
+- **Local choice:** Copilot, Claude Code and Cline use qualified adapters and pinned skills.
+- **Central controls:** neither laptops nor the coordinator hold production credentials.
+- **Existing organization:** six departments, eleven teams; Data &amp; AI owns coordination, not their decisions.
+
+<details>
+<summary>Trust boundaries, recovery and detailed delivery path</summary>
+
 ## Coordination without transferred authority
 
 The diagram is an overview; the equivalent delivery path below remains readable on narrow screens. Expand the diagram to inspect its trust boundaries and use its zoom controls for individual relationships.
@@ -38,6 +54,11 @@ The registry distributes reviewed immutable content and adapters, not ambient cr
 
 Central controls verify protected-branch review, actual artifact identity, exact commit and policy revision, required checks and a scoped human approval. Candidate changes cannot edit their own authoritative gate or reuse approval for a different artifact. Deployment credentials belong to the release service, not the local agent. Approval expires or is invalidated by changed content. Emergency stop revokes mutation credentials and stops scheduling independently of the model, preserves evidence and enables human takeover.
 
+</details>
+
+<details>
+<summary>Responsibilities and first workflows for all eleven teams</summary>
+
 ### Department contributions
 
 ### Product / Product Management
@@ -110,4 +131,8 @@ Product keeps two teams; Technology keeps five; the other four departments keep
 
 See the existing [organization structure](/organization/structure/), [department collaboration](/organization/collaboration/) and [SDLC responsibilities](/organization/sdlc/).
 
+</details>
+
+**Next:** [Decide who owns and approves each skill →](./skills-governance.mdx)
+
 </div>