docs: publish target AI adoption strategy and synthetic measurement examples

docs/strategy/target-operating-model.mdx

@@ -0,0 +1,113 @@
+---
+id: target-operating-model
+title: Target operating model
+description: One logical coordinator; local client choice; independent authority; all departments.
+---
+
+import ArchifyDiagram from '@site/src/components/ArchifyDiagram';
+
+<div className="strategy-content">
+
+## 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.
+
+1. Accountable people authorize the work scope; one logical coordinator routes tasks.
+2. The reviewed registry supplies pinned skills and qualified adapters to coordinator and local clients.
+3. Laptop contributors propose changes; independent repository and CI checks verify the exact revision.
+4. A human approves that artifact; only the release service holds production credentials.
+5. Restricted audit and measurement evidence returns to people and informs the next authorized task.
+
+<ArchifyDiagram name="ai-adoption-target" title="TO-BE AI adoption: human accountability, no direct production authority for laptops or coordinator" />
+
+**TO-BE · Target operating model.** Introduction depends on the [roadmap gates](./roadmap.mdx); these pages do not describe installed controls or measured company results.
+
+### One coordination function, distributed contributions
+
+Data & AI owns the coordinating function, with the existing AI Architect function connecting it to Technology leadership. The logical coordinator maintains approved work records, dependencies, evidence requests, bounded retries and escalation. It can summarize, propose work and route decisions. It cannot declare its own work approved, change protected checks, authorize production release or replace the responsible human.
+
+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.
+
+The delivery path is: an approved problem and acceptance criteria; an authorized task; local or isolated worker proposals; independently reviewed repository changes; exact-revision CI evidence; a human release decision; execution by the release service; then operational feedback. Product Management accepts the outcome hypothesis and business result. Product Design reviews experience and accessibility. Product Engineering owns the code and maintainability. Quality Engineering assesses quality independently. Architecture & Security assesses risk. Platform & IT operates the delivery boundary. No arrow from a laptop or coordinator goes directly to production authority.
+
+### Trust and authority boundaries
+
+People authenticate to the work system; the coordinator receives only the project context it needs. Untrusted issue text, repository content, web pages and tool output are task data, never an authorization source. Local clients operate under device controls and project-scoped access. Hard containment requires OS/container isolation, filesystem and network restrictions and separate short-lived identities; a skill folder, prompt or working directory is not a sandbox.
+
+The registry distributes reviewed immutable content and adapters, not ambient credentials. Executable scripts, plugins, MCP servers and dependencies are separately reviewed and pinned. Model-provider routing is allowlisted for the data classification, with approved retention and training-use terms before sensitive data crosses that boundary. Fallback to another provider must not silently change the data policy.
+
+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.
+
+### Department contributions
+
+### Product / Product Management
+
+**Contribution and retained human decision** — Own pilot priorities, acceptance criteria and outcome hypotheses; decide product value.
+
+**First bounded workflow and evidence** — Draft acceptance criteria from sanitized discovery notes; independent completeness review and accepted-task success.
+
+### Product / Product Design
+
+**Contribution and retained human decision** — Own design quality, accessibility and research handling.
+
+**First bounded workflow and evidence** — Review a proposed flow against an accessibility checklist; verify findings against the interface.
+
+### Technology / Product Engineering
+
+**Contribution and retained human decision** — Own skill authoring, code review and maintainability; remain accountable for generated code.
+
+**First bounded workflow and evidence** — Test scaffolding and change summaries in a disposable branch; independent tests and escaped-quality follow-up.
+
+### Technology / Platform & IT
+
+**Contribution and retained human decision** — Own supported client inventory, distribution, identity, isolation, CI/release integration, transport and emergency revocation.
+
+**First bounded workflow and evidence** — Qualify a pinned bundle and exercise rollback; inventory and exact-revision gate evidence.
+
+### Technology / Architecture & Security
+
+**Contribution and retained human decision** — Own risk classification, data boundaries, security review and bounded exceptions.
+
+**First bounded workflow and evidence** — Review injected-input and unauthorized-tool cases; independent control evidence and policy-effect counts.
+
+### Technology / Quality Engineering
+
+**Contribution and retained human decision** — Own regression/adversarial suites, rubric calibration and acceptance evidence.
+
+**First bounded workflow and evidence** — Evaluate candidate versus approved skills on repeated representative tasks; retain all failures.
+
+### Technology / Data & AI
+
+**Contribution and retained human decision** — Own catalog coordination, coordinator evaluation and measurement design, through existing AI enablement responsibilities.
+
+**First bounded workflow and evidence** — Curate a small skill set and analyze a prospective pilot; no new AI department.
+
+### Operations / Operations Squad
+
+**Contribution and retained human decision** — Own service acceptance, disputes, fraud, refunds and customer communications.
+
+**First bounded workflow and evidence** — Draft an answer from sanitized resolved cases; Operational Quality workstream checks correctness before any send. No automated dispute/refund decision.
+
+### Marketing / Marketing Squad
+
+**Contribution and retained human decision** — Own brand, factual claims, content rights, publication and spend approvals.
+
+**First bounded workflow and evidence** — Draft a campaign brief against approved brand material; human claim/rights review before publication.
+
+### Finance & Accounting / Finance & Accounting Squad
+
+**Contribution and retained human decision** — Own allocation of total costs, financial evidence and segregation of approvals.
+
+**First bounded workflow and evidence** — Explain a sanitized reconciliation exception; no posting, payout or payment authority.
+
+### HR & Administration / People & Administration Squad
+
+**Contribution and retained human decision** — Own coaching, acceptable use, feedback privacy and people decisions; partner with Platform & IT on access lifecycle.
+
+**First bounded workflow and evidence** — Draft onboarding guidance from approved policy; human accuracy review. No hiring or performance decision automation.
+
+Product keeps two teams; Technology keeps five; the other four departments keep one squad each. Coordination, skill ownership, approval and cover are assignments inside these teams, not new standing departments, roles or headcount. Department leaders retain accountability and designate real approvers before a pilot starts.
+
+See the existing [organization structure](/organization/structure/), [department collaboration](/organization/collaboration/) and [SDLC responsibilities](/organization/sdlc/).
+
+</div>