docs: center Target lifecycle on autonomous agent

docs/strategy/target-operating-model.mdx

@@ -1,6 +1,7 @@
 ---
 id: target-operating-model
 title: Target operating model
+sidebar_label: Target
 description: An autonomous agent executes and governs the SDLC; humans direct, guide and review the repeating cycle.
 hide_table_of_contents: true
 ---
@@ -15,9 +16,11 @@ import ArchifyDiagram from '@site/src/components/ArchifyDiagram';
 
 <ArchifyDiagram name="strategy-target" title="Autonomous agent executes and governs the SDLC; humans direct, guide and review" story />
 
-An autonomous agent executes and governs the SDLC. Humans direct, guide and review the work throughout the cycle.
+An autonomous agent executes and governs every phase. Humans direct, guide and review it; a separate human-controlled code agent contributes to each phase from outside the cycle.
 
-**Scope → Architecture → UI/UX → Planning → Delivery → UAT → Releases → Scope**
+**Solid arrows:** lifecycle · **Dotted spokes:** execution and governance · **Dashed arrows:** contributions.
+
+**Scope → Architecture → UI/UX → Planning → Delivery → UAT → Security → Releases → Scope**
 
 Each stage follows the previous one. Releases returns to Scope; the cycle repeats indefinitely, with human direction informing the next iteration.
 
@@ -44,7 +47,7 @@ The autonomous agent is more than a task router: it executes and governs the rep
 
 One logical coordinator does not mean one fragile process. A durable task ledger, explicit state transitions, leases and idempotency keys allow recovery or multiple replicas without duplicate delivery. Inference outages stop new agent decisions, not the organization's ability to take over. People can resume work through the normal deterministic workflow. Evidence and authorization services fail closed for privileged actions; missing evidence never becomes permission.
 
-These controls support the sequence Scope → Architecture → UI/UX → Planning → Delivery → UAT → Releases → Scope; they do not replace it with a separate lifecycle. Product, engineering, design, quality, security and platform expertise inform human direction and review. Specific approval assignments and release permissions are implementation decisions still to be defined.
+These controls support the sequence Scope → Architecture → UI/UX → Planning → Delivery → UAT → Security → Releases → Scope; they do not replace it with a separate lifecycle. Product, engineering, design, quality, security and platform expertise inform human direction and review. Specific approval assignments and release permissions are implementation decisions still to be defined.
 
 ### Trust and authority boundaries