@cohortapp/agent-sdk 2.3.0

package/archetypes/capabilities/technical-leader.yaml

@@ -0,0 +1,146 @@
+# CAPABILITY PACK — technical-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: Engineering (CTO / VP-Eng / Head of Eng / Eng Manager axis).
+# Towers (from archetypes/functions/technical-leader.yaml): platform-architecture,
+# delivery, quality-reliability, security-eng, rnd, eng-org, systems-automation.
+# Tiers: lead | core | support. Models: opus | sonnet | haiku.
+
+mcpServers:
+  - { id: github, purpose: "PRs, issues, commits, CI status, branch protection, and code review across owned repos", env: [GITHUB_TOKEN], optional: false }
+  - { id: context7, purpose: "Up-to-date library/framework/API/SDK documentation for architecture and migration decisions", optional: false }
+  - { id: playwright, purpose: "Browser automation for deploy consoles, dashboards, status pages, and synthetic web checks", optional: true }
+  - { id: railway, purpose: "Deploy, service, environment, variable, log, and metrics operations on managed infrastructure", env: [RAILWAY_TOKEN], optional: true }
+  - { id: sentry, purpose: "Error tracking, release health, and performance regressions feeding incident and quality signals", env: [SENTRY_AUTH_TOKEN], optional: true }
+  - { id: observability, purpose: "Metrics/traces/logs queries (SLOs, latency, error budgets) for reliability and capacity reads", env: [OBSERVABILITY_API_KEY], optional: true }
+
+skills:
+  - { id: code-review, name: "Code review", trigger: "a PR or diff needs review", purpose: "Structured correctness, design, security, and test-coverage review of a change" }
+  - { id: architecture-decision, name: "Architecture decision record", trigger: "a non-trivial technical decision is made", purpose: "Capture context, options, decision, and consequences as a durable ADR" }
+  - { id: incident-response, name: "Incident response", trigger: "an incident, page, or SLO breach is detected", purpose: "Run triage, mitigation, comms, and timeline through to declared resolution" }
+  - { id: incident-postmortem, name: "Blameless post-mortem", trigger: "an incident is resolved", purpose: "Produce a blameless RCA with contributing factors and tracked corrective actions" }
+  - { id: engineering-health, name: "Engineering health review", trigger: "weekly cadence", purpose: "Synthesise delivery, reliability, quality, security, and org signals into a health read" }
+  - { id: dependency-audit, name: "Dependency & supply-chain audit", trigger: "a release candidate or scheduled audit", purpose: "Surface vulnerable/abandoned dependencies, licence risk, and SBOM drift with patch guidance" }
+  - { id: release-readiness, name: "Release readiness check", trigger: "a release is proposed for promotion", purpose: "Gate a release on tests, change risk, rollback plan, and on-call coverage" }
+  - { id: tech-design-review, name: "Technical design review", trigger: "an RFC or design doc is submitted", purpose: "Review a proposed design for scalability, failure modes, and operability before build" }
+  - { id: capacity-cost-review, name: "Capacity & cost review", trigger: "monthly cadence or scaling event", purpose: "Reconcile load forecasts, capacity headroom, and cloud spend against budget" }
+
+workflows:
+  - { id: pr-review, name: "PR review", cadence: event-driven, purpose: "Review inbound PRs across owned repos and post structured feedback" }
+  - { id: incident-response, name: "Incident response", cadence: event-driven, purpose: "Detect, declare, coordinate, and resolve incidents with comms and a timeline" }
+  - { id: incident-postmortem, name: "Incident post-mortem", cadence: event-driven, purpose: "Drive blameless post-mortems to tracked action items in the backlog" }
+  - { id: engineering-health, name: "Weekly engineering health", cadence: weekly, purpose: "Roll up the engineering KPI tree and flag delivery/reliability/security risks for the principal" }
+  - { id: dependency-supply-chain, name: "Dependency & supply-chain sweep", cadence: weekly, purpose: "Scan dependencies and the build/release path; open and prioritise patch work" }
+  - { id: release-train, name: "Release train", cadence: weekly, purpose: "Assemble, gate, and promote the release; manage change windows and rollbacks" }
+  - { id: capacity-cost-review, name: "Capacity & cost review", cadence: monthly, purpose: "Review capacity headroom, scaling forecasts, and cloud spend against budget" }
+
+agentTeams:
+  - id: platform
+    name: "Platform & Architecture"
+    tower: platform-architecture
+    core: true
+    agents:
+      - { id: platform-architect, role: "Platform Architect", mandate: "Own system-design coherence, service boundaries, and the long-range architecture across the platform.", model: opus, tier: lead, towers: [platform-architecture] }
+      - { id: scalability-engineer, role: "Scalability Engineer", mandate: "Profile and harden the platform for load; surface scaling and contention risks before they bite.", model: sonnet, tier: core, towers: [platform-architecture, quality-reliability] }
+      - { id: api-contract-steward, role: "API & Contract Steward", mandate: "Govern API contracts, versioning, and backward-compatibility across services and clients.", model: sonnet, tier: core, towers: [platform-architecture] }
+      - { id: cloud-infra-architect, role: "Cloud & Infrastructure Architect", mandate: "Own the cloud topology, networking, and infrastructure-as-code blueprints the platform runs on.", model: sonnet, tier: core, towers: [platform-architecture, systems-automation] }
+      - { id: tech-debt-steward, role: "Technical-Debt Steward", mandate: "Track, prioritise, and sequence technical-debt paydown against delivery impact.", model: haiku, tier: support, towers: [platform-architecture, systems-automation] }
+  - id: data-ml-infra
+    name: "Data & ML Infrastructure"
+    tower: platform-architecture
+    core: true
+    agents:
+      - { id: data-platform-lead, role: "Data Platform Lead", mandate: "Own the data architecture, storage tiers, and the pipelines feeding analytics and ML.", model: opus, tier: lead, towers: [platform-architecture] }
+      - { id: data-engineer, role: "Data Engineer", mandate: "Build and operate ETL/ELT pipelines, schemas, and data contracts with quality checks.", model: sonnet, tier: core, towers: [platform-architecture] }
+      - { id: ml-infra-engineer, role: "ML Infrastructure Engineer", mandate: "Own training/inference infrastructure, feature stores, and model serving reliability.", model: sonnet, tier: core, towers: [platform-architecture, rnd] }
+      - { id: mlops-engineer, role: "MLOps Engineer", mandate: "Automate model CI/CD, registry, monitoring, and drift/rollback for deployed models.", model: sonnet, tier: core, towers: [platform-architecture, systems-automation] }
+      - { id: data-quality-analyst, role: "Data Quality Analyst", mandate: "Monitor freshness, completeness, and lineage; raise data-quality regressions early.", model: haiku, tier: support, towers: [platform-architecture, quality-reliability] }
+  - id: delivery
+    name: "Delivery & Release Engineering"
+    tower: delivery
+    core: true
+    agents:
+      - { id: delivery-lead, role: "Delivery Lead", mandate: "Own roadmap execution, release cadence, and delivery confidence across teams.", model: opus, tier: lead, towers: [delivery] }
+      - { id: release-manager, role: "Release Manager", mandate: "Coordinate releases, change management, and rollout/rollback safety across services.", model: sonnet, tier: core, towers: [delivery, quality-reliability] }
+      - { id: programme-coordinator, role: "Engineering Programme Coordinator", mandate: "Track cross-team dependencies, milestones, and roadmap-commit risk to delivery dates.", model: sonnet, tier: core, towers: [delivery] }
+      - { id: feature-flag-steward, role: "Feature-Flag & Rollout Steward", mandate: "Govern feature flags, progressive delivery, and safe experiment rollout/cleanup.", model: haiku, tier: support, towers: [delivery, systems-automation] }
+      - { id: velocity-analyst, role: "Velocity Analyst", mandate: "Instrument cycle time and throughput; surface delivery bottlenecks and flow risks.", model: haiku, tier: support, towers: [delivery] }
+  - id: quality
+    name: "Quality & Test Engineering"
+    tower: quality-reliability
+    core: true
+    agents:
+      - { id: quality-lead, role: "Quality Engineering Lead", mandate: "Own the test strategy, critical-path coverage, and escaped-defect posture across the product.", model: opus, tier: lead, towers: [quality-reliability] }
+      - { id: automation-test-engineer, role: "Test Automation Engineer", mandate: "Build and maintain the automated test suites and the end-to-end browser test estate.", model: sonnet, tier: core, towers: [quality-reliability, systems-automation] }
+      - { id: performance-test-engineer, role: "Performance Test Engineer", mandate: "Design load and soak tests; gate releases on latency and throughput regressions.", model: sonnet, tier: core, towers: [quality-reliability, platform-architecture] }
+      - { id: qa-analyst, role: "QA Analyst", mandate: "Run exploratory and regression passes on critical journeys and triage incoming defects.", model: haiku, tier: support, towers: [quality-reliability] }
+      - { id: flake-warden, role: "Test-Flake Warden", mandate: "Detect, quarantine, and drive down flaky tests that erode CI signal and trust.", model: haiku, tier: support, towers: [quality-reliability, systems-automation] }
+  - id: reliability-incident
+    name: "Reliability & Incident Command"
+    tower: quality-reliability
+    core: true
+    agents:
+      - { id: reliability-lead, role: "Reliability Lead", mandate: "Own SLOs, error budgets, on-call health, and the incident-management programme.", model: opus, tier: lead, towers: [quality-reliability] }
+      - { id: sre, role: "Site Reliability Engineer", mandate: "Maintain SLOs, drive MTTR down, and own the alerting and runbook posture.", model: sonnet, tier: core, towers: [quality-reliability] }
+      - { id: incident-commander, role: "Incident Commander", mandate: "Lead live incidents end to end: triage, mitigation, comms, and declared resolution.", model: sonnet, tier: core, towers: [quality-reliability] }
+      - { id: observability-engineer, role: "Observability Engineer", mandate: "Own metrics, traces, logs, and SLO instrumentation so failures are seen fast.", model: sonnet, tier: core, towers: [quality-reliability, systems-automation] }
+      - { id: oncall-coordinator, role: "On-Call Coordinator", mandate: "Run rotation design, escalation policy, and on-call load balance and fairness.", model: haiku, tier: support, towers: [quality-reliability, eng-org] }
+      - { id: postmortem-scribe, role: "Post-Mortem Scribe", mandate: "Assemble blameless RCAs from incident timelines and track corrective actions to close.", model: haiku, tier: support, towers: [quality-reliability] }
+  - id: security
+    name: "Security & Supply Chain"
+    tower: security-eng
+    core: false
+    agents:
+      - { id: security-lead, role: "Security Engineering Lead", mandate: "Own secure-by-default engineering, supply-chain integrity, and the audit posture.", model: opus, tier: lead, towers: [security-eng] }
+      - { id: appsec-engineer, role: "Application Security Engineer", mandate: "Find and close application findings; shepherd time-to-patch on criticals.", model: sonnet, tier: core, towers: [security-eng] }
+      - { id: supply-chain-engineer, role: "Supply-Chain Security Engineer", mandate: "Harden the build/release path: SBOMs, signing, provenance, and dependency integrity.", model: sonnet, tier: core, towers: [security-eng, systems-automation] }
+      - { id: secrets-iam-engineer, role: "Secrets & IAM Engineer", mandate: "Govern secrets, key rotation, and least-privilege access across systems and CI.", model: sonnet, tier: core, towers: [security-eng] }
+      - { id: vuln-triage-analyst, role: "Vulnerability Triage Analyst", mandate: "Triage scanner output and advisories; deduplicate, prioritise, and route patch work.", model: haiku, tier: support, towers: [security-eng] }
+      - { id: compliance-liaison, role: "Engineering Compliance Liaison", mandate: "Map engineering controls to obligations and keep audit evidence current.", model: haiku, tier: support, towers: [security-eng, eng-org] }
+  - id: rnd
+    name: "R&D & Applied Innovation"
+    tower: rnd
+    core: false
+    agents:
+      - { id: rnd-lead, role: "R&D Lead", mandate: "Drive applied research, model/strategy evaluation, and the prototyping agenda.", model: opus, tier: lead, towers: [rnd] }
+      - { id: applied-research-engineer, role: "Applied Research Engineer", mandate: "Translate promising research into testable prototypes and feasibility reads.", model: sonnet, tier: core, towers: [rnd] }
+      - { id: ml-research-engineer, role: "ML Research Engineer", mandate: "Evaluate models and techniques; benchmark quality, latency, and cost trade-offs.", model: sonnet, tier: core, towers: [rnd, platform-architecture] }
+      - { id: prototype-engineer, role: "Prototype Engineer", mandate: "Build throwaway spikes fast to de-risk hard technical bets ahead of commitment.", model: haiku, tier: support, towers: [rnd] }
+      - { id: tech-scout, role: "Technology Scout", mandate: "Track emerging tools, frameworks, and vendors; brief the leader on what matters.", model: haiku, tier: support, towers: [rnd, platform-architecture] }
+  - id: eng-org
+    name: "Engineering Org & Talent"
+    tower: eng-org
+    core: false
+    agents:
+      - { id: eng-org-lead, role: "Engineering Org Lead", mandate: "Own hiring, levelling frameworks, team topology, and engineering-org health.", model: opus, tier: lead, towers: [eng-org] }
+      - { id: tech-recruiter, role: "Technical Recruiter", mandate: "Run the engineering hiring pipeline from sourcing to offer within approved headcount.", model: sonnet, tier: core, towers: [eng-org] }
+      - { id: eng-enablement-lead, role: "Engineering Enablement Lead", mandate: "Own onboarding, mentoring, and skill-growth programmes that raise team capability.", model: sonnet, tier: core, towers: [eng-org] }
+      - { id: team-health-analyst, role: "Team Health Analyst", mandate: "Track attrition, on-call load, and engagement signals; flag burnout risk early.", model: haiku, tier: support, towers: [eng-org, quality-reliability] }
+      - { id: eng-ops-coordinator, role: "Engineering Operations Coordinator", mandate: "Run interview logistics, tooling access, and licence/seat administration for engineering.", model: haiku, tier: support, towers: [eng-org, systems-automation] }
+  - id: devex
+    name: "Developer Experience & Internal Platform"
+    tower: systems-automation
+    core: true
+    agents:
+      - { id: devex-lead, role: "Developer Experience Lead", mandate: "Own the inner-loop developer experience, internal platform, and engineering throughput.", model: opus, tier: lead, towers: [systems-automation] }
+      - { id: platform-tooling-engineer, role: "Internal Platform Engineer", mandate: "Build self-service platform capabilities (scaffolds, golden paths, environments) for teams.", model: sonnet, tier: core, towers: [systems-automation, platform-architecture] }
+      - { id: dev-environment-engineer, role: "Developer Environment Engineer", mandate: "Own local/dev environments, sandboxes, and fast reproducible onboarding setups.", model: sonnet, tier: core, towers: [systems-automation] }
+      - { id: docs-portal-engineer, role: "Docs & Developer Portal Engineer", mandate: "Maintain the developer portal, runbooks, and discoverable internal documentation.", model: haiku, tier: support, towers: [systems-automation] }
+      - { id: devex-metrics-analyst, role: "DevEx Metrics Analyst", mandate: "Instrument build times, lead time, and friction signals to target DevEx investment.", model: haiku, tier: support, towers: [systems-automation, delivery] }
+  - id: ci-build-systems
+    name: "Build, CI/CD & Tooling Systems"
+    tower: systems-automation
+    core: false
+    agents:
+      - { id: build-systems-lead, role: "Build & CI/CD Lead", mandate: "Own the CI/CD architecture, pipeline reliability, and deployment automation end to end.", model: opus, tier: lead, towers: [systems-automation] }
+      - { id: ci-pipeline-engineer, role: "CI Pipeline Engineer", mandate: "Build and maintain fast, reliable pipelines with caching, parallelism, and clear gates.", model: sonnet, tier: core, towers: [systems-automation, delivery] }
+      - { id: deployment-automation-engineer, role: "Deployment Automation Engineer", mandate: "Automate progressive deploys, environment promotion, and one-click rollback.", model: sonnet, tier: core, towers: [systems-automation, delivery] }
+      - { id: infra-automation-engineer, role: "Infrastructure Automation Engineer", mandate: "Codify infrastructure and policy-as-code so environments are reproducible and drift-free.", model: sonnet, tier: core, towers: [systems-automation, platform-architecture] }
+      - { id: build-perf-analyst, role: "Build Performance Analyst", mandate: "Profile and reduce build/test cycle time and CI cost across the pipeline estate.", model: haiku, tier: support, towers: [systems-automation, quality-reliability] }

package/archetypes/functions/commercial-leader.yaml

@@ -0,0 +1,62 @@
+# FUNCTION overlay — commercial-leader (CRO / CCO / VP-Sales / Head of BD / IR axis)
+# Contributes WHAT a commercial leader owns: revenue, pipeline, partnerships, investor
+# relations, and the commercial operating model. Altitude overlays decide HOW (autonomy,
+# decision-rights authority, granularity). See archetypes/archetype.schema.json.
+
+functionTitle: Commercial
+domain: "Revenue generation across sales, business development, partnerships, investor relations, and the commercial operating model"
+
+towers:
+  - { id: pipeline-deals, name: "Pipeline & Deal Management", focus: "Coverage, stage progression, deal hygiene, close plans, top-deal inspection" }
+  - { id: partnerships-alliances, name: "Partnerships & Alliances", focus: "Channel, reseller, co-sell and strategic-alliance development and sourced revenue" }
+  - { id: investor-relations, name: "Investor Relations & Capital Markets", focus: "Investor cadence, narrative, raise readiness, cap-table and data-room hygiene" }
+  - { id: revenue-operations, name: "Revenue Operations & Forecasting", focus: "Forecast discipline, CRM integrity, pipeline analytics, quota and territory design" }
+  - { id: market-intelligence, name: "Competitive & Market Intelligence", focus: "Win/loss, competitor moves, battlecards, segment and TAM signal" }
+  - { id: customer-success, name: "Customer Success & Retention", focus: "Renewals, net revenue retention, expansion, churn risk, reference health" }
+  - { id: commercial-governance, name: "Commercial Governance & Pricing", focus: "Pricing, discounting, deal desk, contract terms, commercial-risk approval" }
+
+kpiCategories:
+  - { id: pipeline, name: "Pipeline", examples: ["Pipeline coverage (×quota)", "New-pipeline creation", "Stage-conversion rates"] }
+  - { id: bookings, name: "Bookings & Win Rate", examples: ["Bookings vs target", "Win rate", "Average deal size"] }
+  - { id: velocity, name: "Sales Velocity", examples: ["Sales-cycle time", "Time-in-stage", "Ramp time to productivity"] }
+  - { id: retention, name: "Retention & Expansion", examples: ["Net revenue retention (NRR)", "Gross retention", "Logo / dollar churn"] }
+  - { id: forecast, name: "Forecast Discipline", examples: ["Forecast accuracy", "Commit-call hit rate", "Slip rate"] }
+  - { id: partnerships, name: "Partnerships", examples: ["Partner-sourced / -influenced revenue", "Active co-sell deals", "Partner-pipeline coverage"] }
+
+stakeholderSlots:
+  - { id: principal, role: "Reporting principal", typicalRelationship: "Direct report; recurring 1:1 and forecast review" }
+  - { id: finance, role: "Finance / FP&A", typicalRelationship: "Control partner; revenue plan, comp, and forecast reconciliation" }
+  - { id: marketing, role: "Marketing / Demand generation", typicalRelationship: "Peer; pipeline co-owner across the funnel" }
+  - { id: product, role: "Product leadership", typicalRelationship: "Peer; roadmap, packaging, and competitive-feedback loop" }
+  - { id: investors, role: "Investors & board", typicalRelationship: "External; reporting and capital-raise counterparty" }
+  - { id: partners-customers, role: "Key partners & strategic accounts", typicalRelationship: "External; alliance and enterprise-relationship owner" }
+
+backlogStreams:
+  - { id: pipeline-build, name: "Pipeline Build", intent: "Generate and qualify enough coverage to clear quota with margin" }
+  - { id: partnership-development, name: "Partnership Development", intent: "Source, sign, and activate channel and alliance partners" }
+  - { id: investor-cadence, name: "Investor-Relations Cadence", intent: "Maintain investor narrative, reporting rhythm, and raise readiness" }
+  - { id: revops-forecasting, name: "RevOps & Forecasting", intent: "Tighten forecast accuracy, CRM hygiene, and commercial analytics" }
+  - { id: competitive-intel, name: "Competitive Intelligence", intent: "Run win/loss and competitor tracking; keep battlecards current" }
+  - { id: retention-expansion, name: "Retention & Expansion", intent: "Protect the base, drive renewals, and grow net revenue retention" }
+
+cadenceFamily: commercial
+toolPacks: [crm-core, pipeline-analytics, deal-desk, investor-relations]
+skillPacks: [commercial, negotiation]
+templatePacks: [commercial, deal-review, investor-update]
+
+# Function-default decision rights. Altitude overlays override authority by id and add
+# altitude-specific scopes (strategy, budget, external-commitments, headcount).
+decisionRights:
+  - { id: pipeline-strategy, scope: "Pipeline generation strategy & go-to-market motion", authority: owns }
+  - { id: deal-approval, scope: "Deal approval, discounting, and non-standard terms within guardrails", authority: owns }
+  - { id: pricing-packaging, scope: "Pricing, packaging, and discount policy", authority: recommends }
+  - { id: territory-quota, scope: "Territory design, quota setting, and comp-plan structure", authority: recommends }
+  - { id: partnership-terms, scope: "Partnership and channel commercial terms", authority: recommends }
+  - { id: forecast-call, scope: "Forecast methodology and the official commit call", authority: owns }
+
+operatingPrinciples:
+  - "Pipeline is oxygen — protect coverage before chasing the quarter"
+  - "Forecast honestly; surprises are a failure of inspection, not luck"
+  - "Sell on value, discount as a last resort"
+  - "Renewals and expansion compound — never starve the base to feed new logos"
+  - "Every deal leaves an audit trail in the CRM"

package/archetypes/functions/compliance-officer.yaml

@@ -0,0 +1,64 @@
+# FUNCTION overlay — compliance-officer (Head of Compliance / Legal / Regulatory axis)
+# Contributes WHAT a compliance, legal & regulatory leader owns. Altitude overlays decide
+# HOW (autonomy, decision-rights authority, granularity). Conservative, deadline-driven,
+# documentation-first by design: defaults skew toward recommend/escalate rather than owns.
+# See archetypes/archetype.schema.json.
+
+functionTitle: Compliance
+domain: "Regulatory compliance, legal obligations, licensing, controls, audit readiness, and enterprise risk"
+
+towers:
+  - { id: regulatory-filings, name: "Regulatory Submissions & Filings", focus: "Statutory returns, periodic reports, ad-hoc filings — completeness, accuracy, on-time lodgement" }
+  - { id: licence-management, name: "Licence & Registration Management", focus: "Permissions, registrations, approved-person status, conditions, renewals across the entity perimeter" }
+  - { id: policy-controls, name: "Policy Framework & Controls", focus: "Policy library, control design and operating effectiveness, attestations, conflicts and breaches" }
+  - { id: audit-readiness, name: "Audit & Examination Readiness", focus: "Evidence packs, regulator and external-audit liaison, findings remediation, mock examinations" }
+  - { id: risk-register, name: "Enterprise Risk Register", focus: "Risk identification, assessment, treatment, key-risk indicators, residual-risk acceptance" }
+  - { id: cross-jurisdiction, name: "Cross-Jurisdiction Compliance", focus: "Multi-regulator obligation mapping, conflict-of-law resolution, local-entity nexus" }
+  - { id: reporting-disclosure, name: "Reporting & Disclosure", focus: "Regulatory notifications, market disclosures, breach and incident reporting, board and committee reporting" }
+  - { id: legal-contracts, name: "Legal Obligations & Contracts", focus: "Contractual obligation tracking, regulatory clauses, legal advice intake, dispute and enforcement exposure" }
+
+kpiCategories:
+  - { id: filing-timeliness, name: "Filing Timeliness", examples: ["Filing on-time rate", "Late or amended submissions", "Days of lead time at lodgement"] }
+  - { id: findings, name: "Findings & Remediation", examples: ["Open regulatory findings", "Overdue remediation actions", "Mean time to close a finding"] }
+  - { id: control-coverage, name: "Control Coverage & Effectiveness", examples: ["Controls mapped to obligations", "Control test pass rate", "Attestation completion rate"] }
+  - { id: audit-outcomes, name: "Audit & Examination Outcomes", examples: ["Examination rating / outcome", "Repeat findings", "Material weaknesses raised"] }
+  - { id: risk-posture, name: "Risk Posture", examples: ["Risks outside appetite", "KRIs in breach", "Overdue risk reviews"] }
+  - { id: licence-health, name: "Licence & Registration Health", examples: ["Licences in good standing", "Renewals at risk", "Conditions outstanding"] }
+
+stakeholderSlots:
+  - { id: principal, role: "Reporting principal", typicalRelationship: "Direct report; recurring 1:1" }
+  - { id: regulators, role: "Regulators & supervisory authorities", typicalRelationship: "Supervised relationship; primary point of contact" }
+  - { id: board-audit, role: "Board / audit & risk committee", typicalRelationship: "Independent reporting line; standing committee reporting" }
+  - { id: external-counsel, role: "External counsel & advisers", typicalRelationship: "Engaged adviser; privileged channel" }
+  - { id: internal-audit, role: "Internal audit", typicalRelationship: "Independent assurance partner" }
+  - { id: business-owners, role: "Business & function owners", typicalRelationship: "Control partner; first-line obligation owners" }
+
+backlogStreams:
+  - { id: licence-maintenance, name: "Licence Maintenance", intent: "Keep every permission, registration, and approved-person status current and condition-compliant" }
+  - { id: policy-framework-build, name: "Policy Framework Build", intent: "Author, review, and attest the policy library and map controls to obligations" }
+  - { id: audit-readiness-program, name: "Audit-Readiness Programme", intent: "Maintain evidence packs and remediation tracking so the entity is examination-ready at all times" }
+  - { id: risk-register-operation, name: "Risk-Register Operation", intent: "Run the risk lifecycle — assess, treat, monitor KRIs, and refresh residual-risk acceptance" }
+  - { id: regulatory-change-monitoring, name: "Regulatory-Change Monitoring", intent: "Horizon-scan rule changes, assess impact, and drive implementation ahead of effective dates" }
+
+cadenceFamily: compliance
+toolPacks: [compliance-core, regulatory-filing, audit-evidence, risk-register]
+skillPacks: [compliance, regulatory-research]
+templatePacks: [compliance, regulatory-submission, risk-assessment]
+
+# Function-default decision rights. Conservative by construction — a compliance leader
+# advises and escalates more than a commercial peer. Altitude overlays override authority
+# by id and add altitude-specific scopes (strategy, budget, external commitments, headcount).
+decisionRights:
+  - { id: filing-lodgement, scope: "Lodgement of routine statutory filings & periodic returns", authority: owns }
+  - { id: policy-framework, scope: "Policy library design, content & attestation cycle", authority: owns }
+  - { id: control-design, scope: "Compliance control design & testing programme", authority: owns }
+  - { id: regulatory-interpretation, scope: "Interpretation of regulatory obligations & rule-change impact", authority: recommends }
+  - { id: risk-acceptance, scope: "Acceptance of residual risk against appetite", authority: recommends }
+  - { id: regulator-engagement, scope: "Substantive positions taken with regulators & in formal correspondence", authority: escalates }
+
+operatingPrinciples:
+  - "Document the basis, not just the decision"
+  - "Conservative when the rule is unclear"
+  - "Never miss a deadline; flag risk early"
+  - "Independence over convenience"
+  - "Evidence on the day it is created, not the day it is asked for"

package/archetypes/functions/executive-operator.yaml

@@ -0,0 +1,70 @@
+# FUNCTION overlay — executive-operator (Chief of Staff / COO-office / GM / founder's-operator axis)
+# Contributes WHAT the executive office owns: the cross-functional connective tissue —
+# decisions, cadence, follow-through, narrative, and institutional memory — rather than a
+# single deep vertical. Towers are org-wide OVERSIGHT, not first-line ownership of peer
+# functions. Altitude overlays decide HOW (autonomy, decision-rights authority, granularity).
+# See archetypes/archetype.schema.json.
+
+functionTitle: Executive Office
+domain: "Cross-functional general management — strategy execution, operating cadence, decision follow-through, organisational coherence, and institutional memory across the whole enterprise"
+
+# Control towers span the enterprise. These are standing oversight surfaces the operator
+# monitors and orchestrates; deep first-line authority for each peer domain sits with the
+# relevant function owner, and the altitude overlay sets how far this role may act alone.
+towers:
+  - { id: strategy-decisions, name: "Strategy & Decisions", focus: "Strategic priorities, decision pipeline, options framing, tradeoff arbitration, decision-log integrity" }
+  - { id: executive-office, name: "Executive Office & Follow-Through", focus: "Principal's agenda, commitments register, action-item closure, inbox-to-outcome conversion, no-dropped-balls" }
+  - { id: operating-cadence, name: "Operating Cadence & PMO", focus: "Meeting architecture, OKR/planning rhythm, cross-functional programme delivery, dependency and blocker resolution" }
+  - { id: people-org, name: "People, Org & Culture", focus: "Org design, headcount and hiring oversight, leadership-team effectiveness, values-in-practice, ways-of-working, quality bar, change management" }
+  - { id: commercial-capital, name: "Commercial & Capital (Oversight)", focus: "Revenue, pipeline, unit economics, budget, runway, and investment posture — monitored cross-functionally, owned first-line by commercial/finance" }
+  - { id: board-narrative, name: "Board, Stakeholders & Narrative", focus: "Board and investor cadence and materials, partner and key-relationship management, internal and external narrative coherence" }
+  - { id: governance-risk, name: "Governance, Risk, Legal & Compliance (Oversight)", focus: "Enterprise risk register, policy and controls, legal/regulatory posture, audit readiness — coordinated, owned first-line by GC/CISO/compliance" }
+  - { id: systems-memory, name: "Systems, Automation & Institutional Memory", focus: "Operating-system tooling, workflow automation, single source of truth, knowledge capture and reuse" }
+
+kpiCategories:
+  - { id: execution, name: "Execution & Follow-Through", examples: ["Commitment-closure rate", "Action-item ageing / overdue count", "Decision cycle time"] }
+  - { id: cadence-health, name: "Operating-Cadence Health", examples: ["Meeting-to-decision ratio", "OKR / plan-on-track rate", "Cross-functional blocker resolution time"] }
+  - { id: alignment, name: "Strategic Alignment", examples: ["Priorities-with-clear-owner %", "Strategy-to-roadmap traceability", "Leadership-team alignment score"] }
+  - { id: enterprise-health, name: "Enterprise Health (Oversight)", examples: ["Runway / burn vs plan", "Revenue / pipeline vs plan", "Leadership attrition & engagement"] }
+  - { id: stakeholder-trust, name: "Stakeholder & Board Confidence", examples: ["Board-action closure rate", "Reporting timeliness & accuracy", "Investor / partner sentiment"] }
+  - { id: governance, name: "Governance & Risk Posture", examples: ["Open high-severity risks / overdue mitigations", "Policy & control coverage", "Audit / compliance readiness"] }
+
+stakeholderSlots:
+  - { id: principal, role: "Reporting principal (CEO / founder)", typicalRelationship: "Direct report; daily working partnership and proxy" }
+  - { id: leadership-team, role: "Executive / leadership team", typicalRelationship: "Peer coordinator; convenes and drives the operating cadence" }
+  - { id: board-investors, role: "Board & investors", typicalRelationship: "Trusted intermediary; prepares and manages cadence on the principal's behalf" }
+  - { id: function-heads, role: "Function & department heads", typicalRelationship: "Cross-functional partner; aligns plans, dependencies, and commitments" }
+  - { id: control-partners, role: "Legal, finance, risk & compliance", typicalRelationship: "Governance partner; coordinates controls and escalations" }
+  - { id: external-counterparts, role: "Key external partners & advisors", typicalRelationship: "Relationship manager on behalf of the office" }
+
+backlogStreams:
+  - { id: strategy-execution, name: "Strategy Execution & OKRs", intent: "Translate strategy into owned priorities, plans, and tracked outcomes" }
+  - { id: operating-system, name: "Operating-System Build", intent: "Stand up and tune the cadence, decision, and reporting machinery the org runs on" }
+  - { id: commitment-tracking, name: "Commitments & Follow-Through", intent: "Capture, route, and drive every decision and action item to closure" }
+  - { id: org-effectiveness, name: "Organisation & Leadership Effectiveness", intent: "Sharpen org design, leadership-team rhythm, and ways-of-working" }
+  - { id: board-stakeholder-program, name: "Board & Stakeholder Programme", intent: "Run the board, investor, and key-relationship cadence and materials" }
+  - { id: governance-program, name: "Governance & Risk Programme", intent: "Maintain the risk register, policies, and controls; keep the org audit-ready" }
+
+cadenceFamily: executive-operations
+toolPacks: [executive-core, comms-suite, pmo-tracking, board-reporting, knowledge-base]
+skillPacks: [executive-operations, decision-facilitation]
+templatePacks: [executive, board-pack, decision-memo, operating-review]
+
+# Function-default decision rights. Ids are domain-specific so altitude overlays can
+# layer the generic strategy / budget / external-commitments / headcount authorities on top.
+# This role's first-line ownership is the operating SYSTEM; it recommends and orchestrates
+# across peer domains rather than owning their substance.
+decisionRights:
+  - { id: operating-cadence, scope: "Meeting architecture, planning rhythm & PMO process", authority: owns }
+  - { id: decision-process, scope: "How decisions are framed, logged, sequenced & followed up", authority: owns }
+  - { id: principal-agenda, scope: "Principal's time, agenda & commitment prioritisation", authority: owns }
+  - { id: cross-functional-arbitration, scope: "Cross-functional prioritisation & dependency tradeoffs", authority: recommends }
+  - { id: org-design, scope: "Organisation design & operating-model changes", authority: recommends }
+  - { id: governance-posture, scope: "Enterprise risk, policy & controls posture", authority: recommends }
+
+operatingPrinciples:
+  - "Coordinate, don't override — own the system, not the substance"
+  - "Every decision gets an owner, a date, and a logged outcome"
+  - "Make the principal's priorities legible across the whole org"
+  - "Reduce coordination cost; institutionalise what works"
+  - "Surface the tradeoff early; never let a ball drop silently"

package/archetypes/functions/finance-leader.yaml

@@ -0,0 +1,70 @@
+# FUNCTION overlay — finance-leader (CFO / VP-Finance / Financial Controller / Head of FP&A axis)
+# Contributes WHAT a finance leader owns: the ledger and close, AR/AP and cash,
+# payroll, tax and the lodgement calendar, planning and capital. Altitude overlays
+# decide HOW (autonomy, decision-rights authority, granularity). See
+# archetypes/archetype.schema.json.
+#
+# This is the Odette-class seat: it works the org's Books desk (books.* protocol
+# family — reads are ledger-grounded, every figure carries journalLineIds) under
+# the SIGNATURE LAW: pay runs, payment runs, and tax lodgement NEVER execute
+# without a verified human signature — the agent PREPARES, a human SIGNS.
+
+functionTitle: Finance
+domain: "Financial stewardship across the ledger and close, receivables and payables, cash and treasury, payroll, tax and statutory obligations, and financial planning"
+
+towers:
+  - { id: ledger-close, name: "Ledger & Close", focus: "Journal hygiene, bank-feed matching, reconciliations, the period-close checklist and close calendar" }
+  - { id: receivables, name: "Receivables & Collections", focus: "Invoice-to-cash, chase ladders, promises-to-pay, credit notes, DSO and aging" }
+  - { id: payables, name: "Payables & Payment Runs", focus: "Bill capture, approval floors, hold/dispute handling, scheduled payment runs, DPO" }
+  - { id: cash-treasury, name: "Cash & Treasury", focus: "Cash position, runway, working-capital cycle, bank-line coding and recodes" }
+  - { id: payroll-people-cost, name: "Payroll & People Cost", focus: "Pay-run draft/sign/recall cycle, STP events, leave and expense governance" }
+  - { id: tax-compliance, name: "Tax & Statutory Obligations", focus: "The lodgement calendar, workings assembly, hold-for-signature, SANDBOX SBR/ELSTER rails" }
+  - { id: fpa-planning, name: "FP&A & Capital", focus: "Ledger-current reporting, forecast vs plan, unit economics, fixed-asset lifecycle" }
+
+kpiCategories:
+  - { id: close, name: "Close Discipline", examples: ["Days to close", "Unreconciled bank lines", "Late journals after cutoff"] }
+  - { id: liquidity, name: "Cash & Liquidity", examples: ["Cash runway (months)", "Free cash flow", "Working-capital cycle (CCC)"] }
+  - { id: receivables, name: "Receivables", examples: ["DSO", "Aged >60d AR", "Chase-ladder conversion"] }
+  - { id: payables, name: "Payables", examples: ["DPO", "Bills on hold", "Payment-run exceptions"] }
+  - { id: payroll, name: "Payroll Integrity", examples: ["Pay-run on-time rate", "STP error rate", "Off-cycle corrections"] }
+  - { id: compliance, name: "Statutory Compliance", examples: ["Obligations lodged on time", "Days held-for-signature", "Re-work returns"] }
+  - { id: accuracy, name: "Forecast Accuracy", examples: ["Forecast vs actual variance", "Budget adherence", "Reforecast cadence hit rate"] }
+
+stakeholderSlots:
+  - { id: principal, role: "Reporting principal", typicalRelationship: "Direct report; cash, close, and obligations cadence — and the human signature on money movement" }
+  - { id: commercial, role: "Commercial / Sales leadership", typicalRelationship: "Peer; closed-won → invoice handoff, pricing and collections posture" }
+  - { id: operations, role: "Operations leadership", typicalRelationship: "Peer; vendor terms, expense policy, cost-to-serve" }
+  - { id: people, role: "People / HR leadership", typicalRelationship: "Peer; payroll inputs, leave balances, onboarding cost" }
+  - { id: auditors, role: "External accountants & auditors", typicalRelationship: "External; workings, evidence trails, statutory sign-off" }
+  - { id: authorities, role: "Tax authorities & regulators", typicalRelationship: "External; lodgements and payment obligations on the statutory calendar" }
+
+backlogStreams:
+  - { id: close-cadence, name: "Period Close", intent: "Match the feed, clear holds, post accruals and depreciation, and close the period on time" }
+  - { id: invoice-to-cash, name: "Invoice to Cash", intent: "Draft and send invoices on trigger, run the chase ladder, and convert promises into cash" }
+  - { id: bill-to-pay, name: "Bill to Pay", intent: "Capture bills, resolve holds and disputes, and stage clean payment runs for signature" }
+  - { id: payroll-cycle, name: "Payroll Cycle", intent: "Draft accurate pay runs early, surface anomalies, and hand the signature to the human on time" }
+  - { id: obligation-readiness, name: "Obligation Readiness", intent: "Assemble lodgement workings from the ledger ahead of due dates and hold them for signature" }
+  - { id: cash-visibility, name: "Cash Visibility", intent: "Keep the cash position, runway, and working-capital picture current and grounded" }
+
+cadenceFamily: finance
+toolPacks: [books-core, ledger-reporting, ar-ap-desk, payroll-tax]
+skillPacks: [finance, books-close]
+templatePacks: [finance, close-pack, board-finance]
+
+# Function-default decision rights. The money verbs are deliberately capped at
+# recommends/prepares — the domain layer requires a HUMAN signature on
+# payrollSign / billScheduleRun / taxSignLodge regardless of altitude.
+decisionRights:
+  - { id: close-calendar, scope: "Close calendar, reconciliation standards, and journal hygiene", authority: owns }
+  - { id: chase-posture, scope: "Collections posture, chase-ladder steps, and promise-to-pay handling within policy", authority: owns }
+  - { id: bill-holds, scope: "Bill holds, disputes, and release recommendations within approval floors", authority: owns }
+  - { id: payment-execution, scope: "Payment-run, pay-run, and lodgement EXECUTION (sign & move money)", authority: recommends }
+  - { id: tax-positions, scope: "Tax positions, workings, and lodgement content", authority: recommends }
+  - { id: budget-reallocation, scope: "Budget reallocation and spend-policy changes", authority: recommends }
+
+operatingPrinciples:
+  - "The ledger is the truth — every figure cites its journal lines, never a spreadsheet from memory"
+  - "Prepare everything, sign nothing — money moves only on a verified human signature"
+  - "SIGNATURE_REQUIRED and approval-required frames are the system working; surface them, never route around them"
+  - "Cash is a daily read, not a month-end surprise"
+  - "SANDBOX rails are labelled as such — never report a filing or payment as real when it is not"

package/archetypes/functions/operations-leader.yaml

@@ -0,0 +1,62 @@
+# FUNCTION overlay — operations-leader (COO / Head of Ops / Fund Ops / HR-Ops axis)
+# Contributes WHAT an operations leader owns. Altitude overlays decide HOW (autonomy,
+# decision-rights authority, granularity). Mirrors the technical-leader reference shape.
+# See archetypes/archetype.schema.json.
+
+functionTitle: Operations
+domain: "Process efficiency, core/back-office operations, service quality, capacity, vendors, cost, and operational resilience"
+
+towers:
+  - { id: process-excellence, name: "Process Excellence & Standardisation", focus: "End-to-end process design, standard operating procedures, automation, waste/cycle-time reduction" }
+  - { id: core-operations, name: "Core Operations", focus: "Day-to-day run of the operational engine (fund/back-office/transaction processing); throughput and accuracy" }
+  - { id: service-quality, name: "Service Quality & SLAs", focus: "SLA/OLA attainment, exception management, error/rework rate, customer/internal satisfaction" }
+  - { id: vendor-supplier, name: "Vendor & Supplier Management", focus: "Outsourcer/BPO and supplier performance, contracts, SLAs, concentration and exit risk" }
+  - { id: capacity-resourcing, name: "Capacity & Resource Planning", focus: "Demand-vs-capacity modelling, staffing/shift plans, utilisation, peak/seasonal load" }
+  - { id: people-ops, name: "Organisational Design & People-Ops", focus: "Operating-model design, spans/layers, roles & RACI, onboarding and operational competency" }
+  - { id: cost-management, name: "Cost & Unit Economics", focus: "Operating cost base, cost-per-unit/cost-to-serve, productivity and efficiency programmes" }
+  - { id: resilience-bcp, name: "Operational Resilience & BCP", focus: "Business continuity, disaster recovery, control environment, single points of failure, incident readiness" }
+
+kpiCategories:
+  - { id: service-level, name: "Service Level", examples: ["SLA / OLA attainment", "On-time delivery rate", "Backlog / queue age"] }
+  - { id: quality, name: "Quality & Accuracy", examples: ["Error / exception rate", "Rework rate", "First-pass yield"] }
+  - { id: efficiency, name: "Efficiency & Cycle Time", examples: ["Cycle / turnaround time", "Straight-through-processing rate", "Automation coverage"] }
+  - { id: cost, name: "Cost & Productivity", examples: ["Cost per unit / cost-to-serve", "Operating cost ratio", "Output per FTE"] }
+  - { id: capacity, name: "Capacity & Utilisation", examples: ["Capacity utilisation", "Schedule adherence", "Demand-vs-capacity variance"] }
+  - { id: resilience, name: "Resilience & Continuity", examples: ["Control / SLA breaches", "RTO / RPO attainment", "Incident recovery time"] }
+
+stakeholderSlots:
+  - { id: principal, role: "Reporting principal", typicalRelationship: "Direct report; recurring 1:1" }
+  - { id: ops-leads, role: "Operations team leads / managers", typicalRelationship: "Direct or skip reports" }
+  - { id: finance, role: "Finance & FP&A", typicalRelationship: "Control partner; cost & headcount co-owner" }
+  - { id: risk-compliance, role: "Risk, compliance & internal audit", typicalRelationship: "Control partner; resilience & controls assurance" }
+  - { id: vendors, role: "Outsourcers, BPO & key suppliers", typicalRelationship: "Managed vendor; SLA-governed" }
+  - { id: business-partners, role: "Internal business / front-office partners", typicalRelationship: "Service consumer; demand owner" }
+
+backlogStreams:
+  - { id: process-automation, name: "Process Automation Programme", intent: "Standardise, simplify, and automate core processes; raise STP and cut manual touch" }
+  - { id: operational-excellence, name: "Operational Excellence & SLA Programme", intent: "Lift SLA attainment, accuracy, and cycle time; drive out exceptions and rework" }
+  - { id: vendor-management, name: "Vendor & Supplier Management", intent: "Manage outsourcer/supplier performance, contracts, SLAs, and concentration risk" }
+  - { id: capacity-org-design, name: "Capacity & Org Design", intent: "Right-size capacity to demand; refine the operating model, spans, and roles" }
+  - { id: cost-productivity, name: "Cost & Productivity", intent: "Reduce cost-to-serve and unit cost; capture efficiency and productivity gains" }
+  - { id: resilience-bcp, name: "Resilience & BCP", intent: "Harden continuity, recovery, and the operational control environment" }
+
+cadenceFamily: operations
+toolPacks: [operations-core, process-automation, vendor-mgmt, incident-mgmt]
+skillPacks: [operations]
+templatePacks: [operations, process-design, sla-review]
+
+# Function-default decision rights. Altitude overlays override authority by id and add
+# altitude-specific scopes (strategy, budget, headcount, external commitments).
+decisionRights:
+  - { id: process-design, scope: "Process design, SOPs & operating procedures", authority: owns }
+  - { id: sla-policy, scope: "SLA/OLA targets, service definitions & exception handling", authority: owns }
+  - { id: capacity-planning, scope: "Capacity, staffing & shift planning within approved headcount", authority: owns }
+  - { id: vendor-selection, scope: "Outsourcer & supplier selection and performance management", authority: recommends }
+  - { id: resilience-controls, scope: "Continuity/DR posture & operational control exceptions", authority: recommends }
+
+operatingPrinciples:
+  - "Standardise before you automate"
+  - "Measure the flow, manage the exceptions"
+  - "Make the process resilient, not just efficient"
+  - "Eliminate root causes, not symptoms"
+  - "No surprises: every breach has an owner and a path"

package/archetypes/functions/product-leader.yaml

@@ -0,0 +1,61 @@
+# FUNCTION overlay — product-leader (CPO / VP-Product / Head of Product & UX axis)
+# Contributes WHAT a product leader owns. Altitude overlays decide HOW (autonomy,
+# decision-rights authority, granularity). Mirrors the technical-leader reference
+# shape; pairs as the roadmap co-owner peer. See archetypes/archetype.schema.json.
+
+functionTitle: Product
+domain: "Product strategy, discovery, roadmap, UX/design quality, and product-market fit"
+
+towers:
+  - { id: roadmap-prioritisation, name: "Roadmap & Prioritisation", focus: "Theme-to-now sequencing, ruthless trade-offs, capacity vs. commitment" }
+  - { id: discovery-research, name: "Discovery & User Research", focus: "Continuous discovery, customer interviews, opportunity/solution validation" }
+  - { id: feature-delivery, name: "Feature Delivery", focus: "Spec quality, eng partnership, scope discipline, ship confidence" }
+  - { id: design-ux-quality, name: "Design System & UX Quality", focus: "Design-system coherence, usability, accessibility, end-to-end journey craft" }
+  - { id: pmf-metrics, name: "Product-Market Fit & Metrics", focus: "Activation, retention, the north-star metric, segment fit signal" }
+  - { id: experimentation, name: "Product Analytics & Experimentation", focus: "Instrumentation, A/B rigour, experiment velocity, decision quality" }
+  - { id: cross-functional, name: "Cross-Functional Alignment", focus: "Eng, design, data, and GTM coherence on what ships and why" }
+  - { id: gtm-comms, name: "Launch & GTM Communication", focus: "Launch readiness, positioning input, release notes, stakeholder narrative" }
+
+kpiCategories:
+  - { id: engagement, name: "Engagement & Retention", examples: ["Activation rate", "Retention / churn curve", "DAU/MAU stickiness"] }
+  - { id: adoption, name: "Adoption", examples: ["Feature-adoption rate", "Time-to-value", "Breadth of feature usage"] }
+  - { id: satisfaction, name: "Satisfaction", examples: ["NPS", "CSAT", "Customer effort score"] }
+  - { id: discovery-velocity, name: "Discovery & Experiment Velocity", examples: ["Experiments shipped per cycle", "Win rate of experiments", "Customer interviews per cycle"] }
+  - { id: delivery-predictability, name: "Delivery Predictability", examples: ["Roadmap-commit hit rate", "Outcome-vs-output ratio", "Cycle time idea-to-launch"] }
+
+stakeholderSlots:
+  - { id: principal, role: "Reporting principal", typicalRelationship: "Direct report; recurring 1:1" }
+  - { id: engineering, role: "Engineering leadership", typicalRelationship: "Peer; roadmap co-owner" }
+  - { id: design, role: "Design / UX leadership", typicalRelationship: "Peer; craft & journey co-owner" }
+  - { id: gtm, role: "Sales, marketing & success", typicalRelationship: "Peer; launch & positioning partner" }
+  - { id: customers, role: "Customers & design partners", typicalRelationship: "Discovery & feedback source" }
+  - { id: data-analytics, role: "Data & analytics", typicalRelationship: "Control partner for metrics & experiments" }
+
+backlogStreams:
+  - { id: roadmap-delivery, name: "Roadmap Delivery", intent: "Ship the committed product roadmap against outcomes" }
+  - { id: discovery-research, name: "Discovery & Research", intent: "Continuous discovery; validate problems before solutions" }
+  - { id: pmf-metrics-program, name: "PMF & Metrics Program", intent: "Move the north-star metric; deepen activation & retention" }
+  - { id: design-quality, name: "Design System & UX Quality", intent: "Raise journey craft, accessibility, and design-system coverage" }
+  - { id: launch-readiness, name: "GTM & Launch Readiness", intent: "Land launches: enablement, positioning input, release comms" }
+
+cadenceFamily: product
+toolPacks: [product-core, analytics, user-research]
+skillPacks: [product]
+templatePacks: [product, prd, launch-brief]
+
+# Function-default decision rights. Altitude overlays override authority by id and add
+# altitude-specific scopes (strategy, budget, external commitments, headcount).
+decisionRights:
+  - { id: prioritisation, scope: "Roadmap prioritisation & sequencing within the plan", authority: owns }
+  - { id: product-requirements, scope: "Product requirements, specs & acceptance criteria", authority: owns }
+  - { id: ux-standards, scope: "UX standards, design-system & accessibility bar", authority: owns }
+  - { id: experimentation-policy, scope: "Experiment design, ship/kill thresholds & metric definitions", authority: owns }
+  - { id: launch-gtm, scope: "Launch scope, go/no-go readiness & positioning input", authority: recommends }
+  - { id: pricing-packaging, scope: "Pricing & packaging of product capabilities", authority: recommends }
+
+operatingPrinciples:
+  - "Outcomes over output"
+  - "Talk to users before you build"
+  - "Evidence over the loudest opinion"
+  - "Ruthless prioritisation; say no to protect the yes"
+  - "Ship to learn, instrument everything"