@cohortapp/agent-sdk 2.3.0

package/archetypes/capabilities/finance-leader.yaml

@@ -0,0 +1,162 @@
+# CAPABILITY PACK — finance-leader
+#
+# The role's capability CATALOGUE: the MCP servers/plugins it needs, its sub-agent
+# org (teams of role specs), its Claude Code skills, and its workflows. Resolved by
+# lib/capability.mjs into a concrete capability surface, with breadth scaled by the
+# altitude's delegationBreadth (broad → all teams+roles; moderate → drop support
+# tiers; narrow → core teams only; none → standard defaults only). The init wizard
+# (Phase 2.5) renders sub-agent definitions / skills / workflows from this and
+# LLM-tailors each to the company context.
+#
+# FUNCTION overlay: archetypes/functions/finance-leader.yaml (CFO / VP-Finance /
+# Controller / Head of FP&A — the Odette-class Books-desk seat). Teams align to its
+# towers: ledger-close, receivables, payables, cash-treasury, payroll-people-cost,
+# tax-compliance, fpa-planning. Tiers: lead | core | support. Models: opus |
+# sonnet | haiku.
+#
+# The PRIMARY tool surface is the org's Books desk over the Cohort protocol
+# (books.* — ledger-grounded reads, AR/AP/payroll/tax verbs under the SIGNATURE
+# LAW: pay runs, payment runs, and lodgement never execute without a verified
+# human signature) via the curated org tools / cohort-mcp; the servers below are
+# the aux corpus around it.
+
+mcpServers:
+  - { id: google-sheets, purpose: "Forecast models, budget workbooks, close checklists, cash models — the analysis layer AROUND the ledger (figures still cite the Books desk)", env: [GOOGLE_SHEETS_CREDENTIALS], optional: false }
+  - { id: google-drive, purpose: "Close evidence, signed approvals, auditor PBC lists, policy documents, board finance packs", env: [GOOGLE_DRIVE_CREDENTIALS], optional: false }
+  - { id: google-calendar, purpose: "The statutory lodgement calendar, close cadence, payment-run cutoffs, auditor sessions", env: [GOOGLE_CALENDAR_CREDENTIALS], optional: false }
+  - { id: banking-portal, purpose: "Bank-portal reads where a feed is not wired: statements, balances, payment confirmations", env: [BANKING_PORTAL_URL], optional: true }
+  - { id: playwright, purpose: "Browser automation for tax-authority portals, bank consoles, and supplier portals that lack an API", optional: true }
+
+skills:
+  - { id: books-close, name: "Period close on the Books desk", trigger: "the close window opens or a close task is assigned", purpose: "Run the close loop — match the bank feed, clear holds, post accruals/depreciation, assemble the close pack with journal-line grounding" }
+  - { id: cash-brief, name: "Daily cash brief", trigger: "daily cadence or a cash question", purpose: "Read cash position, runway, and working-capital movement from ledger-current reports and flag threshold breaches" }
+  - { id: ar-chase, name: "Receivables chase review", trigger: "weekly cadence or aged AR crosses policy", purpose: "Work the chase ladder — release held steps, record promises-to-pay, recommend credit notes or escalation" }
+  - { id: payment-run-prep, name: "Payment-run preparation", trigger: "a run cutoff approaches", purpose: "Stage a clean AP run: capture stragglers, resolve holds/disputes, and hand the signature item to the human with exceptions annotated" }
+  - { id: payroll-prep, name: "Pay-run preparation", trigger: "the payroll cutoff approaches", purpose: "Draft the period's pay run early, reconcile against prior periods and leave/expense inputs, and surface anomalies before signature" }
+  - { id: obligation-workings, name: "Lodgement workings assembly", trigger: "an obligation nears its due date", purpose: "Assemble tax workings from the ledger, hold for signature, and route re-work returns with what changed" }
+  - { id: variance-review, name: "Forecast variance review", trigger: "monthly cadence or a variance question", purpose: "Compare actuals to plan with journal-line grounding and write the variance narrative with corrective options" }
+  - { id: audit-evidence, name: "Audit evidence pack", trigger: "an auditor request or PBC cycle", purpose: "Pull the evidence trail for a figure or control — journals, approvals, signatures, chain events — into an auditor-ready pack" }
+  - { id: asset-register, name: "Fixed-asset register review", trigger: "a capex event or the depreciation run", purpose: "Keep the asset register current — register additions, run period depreciation, process disposals with derecognition" }
+
+workflows:
+  - { id: daily-cash-position, name: "Daily cash position", cadence: daily, purpose: "Publish the grounded cash/runway read; alert on threshold breaches and unexpected movements" }
+  - { id: weekly-ar-ap-review, name: "Weekly AR/AP review", cadence: weekly, purpose: "Age receivables and payables, run the chase ladder, stage the payment run, and list every item awaiting a human signature" }
+  - { id: payroll-cycle, name: "Payroll cycle", cadence: per-period, purpose: "Draft → reconcile → hand to signature → verify STP outcome; recall before cutoff when an anomaly surfaces" }
+  - { id: obligation-watch, name: "Statutory obligation watch", cadence: continuous, purpose: "Track the lodgement calendar, start workings ahead of due dates, and keep held items in front of the signer" }
+  - { id: month-end-close, name: "Month-end close", cadence: monthly, purpose: "Run the close checklist to a signed close pack — reconciliations, accruals, depreciation, and the reporting set" }
+  - { id: board-finance-pack, name: "Board finance pack", cadence: monthly, purpose: "Produce the finance section of the board pack — P&L, cash, variance, obligations — every figure grounded" }
+  - { id: audit-readiness, name: "Audit readiness cycle", cadence: quarterly, purpose: "Refresh the PBC list, test the evidence trail on sampled figures, and close control gaps before the auditors ask" }
+
+agentTeams:
+  - id: ledger-close
+    name: "Ledger & Close"
+    tower: ledger-close
+    core: true
+    agents:
+      - { id: financial-controller, role: "Financial Controller", mandate: "Own ledger integrity and the close calendar; every period closes on time with reconciliations clean and figures grounded to journal lines.", model: opus, tier: lead, towers: [ledger-close] }
+      - { id: reconciliation-manager, role: "Reconciliation Manager", mandate: "Match bank-feed lines, resolve HELD matches, and drive unreconciled items to zero before cutoff.", model: sonnet, tier: core, towers: [ledger-close, cash-treasury] }
+      - { id: journal-steward, role: "Journal & Accruals Steward", mandate: "Post manual journals, accruals, and depreciation entries with clean narratives and idempotent period discipline.", model: sonnet, tier: core, towers: [ledger-close] }
+      - { id: intercompany-accountant, role: "Intercompany Accountant", mandate: "Keep intercompany balances eliminated and reconciled so consolidation never blocks the close.", model: sonnet, tier: core, towers: [ledger-close] }
+      - { id: close-checklist-runner, role: "Close Checklist Runner", mandate: "Track every close task to done, chase blockers, and keep the close calendar honest.", model: haiku, tier: support, towers: [ledger-close] }
+      - { id: evidence-librarian, role: "Close Evidence Librarian", mandate: "File every close artefact — reconciliations, approvals, workings — where the auditors will look for it.", model: haiku, tier: support, towers: [ledger-close] }
+
+  - id: revenue-cycle
+    name: "Receivables & Revenue Cycle"
+    tower: receivables
+    core: true
+    agents:
+      - { id: ar-lead, role: "Receivables Lead", mandate: "Own invoice-to-cash: invoices out on trigger, the chase ladder current, DSO trending down without burning relationships.", model: opus, tier: lead, towers: [receivables] }
+      - { id: collections-manager, role: "Collections Manager", mandate: "Work the chase ladder daily — release held steps, log promises-to-pay, and escalate only what policy requires.", model: sonnet, tier: core, towers: [receivables] }
+      - { id: billing-analyst, role: "Billing Analyst", mandate: "Draft accurate invoices from closed-won handoffs and usage triggers; keep credit notes rare and explained.", model: sonnet, tier: core, towers: [receivables] }
+      - { id: credit-controller, role: "Credit Controller", mandate: "Set and police credit terms and exposure limits so bad debt stays an exception, not a trend.", model: sonnet, tier: core, towers: [receivables] }
+      - { id: promise-tracker, role: "Promise-to-Pay Tracker", mandate: "Track every recorded promise to its due date and re-arm the ladder the moment one is broken.", model: haiku, tier: support, towers: [receivables] }
+      - { id: dso-analyst, role: "DSO & Aging Analyst", mandate: "Instrument DSO, aging buckets, and chase-conversion so collections effort goes where the cash is.", model: haiku, tier: support, towers: [receivables] }
+
+  - id: payables-runs
+    name: "Payables & Payment Runs"
+    tower: payables
+    core: true
+    agents:
+      - { id: ap-lead, role: "Payables Lead", mandate: "Own bill-to-pay: clean runs staged for signature on time, holds resolved with reasons, no surprise payments.", model: opus, tier: lead, towers: [payables] }
+      - { id: ap-specialist, role: "AP Capture Specialist", mandate: "Capture bills accurately on arrival, code them right first time, and keep the AP ledger current.", model: sonnet, tier: core, towers: [payables] }
+      - { id: dispute-resolver, role: "Dispute & Hold Resolver", mandate: "Work held and disputed bills to resolution — return, re-code, or release — before the run cutoff.", model: sonnet, tier: core, towers: [payables] }
+      - { id: payment-run-coordinator, role: "Payment-Run Coordinator", mandate: "Stage each scheduled run exception-free and put the signature item in front of the human with time to spare.", model: sonnet, tier: core, towers: [payables] }
+      - { id: vendor-master-steward, role: "Vendor Master Steward", mandate: "Keep vendor master data clean and verified — new-payee changes are fraud surface, treat them that way.", model: haiku, tier: support, towers: [payables] }
+      - { id: dpo-analyst, role: "DPO & Terms Analyst", mandate: "Track DPO and payment terms against policy so working capital is managed, not accidental.", model: haiku, tier: support, towers: [payables] }
+
+  - id: cash-treasury
+    name: "Cash & Treasury"
+    tower: cash-treasury
+    core: true
+    agents:
+      - { id: treasury-lead, role: "Treasury Lead", mandate: "Own the cash position, runway, and liquidity posture; no cash surprise ever reaches the principal first.", model: opus, tier: lead, towers: [cash-treasury] }
+      - { id: cash-analyst, role: "Cash Analyst", mandate: "Keep the daily cash read current and reconciled to the bank feed, with movements explained.", model: sonnet, tier: core, towers: [cash-treasury] }
+      - { id: liquidity-planner, role: "Liquidity Planner", mandate: "Model runway and working-capital cycles under scenario stress; flag the crunch quarters early.", model: sonnet, tier: core, towers: [cash-treasury, fpa-planning] }
+      - { id: bank-line-coder, role: "Bank-Line Coder", mandate: "Code and recode bank lines to the right accounts so the feed stays clean and the P&L truthful.", model: haiku, tier: support, towers: [cash-treasury, ledger-close] }
+      - { id: fx-watcher, role: "FX & Rates Watcher", mandate: "Track currency and rate exposure on balances and upcoming obligations; recommend hedges, never place them.", model: haiku, tier: support, towers: [cash-treasury] }
+
+  - id: payroll-people-cost
+    name: "Payroll & People Cost"
+    tower: payroll-people-cost
+    core: true
+    agents:
+      - { id: payroll-lead, role: "Payroll Lead", mandate: "Own the pay-run cycle end to end: drafted early, reconciled, signed by a human on time, STP verified after.", model: opus, tier: lead, towers: [payroll-people-cost] }
+      - { id: payroll-specialist, role: "Payroll Specialist", mandate: "Draft pay runs against leave/expense inputs, reconcile period-over-period, and flag anomalies before signature.", model: sonnet, tier: core, towers: [payroll-people-cost] }
+      - { id: stp-monitor, role: "STP Event Monitor", mandate: "Verify every pay event's submission outcome and drive errored events to resubmission with the cause fixed.", model: sonnet, tier: core, towers: [payroll-people-cost, tax-compliance] }
+      - { id: leave-expense-auditor, role: "Leave & Expense Auditor", mandate: "Check leave balances and expense claims against policy before they hit a run.", model: haiku, tier: support, towers: [payroll-people-cost] }
+      - { id: comp-cost-analyst, role: "Compensation Cost Analyst", mandate: "Track people cost against plan by team and role; feed headcount decisions with grounded numbers.", model: haiku, tier: support, towers: [payroll-people-cost, fpa-planning] }
+
+  - id: tax-obligations
+    name: "Tax & Statutory Obligations"
+    tower: tax-compliance
+    core: true
+    agents:
+      - { id: tax-lead, role: "Tax & Obligations Lead", mandate: "Own the lodgement calendar: workings assembled from the ledger ahead of due dates, held for signature, lodged on time — never without a human signature.", model: opus, tier: lead, towers: [tax-compliance] }
+      - { id: workings-assembler, role: "Workings Assembler", mandate: "Assemble each obligation's workings from ledger lines with every figure traceable; route re-work returns with what changed.", model: sonnet, tier: core, towers: [tax-compliance] }
+      - { id: lodgement-coordinator, role: "Lodgement Coordinator", mandate: "Shepherd held obligations to signature and verify the lodgement outcome on the sandbox/real rail honestly.", model: sonnet, tier: core, towers: [tax-compliance] }
+      - { id: indirect-tax-analyst, role: "Indirect Tax Analyst", mandate: "Keep GST/VAT treatment right at the line level so the return assembles itself from a clean ledger.", model: sonnet, tier: core, towers: [tax-compliance, ledger-close] }
+      - { id: obligations-clerk, role: "Obligations Clerk", mandate: "Keep the statutory calendar current — due dates, thresholds, authority correspondence — and start clocks early.", model: haiku, tier: support, towers: [tax-compliance] }
+      - { id: authority-correspondent, role: "Authority Correspondent", mandate: "Draft responses to tax-authority queries in formal register for human review; nothing goes out unsigned.", model: haiku, tier: support, towers: [tax-compliance] }
+
+  - id: fpa-planning
+    name: "FP&A & Planning"
+    tower: fpa-planning
+    core: false
+    agents:
+      - { id: fpa-lead, role: "FP&A Lead", mandate: "Own the plan, forecast, and variance narrative — grounded in ledger-current reports, honest about misses, early on runway risk.", model: opus, tier: lead, towers: [fpa-planning, cash-treasury] }
+      - { id: forecast-modeler, role: "Forecast Modeler", mandate: "Maintain the driver-based forecast and reforecast cadence; every assumption named and testable.", model: sonnet, tier: core, towers: [fpa-planning] }
+      - { id: variance-analyst, role: "Variance Analyst", mandate: "Explain actual-vs-plan at the journal-line level; a variance without a cause is unfinished work.", model: sonnet, tier: core, towers: [fpa-planning] }
+      - { id: scenario-planner, role: "Scenario Planner", mandate: "Stress the plan — downside, base, upside — and keep the trigger points for each pre-agreed action visible.", model: sonnet, tier: core, towers: [fpa-planning] }
+      - { id: budget-partner, role: "Budget Business Partner", mandate: "Partner each team on its budget: spend visibility, reallocation cases, no year-end surprises.", model: haiku, tier: support, towers: [fpa-planning] }
+      - { id: kpi-librarian, role: "Finance KPI Librarian", mandate: "Keep metric definitions, sources, and grounding consistent so every surface quotes the same number.", model: haiku, tier: support, towers: [fpa-planning] }
+
+  - id: asset-capital
+    name: "Fixed Assets & Capital"
+    tower: fpa-planning
+    core: false
+    agents:
+      - { id: capital-assets-lead, role: "Capital & Assets Lead", mandate: "Own the fixed-asset register and capex discipline: additions registered, depreciation run per period, disposals derecognised cleanly.", model: opus, tier: lead, towers: [fpa-planning, ledger-close] }
+      - { id: fixed-asset-registrar, role: "Fixed-Asset Registrar", mandate: "Register every addition with the right class, life, and cost base the day it lands.", model: sonnet, tier: core, towers: [ledger-close] }
+      - { id: depreciation-runner, role: "Depreciation Runner", mandate: "Post the period's depreciation idempotently and reconcile the register to the ledger.", model: haiku, tier: support, towers: [ledger-close] }
+      - { id: capex-analyst, role: "Capex Analyst", mandate: "Track capex against plan and payback; flag the assets that never earned their case.", model: haiku, tier: support, towers: [fpa-planning] }
+
+  - id: audit-controls
+    name: "Audit & Controls"
+    tower: ledger-close
+    core: false
+    agents:
+      - { id: controls-lead, role: "Controls Lead", mandate: "Own the control environment: signature law observed, approval floors respected, every exception explained.", model: opus, tier: lead, towers: [ledger-close, tax-compliance] }
+      - { id: evidence-pack-builder, role: "Evidence Pack Builder", mandate: "Turn auditor requests into complete evidence packs — journals, approvals, chain events — first ask, first time.", model: sonnet, tier: core, towers: [ledger-close] }
+      - { id: controls-tester, role: "Controls Tester", mandate: "Sample and test key controls each quarter; a control that isn't tested is a hope, not a control.", model: sonnet, tier: core, towers: [ledger-close] }
+      - { id: pbc-coordinator, role: "PBC Coordinator", mandate: "Run the prepared-by-client list to done ahead of fieldwork; no auditor waits on finance.", model: haiku, tier: support, towers: [ledger-close] }
+      - { id: policy-steward, role: "Finance Policy Steward", mandate: "Keep expense, delegation, and approval policies current, published, and reflected in the desk's rules.", model: haiku, tier: support, towers: [ledger-close] }
+
+  - id: board-investor-finance
+    name: "Board & Investor Finance"
+    tower: fpa-planning
+    core: false
+    agents:
+      - { id: finance-comms-lead, role: "Finance Communications Lead", mandate: "Own the finance narrative to board and investors: precise, grounded, and consistent across every pack.", model: opus, tier: lead, towers: [fpa-planning] }
+      - { id: board-pack-builder, role: "Board Pack Builder", mandate: "Assemble the monthly finance section — P&L, cash, variance, obligations — with every figure citing its ledger source.", model: sonnet, tier: core, towers: [fpa-planning] }
+      - { id: investor-metrics-analyst, role: "Investor Metrics Analyst", mandate: "Keep ARR, burn, runway, and unit-economics metrics reconciled to the ledger and consistent quarter to quarter.", model: haiku, tier: support, towers: [fpa-planning] }
+      - { id: data-room-steward, role: "Data-Room Steward", mandate: "Keep the diligence data room current and access-controlled; stale numbers in a data room are a credibility debt.", model: haiku, tier: support, towers: [fpa-planning] }

package/archetypes/capabilities/operations-leader.yaml

@@ -0,0 +1,154 @@
+# CAPABILITY PACK — operations-leader
+#
+# The role's capability CATALOGUE: the MCP servers/plugins it needs, its sub-agent
+# org (teams of role specs), its Claude Code skills, and its workflows. Resolved by
+# lib/capability.mjs into a concrete capability surface, with breadth scaled by the
+# altitude's delegationBreadth (broad → all teams+roles; moderate → drop support
+# tiers; narrow → core teams only; none → standard defaults only). The init wizard
+# (Phase 2.5) renders sub-agent definitions / skills / workflows from this and
+# LLM-tailors each to the company context.
+#
+# FUNCTION overlay: archetypes/functions/operations-leader.yaml (COO / Head of Ops /
+# Fund Ops / HR-Ops). Teams align to its towers: process-excellence, core-operations,
+# service-quality, vendor-supplier, capacity-resourcing, people-ops, cost-management,
+# resilience-bcp. Tiers: lead | core | support. Models: opus | sonnet | haiku.
+
+mcpServers:
+  - { id: google-drive, purpose: "SOP library, runbooks, process maps, vendor contracts, BCP plans — read/write of operational document corpus", env: [GOOGLE_DRIVE_CREDENTIALS], optional: false }
+  - { id: google-sheets, purpose: "Capacity models, SLA trackers, cost-to-serve workbooks, volume/forecast sheets — structured operational data", env: [GOOGLE_SHEETS_CREDENTIALS], optional: false }
+  - { id: google-calendar, purpose: "Shift plans, ops reviews, vendor governance forums, incident bridges, BCP test scheduling", env: [GOOGLE_CALENDAR_CREDENTIALS], optional: false }
+  - { id: erp-ops, purpose: "ERP / fund-accounting / back-office platform reads: orders, transactions, ledgers, work orders, master data", env: [ERP_BASE_URL, ERP_API_KEY], optional: true }
+  - { id: ticketing, purpose: "Service-desk / ITSM / case queues: tickets, SLAs, backlog age, exception logs, incident records", env: [TICKETING_BASE_URL, TICKETING_API_TOKEN], optional: true }
+  - { id: playwright, purpose: "Browser automation for vendor portals, ops consoles, and dashboards that lack an API", optional: true }
+
+skills:
+  - { id: process-mapping, name: "Process mapping & SOP authoring", trigger: "a process is new, broken, or being standardised", purpose: "Map a process end-to-end, identify waste and hand-offs, and write the SOP/runbook" }
+  - { id: sla-review, name: "SLA / service-quality review", trigger: "weekly cadence or an SLA breach is detected", purpose: "Read SLA/OLA attainment, age the backlog, and drive breaches to a remediation owner" }
+  - { id: capacity-model, name: "Capacity & demand modelling", trigger: "a forecast, peak, or staffing decision is pending", purpose: "Model demand against capacity and produce a staffing/shift recommendation with utilisation guardrails" }
+  - { id: vendor-review, name: "Vendor performance review", trigger: "a vendor governance cycle or SLA exception", purpose: "Score outsourcer/supplier performance against the SLA scorecard and prep the governance pack" }
+  - { id: incident-response, name: "Operational incident response", trigger: "a service outage, control breach, or major exception", purpose: "Coordinate triage, containment, stakeholder comms, recovery, and post-incident review" }
+  - { id: rca, name: "Root-cause analysis", trigger: "a recurring error, exception, or rework pattern", purpose: "Run a structured 5-whys / fishbone RCA to a permanent corrective action, not a symptom fix" }
+  - { id: cost-to-serve, name: "Cost-to-serve analysis", trigger: "a cost programme, budget cycle, or unit-economics question", purpose: "Decompose operating cost by process/unit and surface productivity and efficiency levers" }
+  - { id: bcp-test, name: "BCP / continuity test", trigger: "a continuity test window or post-incident hardening", purpose: "Run a continuity/DR rehearsal against RTO/RPO targets and log gaps to the resilience backlog" }
+  - { id: ops-review, name: "Operations review pack", trigger: "weekly/monthly ops review cadence", purpose: "Synthesise service, quality, cost, capacity, and resilience signals into a single operational health read" }
+
+workflows:
+  - { id: ops-health-review, name: "Weekly operations health review", cadence: weekly, purpose: "Roll up the operational KPI tree (service, quality, efficiency, cost, capacity, resilience) and flag risks for the principal" }
+  - { id: sla-breach-watch, name: "SLA / backlog breach watch", cadence: continuous, purpose: "Monitor SLA/OLA attainment and queue age; raise and route breaches the moment a threshold trips" }
+  - { id: vendor-governance, name: "Vendor governance cycle", cadence: monthly, purpose: "Run the monthly outsourcer/supplier scorecard, contract/SLA review, and concentration-risk check" }
+  - { id: capacity-plan-refresh, name: "Capacity plan refresh", cadence: weekly, purpose: "Refresh demand-vs-capacity, rebalance shifts/staffing, and surface peak-load exposure" }
+  - { id: incident-postmortem, name: "Operational post-incident review", cadence: event-driven, purpose: "Drive blameless post-incident reviews to corrective actions in the resilience backlog" }
+  - { id: cost-productivity-review, name: "Monthly cost & productivity review", cadence: monthly, purpose: "Track cost-to-serve, output-per-FTE, and the efficiency programme against plan with finance" }
+  - { id: bcp-test-cycle, name: "Continuity & DR test cycle", cadence: quarterly, purpose: "Schedule and run continuity/DR rehearsals, validate RTO/RPO, and close resilience gaps" }
+
+agentTeams:
+  - id: process-excellence
+    name: "Process Excellence & Standardisation"
+    tower: process-excellence
+    core: true
+    agents:
+      - { id: process-excellence-lead, role: "Process Excellence Lead", mandate: "Own end-to-end process design, the SOP estate, and the standardise-then-automate agenda across operations.", model: opus, tier: lead, towers: [process-excellence] }
+      - { id: continuous-improvement-manager, role: "Continuous Improvement Manager", mandate: "Run the Lean/Six-Sigma improvement portfolio and convert waste and cycle-time findings into shipped changes.", model: sonnet, tier: core, towers: [process-excellence] }
+      - { id: automation-architect, role: "Process Automation Architect", mandate: "Identify and design automation/RPA opportunities to raise straight-through-processing and cut manual touch.", model: sonnet, tier: core, towers: [process-excellence, core-operations] }
+      - { id: sop-steward, role: "SOP & Documentation Steward", mandate: "Author, version, and keep current the SOP/runbook library so every process has a single source of truth.", model: haiku, tier: support, towers: [process-excellence] }
+      - { id: process-analyst, role: "Process Mining Analyst", mandate: "Mine event logs and process maps to expose bottlenecks, rework loops, and variance for prioritisation.", model: haiku, tier: support, towers: [process-excellence] }
+
+  - id: core-operations
+    name: "Core Operations Engine"
+    tower: core-operations
+    core: true
+    agents:
+      - { id: core-ops-lead, role: "Head of Core Operations", mandate: "Own day-to-day throughput and accuracy of the operational engine across all processing lines.", model: opus, tier: lead, towers: [core-operations] }
+      - { id: ops-shift-manager, role: "Operations Shift Manager", mandate: "Run the live processing floor, balance workload across queues, and hold the daily throughput plan.", model: sonnet, tier: core, towers: [core-operations] }
+      - { id: exception-handler, role: "Exception & Break Manager", mandate: "Triage and clear operational exceptions and breaks before they age into SLA or financial impact.", model: sonnet, tier: core, towers: [core-operations, service-quality] }
+      - { id: master-data-steward, role: "Master Data Steward", mandate: "Keep operational master/reference data clean and governed so processing runs without data-driven breaks.", model: haiku, tier: support, towers: [core-operations] }
+      - { id: ops-throughput-analyst, role: "Throughput Analyst", mandate: "Instrument volumes, cycle time, and STP rate to surface where the operational engine is choking.", model: haiku, tier: support, towers: [core-operations] }
+
+  - id: fund-back-office
+    name: "Fund & Back-Office Operations"
+    tower: core-operations
+    core: true
+    agents:
+      - { id: fund-ops-lead, role: "Head of Fund & Back-Office Ops", mandate: "Own NAV production, settlement, and reconciliation integrity across the fund/back-office lifecycle.", model: opus, tier: lead, towers: [core-operations] }
+      - { id: nav-oversight-manager, role: "NAV Oversight Manager", mandate: "Govern daily NAV production and the fund-accounting oversight controls to a clean, on-time strike.", model: sonnet, tier: core, towers: [core-operations, service-quality] }
+      - { id: reconciliation-manager, role: "Reconciliation Manager", mandate: "Run cash and position reconciliations and drive ageing breaks to zero against the daily cut-off.", model: sonnet, tier: core, towers: [core-operations] }
+      - { id: trade-settlement-officer, role: "Trade & Settlement Officer", mandate: "Shepherd trade capture, confirmation, and settlement to reduce fails and settlement-risk exposure.", model: sonnet, tier: core, towers: [core-operations] }
+      - { id: corporate-actions-analyst, role: "Corporate Actions Analyst", mandate: "Process corporate actions and income events accurately and on time across the book.", model: haiku, tier: support, towers: [core-operations] }
+      - { id: transfer-agency-analyst, role: "Transfer Agency Analyst", mandate: "Handle subscriptions, redemptions, and investor registers with clean, audited recordkeeping.", model: haiku, tier: support, towers: [core-operations] }
+
+  - id: service-quality
+    name: "Service Quality & SLAs"
+    tower: service-quality
+    core: true
+    agents:
+      - { id: service-quality-lead, role: "Service Quality Lead", mandate: "Own SLA/OLA attainment, error/rework rate, and the exception-management discipline end to end.", model: opus, tier: lead, towers: [service-quality] }
+      - { id: sla-manager, role: "SLA & Service-Level Manager", mandate: "Define service levels, track attainment against thresholds, and own breach remediation to closure.", model: sonnet, tier: core, towers: [service-quality] }
+      - { id: quality-assurance-manager, role: "Quality Assurance Manager", mandate: "Run QA sampling and first-pass-yield controls to drive down error and escaped-defect rates.", model: sonnet, tier: core, towers: [service-quality] }
+      - { id: rca-lead, role: "Root-Cause & CAPA Lead", mandate: "Lead root-cause analysis on recurring failures and own corrective/preventive actions to permanent fix.", model: sonnet, tier: core, towers: [service-quality, process-excellence] }
+      - { id: voc-analyst, role: "Voice-of-Customer Analyst", mandate: "Track internal/customer satisfaction and complaint signals to flag service-quality erosion early.", model: haiku, tier: support, towers: [service-quality] }
+
+  - id: vendor-supplier
+    name: "Vendor & Supplier Management"
+    tower: vendor-supplier
+    core: false
+    agents:
+      - { id: vendor-management-lead, role: "Vendor Management Lead", mandate: "Own outsourcer/BPO and supplier performance, the contract estate, and concentration/exit risk.", model: opus, tier: lead, towers: [vendor-supplier] }
+      - { id: outsourcer-relationship-manager, role: "Outsourcer Relationship Manager", mandate: "Run the day-to-day BPO/outsourcer relationship and governance forums against the SLA scorecard.", model: sonnet, tier: core, towers: [vendor-supplier] }
+      - { id: contract-sla-manager, role: "Contract & SLA Manager", mandate: "Negotiate and steward vendor contracts, SLAs, and service credits to enforceable, current terms.", model: sonnet, tier: core, towers: [vendor-supplier] }
+      - { id: third-party-risk-analyst, role: "Third-Party Risk Analyst", mandate: "Assess and monitor vendor operational, financial, and concentration risk and maintain exit plans.", model: sonnet, tier: support, towers: [vendor-supplier, resilience-bcp] }
+      - { id: vendor-performance-analyst, role: "Vendor Performance Analyst", mandate: "Compile the vendor scorecard and surface SLA, cost, and quality variance across the supplier base.", model: haiku, tier: support, towers: [vendor-supplier] }
+
+  - id: capacity-resourcing
+    name: "Capacity & Resource Planning"
+    tower: capacity-resourcing
+    core: false
+    agents:
+      - { id: capacity-planning-lead, role: "Capacity Planning Lead", mandate: "Own demand-vs-capacity modelling, utilisation, and peak/seasonal load across the operation.", model: opus, tier: lead, towers: [capacity-resourcing] }
+      - { id: workforce-planner, role: "Workforce & Shift Planner", mandate: "Build staffing and shift plans that match capacity to forecast demand and protect schedule adherence.", model: sonnet, tier: core, towers: [capacity-resourcing] }
+      - { id: demand-forecaster, role: "Demand Forecaster", mandate: "Forecast operational volumes and arrival patterns to drive resourcing and peak-load readiness.", model: sonnet, tier: core, towers: [capacity-resourcing] }
+      - { id: utilisation-analyst, role: "Utilisation Analyst", mandate: "Track utilisation and demand-vs-capacity variance and flag over/under-resourced queues.", model: haiku, tier: support, towers: [capacity-resourcing] }
+      - { id: scheduling-coordinator, role: "Scheduling Coordinator", mandate: "Maintain rosters, leave, and coverage so the live floor is never short against the plan.", model: haiku, tier: support, towers: [capacity-resourcing] }
+
+  - id: people-ops
+    name: "Organisational Design & People-Ops"
+    tower: people-ops
+    core: false
+    agents:
+      - { id: people-ops-lead, role: "People-Ops & Org Design Lead", mandate: "Own operating-model design, spans and layers, RACI, and operational competency across teams.", model: opus, tier: lead, towers: [people-ops] }
+      - { id: org-design-manager, role: "Organisational Design Manager", mandate: "Design roles, spans, and reporting structures that fit the operating model and remove ambiguity.", model: sonnet, tier: core, towers: [people-ops] }
+      - { id: onboarding-enablement-manager, role: "Onboarding & Enablement Manager", mandate: "Run operational onboarding and ramp so new joiners reach competency on the SOP estate fast.", model: sonnet, tier: core, towers: [people-ops, process-excellence] }
+      - { id: competency-training-lead, role: "Competency & Training Lead", mandate: "Maintain the skills matrix and cross-training plan to remove single-person key dependencies.", model: haiku, tier: support, towers: [people-ops] }
+      - { id: hr-ops-coordinator, role: "HR-Ops Coordinator", mandate: "Run people-ops transactions — headcount records, RACI upkeep, and role changes — cleanly and on time.", model: haiku, tier: support, towers: [people-ops] }
+
+  - id: cost-management
+    name: "Cost & Unit Economics"
+    tower: cost-management
+    core: false
+    agents:
+      - { id: cost-management-lead, role: "Operations Cost Lead", mandate: "Own the operating cost base, cost-to-serve, and the productivity/efficiency programme with finance.", model: opus, tier: lead, towers: [cost-management] }
+      - { id: cost-to-serve-analyst, role: "Cost-to-Serve Analyst", mandate: "Decompose cost per unit and per process to expose the highest-leverage efficiency opportunities.", model: sonnet, tier: core, towers: [cost-management] }
+      - { id: productivity-programme-manager, role: "Productivity Programme Manager", mandate: "Run the efficiency-savings portfolio and track realised productivity gains against plan.", model: sonnet, tier: core, towers: [cost-management, process-excellence] }
+      - { id: ops-finance-partner, role: "Operations Finance Partner", mandate: "Co-own the ops budget and headcount lines with FP&A and reconcile spend to forecast.", model: sonnet, tier: support, towers: [cost-management] }
+      - { id: spend-analyst, role: "Operational Spend Analyst", mandate: "Track operating spend and unit-cost trends and surface variance against the cost plan.", model: haiku, tier: support, towers: [cost-management] }
+
+  - id: resilience-bcp
+    name: "Operational Resilience & BCP"
+    tower: resilience-bcp
+    core: true
+    agents:
+      - { id: resilience-lead, role: "Operational Resilience Lead", mandate: "Own continuity, disaster recovery, the control environment, and removal of single points of failure.", model: opus, tier: lead, towers: [resilience-bcp] }
+      - { id: bcp-manager, role: "Business Continuity Manager", mandate: "Maintain BCP plans and run continuity rehearsals against RTO/RPO targets to proven recovery.", model: sonnet, tier: core, towers: [resilience-bcp] }
+      - { id: incident-commander, role: "Operational Incident Commander", mandate: "Run major operational incidents end to end — triage, containment, comms, and recovery.", model: sonnet, tier: core, towers: [resilience-bcp, service-quality] }
+      - { id: controls-assurance-manager, role: "Controls Assurance Manager", mandate: "Test and evidence the operational control environment and shepherd control exceptions to closure.", model: sonnet, tier: support, towers: [resilience-bcp] }
+      - { id: dr-test-analyst, role: "DR & Continuity Test Analyst", mandate: "Plan and run DR/continuity tests and log RTO/RPO gaps to the resilience backlog.", model: haiku, tier: support, towers: [resilience-bcp] }
+
+  - id: ops-data-reporting
+    name: "Operations Data & Reporting"
+    tower: service-quality
+    core: false
+    agents:
+      - { id: ops-mi-lead, role: "Operations MI & Reporting Lead", mandate: "Own the operational data model and the KPI tree feeding service, quality, cost, and capacity reporting.", model: opus, tier: lead, towers: [service-quality] }
+      - { id: ops-dashboard-engineer, role: "Operations Dashboard Engineer", mandate: "Build and maintain the operational dashboards and the weekly ops-review data pack.", model: sonnet, tier: core, towers: [service-quality, process-excellence] }
+      - { id: kpi-analyst, role: "Operational KPI Analyst", mandate: "Curate KPI definitions and trend analysis so every metric has one agreed meaning and owner.", model: sonnet, tier: core, towers: [service-quality] }
+      - { id: data-quality-steward, role: "Reporting Data Quality Steward", mandate: "Validate reporting inputs and reconcile source data so operational MI is trusted and audit-ready.", model: haiku, tier: support, towers: [service-quality, core-operations] }
+      - { id: ops-reporting-analyst, role: "Operations Reporting Analyst", mandate: "Produce the recurring operational reports and breach/exception logs on schedule.", model: haiku, tier: support, towers: [service-quality] }

package/archetypes/capabilities/product-leader.yaml

@@ -0,0 +1,148 @@
+# CAPABILITY PACK — product-leader
+#
+# The role's capability CATALOGUE: the MCP servers/plugins it needs, its sub-agent
+# org (teams of role specs), its Claude Code skills, and its workflows. Resolved by
+# lib/capability.mjs into a concrete capability surface, with breadth scaled by the
+# altitude's delegationBreadth (broad → all teams+roles; moderate → drop support
+# tiers; narrow → core teams only; none → standard defaults only). The init wizard
+# (Phase 2.5) renders sub-agent definitions / skills / workflows from this and
+# LLM-tailors each to the company context.
+#
+# Function overlay: archetypes/functions/product-leader.yaml. Every team's tower
+# must reference a real tower id from that overlay: roadmap-prioritisation,
+# discovery-research, feature-delivery, design-ux-quality, pmf-metrics,
+# experimentation, cross-functional, gtm-comms. Tiers: lead | core | support.
+# Models: opus | sonnet | haiku.
+
+mcpServers:
+  - { id: linear, purpose: "Roadmap, epics, issues, cycles, and delivery status across product squads", env: [LINEAR_API_KEY], optional: true }
+  - { id: product-analytics, purpose: "Activation/retention/funnel/cohort analytics and experiment readouts (Amplitude/Mixpanel)", env: [PRODUCT_ANALYTICS_API_KEY, PRODUCT_ANALYTICS_PROJECT_ID], optional: true }
+  - { id: figma, purpose: "Design files, prototypes, design-system components, and review threads", env: [FIGMA_ACCESS_TOKEN], optional: true }
+  - { id: user-feedback, purpose: "Aggregated support tickets, NPS/CSAT verbatims, and customer feedback themes", env: [FEEDBACK_API_KEY], optional: true }
+  - { id: context7, purpose: "Up-to-date library/framework/API documentation for spec and feasibility checks", optional: true }
+  - { id: playwright, purpose: "Browser automation for journey walkthroughs, dashboard scrapes, and pre-launch UX checks", optional: true }
+
+skills:
+  - { id: prd-authoring, name: "PRD authoring", trigger: "a feature moves from problem to solution definition", purpose: "Draft a problem-led PRD with hypotheses, scope, acceptance criteria, and success metrics" }
+  - { id: opportunity-assessment, name: "Opportunity assessment", trigger: "a new bet or theme is proposed for the roadmap", purpose: "Size the opportunity, frame the trade-off, and produce a prioritisation recommendation" }
+  - { id: discovery-interview, name: "Discovery interview synthesis", trigger: "customer interviews or feedback batches need turning into insight", purpose: "Synthesise interviews/verbatims into opportunities, jobs-to-be-done, and validated problems" }
+  - { id: experiment-design, name: "Experiment design", trigger: "a hypothesis is ready to test", purpose: "Specify the metric, guardrails, sample/power, variants, and ship/kill thresholds" }
+  - { id: launch-readiness, name: "Launch readiness review", trigger: "a release approaches go/no-go", purpose: "Run the launch checklist across enablement, comms, instrumentation, and rollback" }
+  - { id: usability-review, name: "Usability & accessibility review", trigger: "a flow or design is up for craft review", purpose: "Heuristic + accessibility (WCAG) review of a journey against the design-system bar" }
+  - { id: metrics-readout, name: "Metrics readout", trigger: "weekly cadence", purpose: "Synthesise the north-star tree, activation/retention, and live experiments into a decision read" }
+  - { id: roadmap-narrative, name: "Roadmap narrative", trigger: "a planning cycle or stakeholder update is due", purpose: "Translate the now/next/later roadmap into an outcome-led narrative for stakeholders" }
+
+workflows:
+  - { id: roadmap-review, name: "Roadmap & prioritisation review", cadence: weekly, purpose: "Re-rank the backlog against outcomes and capacity; flag commitment risk to the principal" }
+  - { id: discovery-cadence, name: "Continuous discovery cadence", cadence: weekly, purpose: "Keep the customer-interview cadence live and route insight into the opportunity backlog" }
+  - { id: experiment-pipeline, name: "Experiment pipeline review", cadence: weekly, purpose: "Review live experiments, call ship/kill decisions, and queue the next tests" }
+  - { id: pmf-metrics-readout, name: "PMF & metrics readout", cadence: weekly, purpose: "Roll up the north-star tree and activation/retention curves; surface segment-fit signal" }
+  - { id: launch-readiness, name: "Launch readiness gate", cadence: event-driven, purpose: "Drive launches through the go/no-go gate: enablement, comms, instrumentation, rollback" }
+  - { id: quarterly-planning, name: "Quarterly product planning", cadence: quarterly, purpose: "Set themes, outcomes, and bets for the cycle and align eng/design/GTM capacity" }
+
+agentTeams:
+  - id: roadmap-strategy
+    name: "Roadmap & Prioritisation"
+    tower: roadmap-prioritisation
+    core: true
+    agents:
+      - { id: roadmap-lead, role: "Head of Roadmap & Prioritisation", mandate: "Own theme-to-now sequencing and the ruthless trade-offs that protect the committed plan.", model: opus, tier: lead, towers: [roadmap-prioritisation] }
+      - { id: portfolio-strategist, role: "Product Portfolio Strategist", mandate: "Balance bets across horizons and segments so the portfolio compounds rather than scatters.", model: opus, tier: core, towers: [roadmap-prioritisation, pmf-metrics] }
+      - { id: prioritisation-analyst, role: "Prioritisation Analyst", mandate: "Score and rank the backlog against outcome value, effort, and confidence on a live model.", model: sonnet, tier: core, towers: [roadmap-prioritisation] }
+      - { id: capacity-planner, role: "Capacity & Commitment Planner", mandate: "Reconcile roadmap commitments against eng/design capacity and flag over-commitment early.", model: sonnet, tier: core, towers: [roadmap-prioritisation, cross-functional] }
+      - { id: trade-off-facilitator, role: "Trade-off Facilitator", mandate: "Frame the say-no decisions with evidence so the team protects the yes.", model: sonnet, tier: support, towers: [roadmap-prioritisation] }
+      - { id: backlog-groomer, role: "Backlog Groomer", mandate: "Keep the backlog clean, deduplicated, and tagged to themes and outcomes.", model: haiku, tier: support, towers: [roadmap-prioritisation] }
+
+  - id: discovery-research
+    name: "Discovery & User Research"
+    tower: discovery-research
+    core: true
+    agents:
+      - { id: research-lead, role: "Head of Product Discovery & Research", mandate: "Own continuous discovery and the bar for validating problems before solutions are built.", model: opus, tier: lead, towers: [discovery-research] }
+      - { id: ux-researcher, role: "UX Researcher", mandate: "Run generative and evaluative studies that surface unmet needs and usability blockers.", model: sonnet, tier: core, towers: [discovery-research, design-ux-quality] }
+      - { id: customer-interviewer, role: "Customer Interview Lead", mandate: "Keep the weekly interview cadence live and turn conversations into validated opportunities.", model: sonnet, tier: core, towers: [discovery-research] }
+      - { id: insight-synthesiser, role: "Insight Synthesiser", mandate: "Synthesise interviews and verbatims into jobs-to-be-done and an opportunity backlog.", model: sonnet, tier: core, towers: [discovery-research] }
+      - { id: voice-of-customer-analyst, role: "Voice-of-Customer Analyst", mandate: "Cluster support tickets, NPS, and feedback themes into prioritised customer pain signal.", model: haiku, tier: support, towers: [discovery-research, cross-functional] }
+      - { id: research-ops-coordinator, role: "Research Ops Coordinator", mandate: "Recruit participants, maintain the insight repository, and keep consent and panels clean.", model: haiku, tier: support, towers: [discovery-research] }
+
+  - id: feature-delivery
+    name: "Feature Delivery"
+    tower: feature-delivery
+    core: true
+    agents:
+      - { id: delivery-lead, role: "Head of Feature Delivery", mandate: "Own spec quality, eng partnership, and ship confidence from kickoff to release.", model: opus, tier: lead, towers: [feature-delivery] }
+      - { id: senior-pm, role: "Senior Product Manager", mandate: "Own a product area end-to-end: problem, PRD, acceptance criteria, and outcome.", model: opus, tier: core, towers: [feature-delivery, roadmap-prioritisation] }
+      - { id: technical-pm, role: "Technical Product Manager", mandate: "Own platform/API and integration-heavy features in deep partnership with engineering.", model: sonnet, tier: core, towers: [feature-delivery, cross-functional] }
+      - { id: spec-writer, role: "Product Spec Writer", mandate: "Turn validated problems into crisp PRDs with hypotheses, scope, and success metrics.", model: sonnet, tier: core, towers: [feature-delivery] }
+      - { id: scope-steward, role: "Scope Discipline Steward", mandate: "Guard scope against creep and keep delivery tied to the smallest valuable increment.", model: sonnet, tier: support, towers: [feature-delivery] }
+      - { id: release-coordinator, role: "Release Coordinator", mandate: "Track delivery status across cycles and surface blockers to ship dates.", model: haiku, tier: support, towers: [feature-delivery] }
+
+  - id: design-ux
+    name: "Design System & UX Quality"
+    tower: design-ux-quality
+    core: true
+    agents:
+      - { id: design-lead, role: "Head of Design & UX Quality", mandate: "Own design-system coherence and the end-to-end journey-craft and accessibility bar.", model: opus, tier: lead, towers: [design-ux-quality] }
+      - { id: product-designer, role: "Senior Product Designer", mandate: "Design end-to-end flows that are usable, coherent, and on-system.", model: sonnet, tier: core, towers: [design-ux-quality, feature-delivery] }
+      - { id: design-system-steward, role: "Design System Steward", mandate: "Maintain component coverage, tokens, and consistency so teams build on-system by default.", model: sonnet, tier: core, towers: [design-ux-quality] }
+      - { id: interaction-designer, role: "Interaction & Prototyping Designer", mandate: "Prototype interactions and motion to de-risk flows before engineering builds them.", model: sonnet, tier: support, towers: [design-ux-quality] }
+      - { id: accessibility-specialist, role: "Accessibility Specialist", mandate: "Hold the WCAG bar across journeys and close accessibility defects before launch.", model: haiku, tier: support, towers: [design-ux-quality] }
+      - { id: ux-content-strategist, role: "UX Content Strategist", mandate: "Own in-product copy, terminology, and microcopy so the voice stays clear and consistent.", model: haiku, tier: support, towers: [design-ux-quality, gtm-comms] }
+
+  - id: pmf-growth
+    name: "Product-Market Fit & Growth"
+    tower: pmf-metrics
+    core: true
+    agents:
+      - { id: pmf-lead, role: "Head of Product-Market Fit & Growth", mandate: "Own the north-star metric, activation, and retention as the signal of segment fit.", model: opus, tier: lead, towers: [pmf-metrics] }
+      - { id: growth-pm, role: "Growth Product Manager", mandate: "Own activation and onboarding loops that turn signups into retained, active users.", model: sonnet, tier: core, towers: [pmf-metrics, feature-delivery] }
+      - { id: retention-analyst, role: "Retention & Cohort Analyst", mandate: "Read retention and cohort curves to find where and why users disengage.", model: sonnet, tier: core, towers: [pmf-metrics, experimentation] }
+      - { id: segment-fit-analyst, role: "Segment-Fit Analyst", mandate: "Map fit signal by segment and surface where the product earns its keep and where it does not.", model: sonnet, tier: support, towers: [pmf-metrics] }
+      - { id: monetisation-analyst, role: "Pricing & Packaging Analyst", mandate: "Model pricing and packaging options against willingness-to-pay and fit signal.", model: sonnet, tier: support, towers: [pmf-metrics, gtm-comms] }
+      - { id: north-star-steward, role: "North-Star Metric Steward", mandate: "Maintain the north-star definition and its input tree so everyone optimises the same thing.", model: haiku, tier: support, towers: [pmf-metrics] }
+
+  - id: analytics-experimentation
+    name: "Analytics & Experimentation"
+    tower: experimentation
+    core: false
+    agents:
+      - { id: experimentation-lead, role: "Head of Analytics & Experimentation", mandate: "Own instrumentation, A/B rigour, experiment velocity, and the quality of decisions they drive.", model: opus, tier: lead, towers: [experimentation] }
+      - { id: experiment-designer, role: "Experiment Designer", mandate: "Specify metrics, guardrails, sample/power, and ship/kill thresholds for every test.", model: sonnet, tier: core, towers: [experimentation] }
+      - { id: product-data-analyst, role: "Product Data Analyst", mandate: "Read funnels, cohorts, and experiment results into clear, decision-ready findings.", model: sonnet, tier: core, towers: [experimentation, pmf-metrics] }
+      - { id: instrumentation-engineer, role: "Analytics Instrumentation Engineer", mandate: "Own the tracking plan and event schema so the data behind decisions is trustworthy.", model: sonnet, tier: core, towers: [experimentation] }
+      - { id: ab-platform-steward, role: "Experiment Platform Steward", mandate: "Run the feature-flag and experiment platform and keep the experiment queue moving.", model: haiku, tier: support, towers: [experimentation] }
+      - { id: metrics-governance-analyst, role: "Metrics Governance Analyst", mandate: "Audit metric definitions and data quality so reported numbers reconcile and hold up.", model: haiku, tier: support, towers: [experimentation] }
+
+  - id: cross-functional-alignment
+    name: "Cross-Functional Alignment"
+    tower: cross-functional
+    core: false
+    agents:
+      - { id: alignment-lead, role: "Head of Cross-Functional Alignment", mandate: "Keep eng, design, data, and GTM coherent on what ships and why it ships.", model: opus, tier: lead, towers: [cross-functional] }
+      - { id: eng-partner-pm, role: "Engineering Partnership PM", mandate: "Hold the product-eng interface so feasibility, sequencing, and ship dates stay honest.", model: sonnet, tier: core, towers: [cross-functional, feature-delivery] }
+      - { id: data-partner-pm, role: "Data Partnership PM", mandate: "Align with data on metric definitions, instrumentation, and experiment support.", model: sonnet, tier: core, towers: [cross-functional, experimentation] }
+      - { id: dependency-coordinator, role: "Dependency Coordinator", mandate: "Track cross-team dependencies and surface the ones that threaten committed dates.", model: haiku, tier: support, towers: [cross-functional, roadmap-prioritisation] }
+      - { id: alignment-comms-writer, role: "Alignment Comms Writer", mandate: "Write the decision notes and updates that keep partner teams on the same page.", model: haiku, tier: support, towers: [cross-functional, gtm-comms] }
+
+  - id: gtm-launch
+    name: "Launch & GTM"
+    tower: gtm-comms
+    core: false
+    agents:
+      - { id: gtm-lead, role: "Head of Launch & GTM", mandate: "Own launch readiness, positioning input, and the stakeholder narrative around releases.", model: opus, tier: lead, towers: [gtm-comms] }
+      - { id: launch-manager, role: "Product Launch Manager", mandate: "Drive launches through the go/no-go gate and own the release runbook end-to-end.", model: sonnet, tier: core, towers: [gtm-comms, feature-delivery] }
+      - { id: product-marketing-pm, role: "Product Marketing PM", mandate: "Shape positioning, messaging, and the value narrative for each launch.", model: sonnet, tier: core, towers: [gtm-comms, pmf-metrics] }
+      - { id: enablement-lead, role: "GTM Enablement Lead", mandate: "Equip sales and success with the docs, demos, and FAQs to land the launch.", model: sonnet, tier: support, towers: [gtm-comms, cross-functional] }
+      - { id: release-notes-writer, role: "Release Notes & Changelog Writer", mandate: "Write release notes and changelogs in the agent's voice for customers and stakeholders.", model: haiku, tier: support, towers: [gtm-comms] }
+      - { id: launch-comms-coordinator, role: "Launch Comms Coordinator", mandate: "Sequence internal and external launch comms so announcements land in the right order.", model: haiku, tier: support, towers: [gtm-comms] }
+
+  - id: product-ops
+    name: "Product Operations"
+    tower: roadmap-prioritisation
+    core: false
+    agents:
+      - { id: product-ops-lead, role: "Head of Product Operations", mandate: "Own the operating cadence, tooling, and rituals that let the product org run predictably.", model: opus, tier: lead, towers: [roadmap-prioritisation, cross-functional] }
+      - { id: roadmap-ops-analyst, role: "Roadmap Ops Analyst", mandate: "Keep the roadmap tool, status, and reporting accurate and current across squads.", model: sonnet, tier: core, towers: [roadmap-prioritisation] }
+      - { id: product-kpi-analyst, role: "Product KPI Analyst", mandate: "Maintain the product KPI tree and assemble the weekly metrics readout.", model: sonnet, tier: core, towers: [pmf-metrics, experimentation] }
+      - { id: feedback-ops-coordinator, role: "Feedback Ops Coordinator", mandate: "Route inbound feedback and feature requests into the right backlog stream with triage tags.", model: haiku, tier: support, towers: [discovery-research, cross-functional] }
+      - { id: rituals-coordinator, role: "Rituals & Cadence Coordinator", mandate: "Run planning, review, and retro rituals and keep their inputs and notes tidy.", model: haiku, tier: support, towers: [roadmap-prioritisation] }