@adaptic/maestro 1.0.0

package/docs/superpowers/specs/2026-04-03-phase2-people-product-commercial-design.md

@@ -0,0 +1,452 @@
+# Phase 2: People + Product + Commercial — Design Spec
+
+**Date**: 2026-04-03
+**Author**: Sophie Nguyen (Chief of Staff)
+**Approved by**: Mehran Granfar (CEO)
+**Status**: Approved
+**Scope**: Control Towers 4-7 — People/Hiring/Org, Culture/Standards/Leadership, Product/Platform/Engineering, Commercial/Customers/Market
+**Depends on**: Phase 0 (complete), Phase 1 (complete)
+
+## Context
+
+Phases 0-1 built the operational runtime and executive core — queues, dashboards, event polling, meeting integration, SLA tracking, drift detection, and self-evolution. Phase 2 adds four domain-specific control towers that extend Sophie's oversight into people, product, and commercial health.
+
+### Current State
+
+- CT4 (People/Hiring): 85% scaffolded — hiring agent, 94-role config, weekly hiring review, daily triage all operational
+- CT5 (Culture/Standards): 0% — no infrastructure exists
+- CT6 (Product/Engineering): 75% scaffolded — engineering-coordination agent, 7-repo registry, but no health dashboard or delivery tracking
+- CT7 (Commercial/Market): 60% scaffolded — competitive-intelligence and market-research agents exist, but no pipeline tracking or commercial metrics
+
+## Architecture
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│                 PHASE 2: DOMAIN TOWERS                       │
+├────────────┬──────────────┬──────────────┬──────────────────┤
+│  CT4:      │  CT5:        │  CT6:        │  CT7:            │
+│  People    │  Leadership  │  Engineering │  Commercial      │
+│  & Hiring  │  & Standards │  & Platform  │  & Market        │
+├────────────┴──────────────┴──────────────┴──────────────────┤
+│  Org Health │ Accountability │ Eng Health │ Relationship     │
+│  Founder    │ Dashboard      │ Tech Debt  │ Pipeline         │
+│  Dependency │ Comm Quality   │ Repo Mon   │ Market Signals   │
+├─────────────────────────────────────────────────────────────┤
+│              PHASE 1: EXECUTIVE CORE                         │
+│  Strategy │ Follow-Through │ Cadence │ Meeting Integration   │
+├─────────────────────────────────────────────────────────────┤
+│              PHASE 0: OPERATIONAL FOUNDATION                 │
+│  Queues │ Dashboards │ Memory │ Polling │ Triggers │ Audit   │
+└─────────────────────────────────────────────────────────────┘
+```
+
+## Control Tower 4: People, Hiring & Organisation
+
+### 4.1 Org Health Monitor
+
+**Purpose**: Track organisational health beyond just hiring pipeline — capability gaps, structural risks, role staleness.
+
+**Location**: `state/dashboards/org-health.yaml`
+
+```yaml
+generated: ISO-8601
+
+hiring_pipeline:
+  total_roles: 94
+  filled: int
+  in_progress: int
+  stale: int # Open >30 days with no pipeline activity
+  critical_unfilled: # Roles tied to P1-P5 priorities
+    - role: string
+      priority: string
+      days_open: int
+
+capability_gaps:
+  - priority: string
+    gap: string # What capability is missing
+    mitigation: string
+
+org_structure:
+  functions_with_leader: int
+  functions_without_leader: int
+  flags: [] # Structural concerns
+
+founder_dependency:
+  mehran_owned_items: int
+  total_open_items: int
+  dependency_percent: float
+  trend: increasing | stable | decreasing
+  threshold_breached: boolean # >60%
+```
+
+**Mechanism**: Enhanced weekly hiring review generates this dashboard. Founder dependency calculated by scanning all queues for items where `owner: mehran`.
+
+### 4.2 Founder Dependency Tracker
+
+**Purpose**: Track and reduce Mehran's centrality to prevent bottleneck and key-person risk.
+
+**Mechanism**: Added to the weekly priorities review:
+
+1. Count queue items across all queues where `owner` contains "mehran"
+2. Calculate `dependency_percent = mehran_items / total_items * 100`
+3. Track weekly trend in `state/dashboards/org-health.yaml`
+4. If >60%, flag in the strategic memo as an org design risk with recommendation to delegate
+5. Identify specific items that could be delegated to leadership team members
+
+### 4.3 Onboarding Tracker
+
+**Purpose**: When new hires are detected (via HR system integration), create structured onboarding milestones.
+
+**Mechanism**: The weekly hiring review checks for newly filled roles. When detected:
+
+1. Create onboarding checklist items in `state/queues/action-stack.yaml` with milestones at 30/60/90 days
+2. Assign hiring manager as owner
+3. Track completion in the org health dashboard
+
+## Control Tower 5: Culture, Standards & Leadership Behaviour
+
+### 5.1 Leadership Accountability Dashboard
+
+**Purpose**: Per-leader metrics tracking commitment follow-through, response times, and accountability trends.
+
+**Location**: `state/dashboards/leadership-accountability.yaml`
+
+```yaml
+generated: ISO-8601
+period: weekly # Rolling 7-day metrics
+
+leaders:
+  mehran-granfar:
+    name: Mehran Granfar
+    role: CEO
+    metrics:
+      commitments_total: int # Queue items where they're owner
+      commitments_met_on_time: int
+      commitments_late: int
+      commitments_missed: int # Still open past SLA
+      avg_response_hours: float # Average time to respond to Sophie's follow-ups
+      chase_count: int # Times Sophie had to chase them this week
+      items_currently_overdue: int
+      sla_breach_count: int
+    trend: improving | stable | declining
+    flags: [] # e.g., "3 consecutive weeks of declining follow-through"
+
+  hootan-yazhari:
+    name: Hootan Yazhari
+    role: CFO / CIO / SEO (DFSA)
+    metrics:
+      commitments_total: int
+      commitments_met_on_time: int
+      commitments_late: int
+      commitments_missed: int
+      avg_response_hours: float
+      chase_count: int
+      items_currently_overdue: int
+      sla_breach_count: int
+    trend: improving | stable | declining
+    flags: []
+
+  bronwyn-leong:
+    name: Bronwyn Leong
+    role: Co-founder / Director
+    metrics:
+      commitments_total: int
+      commitments_met_on_time: int
+      commitments_late: int
+      commitments_missed: int
+      avg_response_hours: float
+      chase_count: int
+      items_currently_overdue: int
+      sla_breach_count: int
+    trend: improving | stable | declining
+    flags: []
+
+  nima-masroori:
+    name: Nima Masroori
+    role: General Counsel
+    metrics:
+      commitments_total: int
+      commitments_met_on_time: int
+      commitments_late: int
+      commitments_missed: int
+      avg_response_hours: float
+      chase_count: int
+      items_currently_overdue: int
+      sla_breach_count: int
+    trend: improving | stable | declining
+    flags: []
+
+  shayan-kargarian:
+    name: Shayan Kargarian
+    role: Managing Partner, FTLab
+    metrics:
+      commitments_total: int
+      commitments_met_on_time: int
+      commitments_late: int
+      commitments_missed: int
+      avg_response_hours: float
+      chase_count: int
+      items_currently_overdue: int
+      sla_breach_count: int
+    trend: improving | stable | declining
+    flags: []
+
+summary:
+  highest_follow_through: string # Leader name
+  lowest_follow_through: string # Leader name
+  most_improved: string
+  concerns: [] # Flagged patterns
+```
+
+**Mechanism**: Evening wrap calculates per-leader metrics by:
+
+1. Scanning all queues for items owned by each leader
+2. Checking item history for: created date, SLA deadline, resolution date, chase events
+3. Calculating metrics
+4. Comparing against last week to determine trend
+5. Flagging concerning patterns (3+ consecutive weeks declining, >50% items overdue)
+
+### 5.2 Weekly Leadership Effectiveness Scorecard
+
+**Purpose**: Candid assessment of leadership follow-through included in the Friday strategic memo.
+
+**Mechanism**: Added to the weekly strategic memo workflow:
+
+1. Read `state/dashboards/leadership-accountability.yaml`
+2. For each leader, summarise: commitments met/missed, response quality, trend
+3. Flag patterns: someone consistently missing deadlines, someone going silent, accountability declining
+4. Include Sophie's candid assessment and specific recommendations
+5. This section is sensitive — marked for Mehran's eyes only (DM, not channel)
+
+### 5.3 Communication Quality Signals
+
+**Purpose**: Enrich the leadership dashboard with qualitative communication signals.
+
+**Mechanism**: The inbox processor, when processing messages from leadership team members, tracks:
+
+- `response_latency`: time between original message and their reply
+- `completeness`: did they address what was asked, or deflect?
+- `follow_through`: did they do what they said they'd do in previous messages?
+
+These signals are stored in `memory/profiles/users/{person}.yaml` under an `accountability` section and feed into the leadership dashboard calculation.
+
+## Control Tower 6: Product, Platform & Engineering Oversight
+
+### 6.1 Engineering Health Dashboard
+
+**Purpose**: Weekly snapshot of delivery health across all source repos.
+
+**Location**: `state/dashboards/engineering-health.yaml`
+
+```yaml
+generated: ISO-8601
+
+repos:
+  adapticai:
+    name: Adaptic Core Platform
+    path: ~/adapticai
+    last_commit: ISO-8601
+    commits_this_week: int
+    activity_status: active | quiet | stale # active >5 commits, quiet 1-5, stale 0
+    open_prs: int
+    oldest_pr_days: int
+    milestone_refs: [P1, P3] # Which priorities this repo serves
+    flags: []
+
+  dfsa-submission:
+    name: DFSA Regulatory Submission
+    path: ~/dfsa-submission
+    last_commit: ISO-8601
+    commits_this_week: int
+    activity_status: active | quiet | stale
+    open_prs: int
+    oldest_pr_days: int
+    milestone_refs: [P1]
+    flags: []
+
+  rollup-strategy:
+    name: Project Aether Rollup
+    path: ~/rollup-strategy
+    last_commit: ISO-8601
+    commits_this_week: int
+    activity_status: active | quiet | stale
+    open_prs: int
+    oldest_pr_days: int
+    milestone_refs: [P2]
+    flags: []
+
+  # Additional repos from config/repo-registry.yaml...
+
+cross_repo:
+  dependency_flags: [] # Known cross-repo dependencies at risk
+  stale_repos: [] # Repos with no commits in >2 weeks
+
+overall:
+  active_repos: int
+  quiet_repos: int
+  stale_repos: int
+  total_open_prs: int
+  delivery_confidence: high | medium | low # Derived from activity + milestone alignment
+```
+
+**Mechanism**: New weekly trigger `weekly-engineering-health.md` runs Wednesday 10:00 GST (before the execution review at 14:00):
+
+1. For each repo in `config/repo-registry.yaml`, check recent git activity
+2. Count commits, open PRs, last commit date
+3. Map repos to strategic priorities
+4. Calculate delivery confidence
+5. Write dashboard
+6. The Wednesday execution review references this dashboard
+
+### 6.2 Tech Debt Register
+
+**Purpose**: Track technical debt items with strategic impact.
+
+**Location**: `state/queues/tech-debt.yaml` (new queue, same schema as other queues)
+
+**Mechanism**: When the execution review or engineering health workflow identifies recurring technical issues:
+
+1. Create tech-debt queue item with `source: engineering-health`
+2. Track: what system is affected, what's the strategic impact, who owns it
+3. Tech debt items appear in the strategy scorecard when they block priority milestones
+
+## Control Tower 7: Commercial, Customers & Market
+
+### 7.1 Relationship Pipeline Tracker
+
+**Purpose**: Track all strategic relationships with stage, warmth, and next actions.
+
+**Location**: `state/dashboards/relationship-pipeline.yaml`
+
+```yaml
+generated: ISO-8601
+
+relationships:
+  investors: []
+  partners:
+    - name: string
+      organisation: string
+      stage: cold | warm | active | engaged | committed
+      last_interaction: ISO-8601
+      next_action: string
+      next_action_due: ISO-8601
+      warmth_trend: warming | stable | cooling
+      owner: string
+      notes: string
+
+  acquisition_targets: []
+  advisors: []
+  regulators: []
+  vendors: []
+
+summary:
+  total_active: int
+  warming: int
+  cooling: int
+  overdue_actions: int
+  relationships_needing_attention: []
+```
+
+**Mechanism**: The weekly strategic memo maintains this pipeline:
+
+1. Review `memory/interactions/` for all external interactions this week
+2. Update relationship stages and warmth based on interaction recency
+3. Flag cooling relationships (no interaction in >2 weeks for active relationships)
+4. Flag overdue next-actions
+5. Include relationship health summary in the strategic memo
+
+### 7.2 Competitive Intelligence Feed
+
+**Purpose**: Structured capture of competitive and market signals.
+
+**Location**: `memory/precedents/market-signals/` (YAML files per signal)
+
+**Signal Schema**:
+
+```yaml
+date: ISO-8601
+source: web | slack | email | meeting | research
+category: competitor | regulation | market | technology | talent
+signal: string
+relevance: high | medium | low
+implication: string
+action_recommended: string
+captured_by: sophie | competitive-intelligence | market-research
+```
+
+**Mechanism**:
+
+- The morning brief includes a web scan for relevant market signals (already uses WebSearch)
+- The inbox processor tags messages containing market/competitive intelligence
+- The weekly strategic memo synthesises weekly signals into the "Emerging Signals" section of `knowledge/syntheses/strategy-state.yaml`
+
+### 7.3 Commercial Health Section
+
+**Purpose**: Weekly commercial position assessment in the strategic memo.
+
+**Mechanism**: Added to the Friday strategic memo:
+
+1. Read `state/dashboards/relationship-pipeline.yaml` for relationship health
+2. Read market signals from `memory/precedents/market-signals/`
+3. Assess: ICP clarity, pipeline warmth, partner engagement, competitive positioning
+4. Include "Commercial Position" section in the memo
+
+## New Files Summary
+
+### New state files
+
+- `state/dashboards/org-health.yaml` — Org structure, hiring, capability gaps, founder dependency
+- `state/dashboards/leadership-accountability.yaml` — Per-leader accountability metrics
+- `state/dashboards/engineering-health.yaml` — Repo activity, PRs, delivery confidence
+- `state/dashboards/relationship-pipeline.yaml` — Strategic relationship tracking
+- `state/queues/tech-debt.yaml` — Technical debt with strategic impact
+
+### New knowledge files
+
+- `memory/precedents/market-signals/.gitkeep` — Market signal directory
+
+### New trigger prompts
+
+- `schedules/triggers/weekly-engineering-health.md` — Wednesday 10:00 GST
+
+### New launchd plists
+
+- `ai.adaptic.sophie-weekly-engineering-health.plist` — Wednesday 10:00 GST
+
+### Modified files
+
+- `schedules/triggers/weekly-hiring.md` — Add org health + founder dependency + onboarding tracking
+- `schedules/triggers/daily-evening-wrap.md` — Add leadership accountability metrics calculation
+- `schedules/triggers/weekly-strategic-memo.md` — Add leadership scorecard + relationship pipeline + commercial health + market signals
+- `schedules/triggers/weekly-execution.md` — Add engineering health reference + tech debt
+- `schedules/triggers/inbox-processor.md` — Add communication quality signal tracking
+- `schedules/triggers/daily-morning-brief.md` — Add org health + engineering health references
+- `memory/profiles/users/*.yaml` — Add accountability section to user profiles
+- `CLAUDE.md` — Add Phase 2 documentation
+
+## Implementation Sequence
+
+1. Create new dashboard files (org-health, leadership-accountability, engineering-health, relationship-pipeline)
+2. Create tech-debt queue and market-signals directory
+3. Create weekly-engineering-health trigger prompt
+4. Add accountability section to all 5 user profiles
+5. Enhance weekly hiring with org health + founder dependency
+6. Enhance evening wrap with leadership accountability metrics
+7. Enhance strategic memo with leadership scorecard + relationship pipeline + commercial health
+8. Enhance execution review with engineering health + tech debt
+9. Enhance inbox processor with communication quality signals
+10. Enhance morning brief with Phase 2 dashboard references
+11. Create launchd plist and install engineering health trigger
+12. Update CLAUDE.md with Phase 2 documentation
+13. Verify all files and triggers
+
+## Success Criteria
+
+- Org health dashboard tracks hiring pipeline + capability gaps + founder dependency
+- Founder dependency metric calculated weekly; flagged when >60%
+- Leadership accountability metrics calculated daily; trends tracked weekly
+- Engineering health dashboard shows per-repo activity and delivery confidence
+- Tech debt items tracked when engineering blockers recur
+- Relationship pipeline tracks all strategic relationships with warmth trends
+- Market signals captured and fed into strategy state
+- Weekly strategic memo includes leadership scorecard, commercial position, and engineering health

package/docs/superpowers/specs/2026-04-03-phase3-4-final-towers-design.md

@@ -0,0 +1,129 @@
+# Phases 3-4: Final Control Towers — Design Spec
+
+**Date**: 2026-04-03
+**Author**: Sophie Nguyen (Chief of Staff)
+**Approved by**: Mehran Granfar (CEO)
+**Status**: Approved
+**Scope**: Phase 3 (CT8-10: Capital/External/Risk) + Phase 4 (CT11-12: Systems/Knowledge)
+**Depends on**: Phases 0-2 (complete)
+
+## Context
+
+Phases 0-2 built: operational runtime (15 queues, dashboards, polling, triggers), executive core (strategy, follow-through, cadence), and domain towers (people, leadership, engineering, commercial). Phases 3-4 complete the remaining 5 control towers to achieve full operational coverage of the charter's 12-tower architecture.
+
+## Phase 3: Capital + External + Risk
+
+### Control Tower 8: Board, Advisors & High-Value Stakeholders
+
+**What exists**: Board-prep agent, investor-relations workflows, relationship-pipeline dashboard (Phase 2).
+
+**What to build:**
+
+1. **Board Calendar Tracker** — Added to the relationship pipeline. Tracks board meeting dates, pack deadlines, and advisor engagement cadence. Monthly board-readiness workflow (already exists) enhanced with pipeline awareness.
+
+2. **Advisor Utilisation Monitor** — Track whether advisors are being leveraged or are just names. The weekly strategic memo notes: advisors contacted this month, value extracted, recommended re-engagement.
+
+### Control Tower 9: Capital, Finance & Corporate Development
+
+**What exists**: Capital-raising agent, corporate-development agent, rollup-execution agent, M&A workflows.
+
+**What to build:**
+
+1. **Capital Readiness Dashboard** (`state/dashboards/capital-readiness.yaml`):
+   - Runway estimate (months)
+   - Fundraising readiness score (materials, narrative, data room)
+   - Investor pipeline (from relationship-pipeline, filtered to investors)
+   - Corp dev target pipeline (from relationship-pipeline, filtered to acquisition targets)
+   - Key milestones: investor deck ready, data room ready, first meetings
+
+2. **Monthly Financial Review Enhancement** — The existing monthly workflow enhanced to populate the capital readiness dashboard with financial signals.
+
+### Control Tower 10: Legal, Risk, Compliance & Regulatory
+
+**What exists**: Regulatory-dfsa agent, legal-ops agent, legal-obligations queue, DFSA-specific workflows.
+
+**What to build:**
+
+1. **Risk Register** (`state/dashboards/risk-register.yaml`):
+   - Enterprise risks tracked with severity, likelihood, owner, mitigation, review date
+   - Seeded from the strategic risks in `knowledge/syntheses/strategy-state.yaml`
+   - Updated monthly by a risk review addition to the strategic memo
+   - Overdue mitigations flagged in morning brief
+
+2. **Regulatory Milestone Tracker** — The strategy scorecard already tracks P1 (DFSA) milestones. This adds a regulatory-specific view that tracks: submission dependencies, evidence pack readiness, policy documentation status, control design progress. Stored as a section in the strategy scorecard.
+
+3. **Compliance Calendar** — Added to `state/queues/legal-obligations.yaml`. The weekly review checks for upcoming compliance deadlines across all jurisdictions and flags in the morning brief.
+
+## Phase 4: Systems + Knowledge
+
+### Control Tower 11: Systems, Automation, Knowledge & Institutional Memory
+
+**What exists**: Knowledge management system, executive memory, decision library, precedents, templates, self-evolution engine.
+
+**What to build:**
+
+1. **Knowledge Health Monitor** — Added to the evening wrap. Checks:
+   - Decision index freshness (last updated)
+   - Strategy state freshness
+   - User profile staleness (last_interaction dates)
+   - Memory index coverage (are there people/topics without index entries?)
+   - Flags knowledge gaps in the morning brief
+
+2. **Automation Opportunity Tracker** — The self-evolution engine (evening wrap) already reflects on learnable patterns. This enhancement explicitly logs automation opportunities to `state/queues/improvement-backlog.yaml` when Sophie notices: repeated manual work, questions she can't answer without manual research, workflows that could be faster.
+
+3. **Process Fragility Scanner** — Added to the weekly execution review. Identifies: single-point-of-failure processes (one person, one system), undocumented critical workflows, handoffs with no tracking.
+
+### Control Tower 12: Sophie's Self-Governance
+
+**What to build:**
+
+1. **Sophie System Health Enhancement** — The existing `state/dashboards/system-health.yaml` enhanced with:
+   - Self-evolution audit: changes made this week, approval status
+   - Knowledge coverage: % of contacts with profiles, % of channels with norms
+   - Trigger reliability: successful vs failed workflow executions
+   - Queue health: items per queue, growth rate, resolution rate
+
+2. **Quarterly Self-Assessment** — A new quarterly trigger where Sophie produces a candid self-assessment: what's working, what's not, where she needs new capabilities, what she'd recommend changing about her own operating model. Sent to Mehran for review.
+
+## New Files
+
+### Phase 3
+
+- `state/dashboards/capital-readiness.yaml` — Runway, fundraising readiness, corp dev pipeline
+- `state/dashboards/risk-register.yaml` — Enterprise risk tracking
+
+### Phase 4
+
+- `schedules/triggers/quarterly-self-assessment.md` — Sophie's quarterly self-review
+
+### Modified Files (Both Phases)
+
+- `schedules/triggers/daily-morning-brief.md` — Add risk register + capital readiness references
+- `schedules/triggers/daily-evening-wrap.md` — Add knowledge health monitor
+- `schedules/triggers/weekly-strategic-memo.md` — Add advisor utilisation + risk review + capital position
+- `schedules/triggers/weekly-execution.md` — Add process fragility scanner
+- `state/dashboards/system-health.yaml` — Enhanced with self-governance metrics
+- `CLAUDE.md` — Add Phase 3-4 documentation
+
+## Implementation Sequence
+
+1. Create capital readiness dashboard and risk register
+2. Create quarterly self-assessment trigger
+3. Enhance morning brief with risk + capital references
+4. Enhance evening wrap with knowledge health monitor
+5. Enhance strategic memo with advisor utilisation + risk review + capital position
+6. Enhance execution review with process fragility scanner
+7. Enhance system-health dashboard schema with self-governance
+8. Update CLAUDE.md with Phases 3-4 documentation
+9. Install quarterly trigger daemon
+10. Verify all files
+
+## Success Criteria
+
+- Capital readiness dashboard tracks runway, fundraising readiness, and pipeline health
+- Enterprise risk register maintained with severity/owner/mitigation
+- Knowledge health flagged when profiles stale or indexes incomplete
+- Automation opportunities captured in improvement backlog
+- Process fragility surfaced in execution reviews
+- Sophie produces quarterly self-assessment
+- All 12 control towers documented in CLAUDE.md