@adaptic/maestro 1.0.0

package/workflows/daily/slack-followup-sweep.yaml

@@ -0,0 +1,87 @@
+# Slack Follow-Up Sweep
+# Runs daily at 12:00 and 17:00 GST
+
+name: slack-followup-sweep
+schedule: "0 12,17 * * *"
+timezone: Asia/Dubai
+description: >
+  Checks all pending Slack follow-ups — messages sent that haven't received
+  a response, commitments made by others that are overdue, and threads
+  that need continuation.
+
+steps:
+  - id: check-awaiting-reply
+    agent: slack-operator
+    action: check-pending-replies
+    description: Check if any messages we sent have received responses
+    timeout: 300
+    inputs:
+      mode: observe
+      queue: awaiting-reply
+      source: knowledge/memory/executive-memory.yaml
+    outputs:
+      file: outputs/followups/daily/{date}/slack-reply-status.md
+
+  - id: check-commitments
+    agent: pmo-execution
+    action: check-slack-commitments
+    description: Check if commitments made in Slack have been fulfilled
+    timeout: 180
+    depends_on: [check-awaiting-reply]
+    inputs:
+      source: knowledge/memory/executive-memory.yaml
+      section: open_loops
+      channel: slack
+    outputs:
+      file: outputs/followups/daily/{date}/slack-commitments-status.md
+
+  - id: draft-followups
+    agent: communications
+    action: draft-followup-messages
+    description: Draft follow-up messages for overdue items
+    timeout: 300
+    depends_on: [check-commitments]
+    inputs:
+      overdue_items: outputs/followups/daily/{date}/slack-commitments-status.md
+      voice: sophie # Follow up in Sophie's voice
+    outputs:
+      file: outputs/followups/daily/{date}/slack-followup-drafts.md
+
+  - id: approval-gate
+    action: approval-check
+    description: Check if follow-up messages are pre-approved category
+    depends_on: [draft-followups]
+    inputs:
+      drafts: outputs/followups/daily/{date}/slack-followup-drafts.md
+      policy: policies/communications-policy.yaml
+    outputs:
+      approved: [] # messages cleared for sending
+      pending_approval: [] # messages needing Mehran's review
+
+  - id: send-approved
+    agent: slack-operator
+    action: send-messages
+    description: Send pre-approved follow-up messages
+    depends_on: [approval-gate]
+    inputs:
+      messages: "{approval-gate.outputs.approved}"
+      mode: execute
+      log: true
+    outputs:
+      file: logs/daily/{date}/slack-sends.log
+
+  - id: queue-pending
+    agent: pmo-execution
+    action: queue-for-approval
+    description: Queue messages requiring approval for next CEO review
+    depends_on: [approval-gate]
+    inputs:
+      messages: "{approval-gate.outputs.pending_approval}"
+    outputs:
+      update: knowledge/memory/executive-memory.yaml
+
+on_failure:
+  action: log-and-notify
+  message: "Slack follow-up sweep failed at step {failed_step}"
+  notify: sophie-chief-of-staff
+  severity: medium

package/workflows/event-driven/README.md

@@ -0,0 +1,50 @@
+# Event-Driven Workflows
+
+These workflows trigger in response to events rather than on a schedule.
+
+## Planned Event Triggers
+
+### High-Priority Inbound Message
+
+- **Trigger**: Message from CEO, investor, or board member detected during monitoring
+- **Action**: Immediately surface to Sophie, classify urgency, prepare response options
+- **Agent**: slack-operator or gmail-operator → sophie-chief-of-staff
+
+### Regulatory Development
+
+- **Trigger**: DFSA announcement, regulatory change, or compliance alert
+- **Action**: Assess impact on Adaptic, update regulatory tracker, brief CEO if material
+- **Agent**: regulatory-dfsa → sophie-chief-of-staff
+
+### Pipeline Target Event
+
+- **Trigger**: News about an acquisition target (AUM change, personnel change, regulatory action)
+- **Action**: Update target profile, assess impact on pipeline, brief corporate-development
+- **Agent**: competitive-intelligence → corporate-development
+
+### Engineering Incident
+
+- **Trigger**: Build failure, test regression, or production alert in adapticai repo
+- **Action**: Assess severity, route to engineering-coordination, brief if material
+- **Agent**: engineering-coordination → sophie-chief-of-staff
+
+### Calendar Event Approaching
+
+- **Trigger**: 30 minutes before a scheduled meeting
+- **Action**: Prepare meeting brief with relevant context, open loops, and talking points
+- **Agent**: calendar-ops → ceo-briefing
+
+### Decision Deadline
+
+- **Trigger**: Decision deadline approaching (from decision-log)
+- **Action**: Surface decision with options, remind of deadline, escalate if needed
+- **Agent**: decision-log → sophie-chief-of-staff
+
+## Implementation
+
+Event-driven workflows will be implemented via:
+
+1. **Polling monitors** — Lightweight agents that check for events at high frequency
+2. **File watchers** — `fswatch` monitoring for changes to key files
+3. **Webhook receivers** — HTTP endpoints for external event sources (future)
+4. **MCP event streams** — Real-time event ingestion via MCP servers (future)

package/workflows/monthly/board-readiness.yaml

@@ -0,0 +1,76 @@
+# Monthly Board Readiness Review
+# Runs first Monday of each month at 09:00 GST
+
+name: board-readiness-review
+schedule: "0 9 1-7 * 1" # First Monday of month
+timezone: Asia/Dubai
+description: >
+  Monthly assessment of board readiness — what materials exist, what gaps remain,
+  what updates are needed for the next board meeting.
+
+steps:
+  - id: board-materials-audit
+    agent: board-prep
+    action: materials-inventory
+    description: Inventory existing board materials and identify gaps
+    timeout: 300
+
+  - id: financial-summary
+    agent: fund-ops
+    action: monthly-financial-summary
+    description: Monthly financial position and runway summary
+    timeout: 300
+    parallel_with: board-materials-audit
+
+  - id: strategic-progress
+    agent: strategic-planning
+    action: monthly-strategy-progress
+    description: Progress against strategic plan milestones
+    timeout: 300
+    parallel_with: board-materials-audit
+
+  - id: risk-refresh
+    agent: risk-register
+    action: monthly-risk-refresh
+    description: Updated risk register with new risks and changed scores
+    timeout: 300
+    parallel_with: board-materials-audit
+
+  - id: regulatory-status
+    agent: regulatory-dfsa
+    action: monthly-regulatory-summary
+    description: Regulatory application status and compliance posture
+    timeout: 180
+    parallel_with: board-materials-audit
+
+  - id: pipeline-summary
+    agent: corporate-development
+    action: monthly-pipeline-summary
+    description: M&A pipeline status for board reporting
+    timeout: 180
+    parallel_with: board-materials-audit
+
+  - id: produce-readiness-report
+    agent: board-prep
+    action: produce-readiness-assessment
+    description: Produce the board readiness assessment
+    timeout: 300
+    depends_on:
+      [
+        board-materials-audit,
+        financial-summary,
+        strategic-progress,
+        risk-refresh,
+        regulatory-status,
+        pipeline-summary,
+      ]
+    outputs:
+      file: outputs/board/monthly/{date}/board-readiness-review.md
+
+on_failure:
+  action: log-and-notify
+  message: "Board readiness review failed at step {failed_step}"
+  notify: sophie-chief-of-staff
+  severity: medium
+
+final_output: outputs/board/monthly/{date}/board-readiness-review.md

package/workflows/quarterly/strategic-scenario-analysis.yaml

@@ -0,0 +1,85 @@
+# Quarterly Strategic Scenario Analysis
+# Runs first week of each quarter
+
+name: strategic-scenario-analysis
+schedule: "0 9 1-7 1,4,7,10 1" # First Monday of Jan, Apr, Jul, Oct
+timezone: Asia/Dubai
+description: >
+  Comprehensive quarterly scenario analysis covering base case, upside,
+  downside, and severe downside scenarios for Adaptic.ai.
+
+steps:
+  - id: market-environment
+    agent: market-research
+    action: quarterly-market-assessment
+    description: Assess macro environment, market conditions, sector trends
+    timeout: 600
+
+  - id: competitive-landscape
+    agent: competitive-intelligence
+    action: quarterly-competitive-deep-dive
+    description: Deep competitive analysis including new entrants and positioning shifts
+    timeout: 600
+    parallel_with: market-environment
+
+  - id: regulatory-landscape
+    agent: regulatory-dfsa
+    action: quarterly-regulatory-outlook
+    description: Regulatory developments and outlook across jurisdictions
+    timeout: 300
+    parallel_with: market-environment
+
+  - id: pipeline-assessment
+    agent: corporate-development
+    action: quarterly-pipeline-assessment
+    description: Rollup pipeline health and execution trajectory
+    timeout: 300
+    parallel_with: market-environment
+
+  - id: platform-maturity
+    agent: product-strategy
+    action: quarterly-platform-review
+    description: Platform maturity, feature completeness, technical readiness
+    timeout: 300
+    parallel_with: market-environment
+
+  - id: scenario-construction
+    agent: strategic-planning
+    action: construct-scenarios
+    description: Build scenarios from all inputs
+    timeout: 600
+    depends_on:
+      [
+        market-environment,
+        competitive-landscape,
+        regulatory-landscape,
+        pipeline-assessment,
+        platform-maturity,
+      ]
+    inputs:
+      scenarios:
+        - name: base_case
+          probability: 0.35
+        - name: upside
+          probability: 0.10
+        - name: downside
+          probability: 0.35
+        - name: severe_downside
+          probability: 0.20
+
+  - id: recommendation-synthesis
+    agent: strategic-planning
+    action: produce-scenario-analysis
+    description: Synthesise into quarterly scenario analysis with recommendations
+    timeout: 600
+    depends_on: [scenario-construction]
+    outputs:
+      file: outputs/memos/quarterly/{date}/strategic-scenario-analysis.md
+
+on_failure:
+  action: log-and-notify
+  message: "Quarterly scenario analysis failed at step {failed_step}"
+  notify: sophie-chief-of-staff
+  severity: medium
+
+final_output: outputs/memos/quarterly/{date}/strategic-scenario-analysis.md

package/workflows/session-protocol.md

@@ -0,0 +1,171 @@
+# Session Protocol
+
+Sophie's session lifecycle defines what happens at the start, during, and end of every Claude Code session. This protocol ensures Sophie never misses a message — even while deep in complex tasks.
+
+## Architecture
+
+Two complementary polling layers run simultaneously:
+
+| Layer                    | Mechanism                                               | Interval   | Scope                                                                                                 |
+| ------------------------ | ------------------------------------------------------- | ---------- | ----------------------------------------------------------------------------------------------------- |
+| **External poller**      | `scripts/poller/index.mjs` via macOS launchd            | 60 seconds | All Slack channels, Gmail, Calendar — runs continuously whether or not a session is active            |
+| **Intra-session poller** | `scripts/poller/intra-session-check.mjs` via CronCreate | 2 minutes  | CEO DM channel (D099N1JGKRQ), critical channels (#ceo-office, #engineering, #all-adaptic), inbox scan |
+
+Combined worst-case latency for detecting a CEO message: ~90 seconds.
+
+## Session Start
+
+**Script:** `scripts/session-start.sh`
+
+Every new Claude Code session begins with this sequence:
+
+### 1. Emergency stop check
+
+- If `.emergency-stop` exists, halt immediately
+
+### 2. Read executive summary dashboard
+
+- Load `state/dashboards/executive-summary.yaml`
+- Surface key metrics: open items, critical items, SLA breaches, resolved today
+
+### 3. Check unprocessed inbox
+
+- Scan `state/inbox/{slack,gmail,calendar,sms,internal}/` for `.yaml` files
+- Report count of unprocessed items
+
+### 4. Check pending decisions
+
+- Read `state/queues/decision-queue.yaml` for items with `status: open`
+
+### 5. Check priority triggers
+
+- Scan `state/triggers/priority/` for pending trigger files
+- If triggers exist, process them before any other work
+
+### 6. Set up intra-session polling (CronCreate)
+
+- Create a 2-minute recurring job using CronCreate
+- The job runs `scripts/poller/intra-session-check.mjs`
+- This is the critical step that prevents Sophie from going dark during long tasks
+
+### 7. Log session start
+
+- Write session start event to `logs/sessions/{date}-sessions.jsonl`
+
+## During Session: Intra-Session Polling
+
+Every 2 minutes, the CronCreate job runs the intra-session check:
+
+### What it checks
+
+1. **CEO DM channel** (D099N1JGKRQ) — last 5 minutes of messages from Mehran
+2. **Critical Slack channels** — #ceo-office, #engineering, #all-adaptic — last 3 minutes
+3. **Inbox directories** — count of unprocessed items across all services
+4. **Existing triggers** — count of pending priority triggers
+
+### Priority trigger creation
+
+A priority trigger file is created at `state/triggers/priority/` when:
+
+- A CEO message is found in the DM channel
+- A CEO message is found in a critical channel
+- An urgent-tagged message is found (contains "urgent", "emergency", "asap", "blocker", "critical")
+
+### Trigger file format
+
+```yaml
+type: priority_trigger
+reason: "CEO DM detected during intra-session poll"
+source: "slack:D099N1JGKRQ:1775164334.094809"
+sender: "mehran-granfar"
+channel: "dm/mehran-granfar"
+timestamp: "2026-04-03T09:10:00Z"
+detected_by: intra-session-check
+content: |
+  Message content here
+```
+
+### How priority triggers work
+
+1. Intra-session check detects a CEO message
+2. Writes a trigger file to `state/triggers/priority/`
+3. Exits with code 2 (signals priority to the CronCreate handler)
+4. Claude Code session should **interrupt current work** and process the trigger
+5. After processing, the trigger file is moved to `state/triggers/processed/` or deleted
+
+### Output format
+
+The check logs to stdout for the Claude Code session:
+
+```
+[inbox-poll] CEO DM: 1 new message(s) — PRIORITY TRIGGER CREATED | Channels: #engineering(2) | Inbox: 3 unprocessed
+```
+
+If nothing is found:
+
+```
+[inbox-poll] 09:12:00 — Clear
+```
+
+## Session End
+
+Every Claude Code session ends with this sequence:
+
+### 1. Update modified queues
+
+- Write back any queue items that were modified during the session
+- Ensure all status changes are persisted
+
+### 2. Regenerate executive summary dashboard
+
+- Update `state/dashboards/executive-summary.yaml` with current queue counts
+- Refresh key metrics (open items, critical items, SLA breaches)
+
+### 3. Self-evolution reflection
+
+- Note any automation opportunities discovered during the session
+- Log improvement candidates to `state/queues/improvement-backlog.yaml`
+
+### 4. Commit changes
+
+- Stage and commit all modified state files, logs, and outputs
+- Commit message follows the established format
+
+### 5. Log session end
+
+- Write session end event to `logs/sessions/{date}-sessions.jsonl`
+- Include session duration, items processed, actions taken
+
+## CronCreate Setup (Copy-Paste)
+
+At the start of every session, after running `scripts/session-start.sh`, execute this CronCreate:
+
+```
+CronCreate:
+  interval: "2m"
+  command: "Run intra-session inbox check"
+  instructions: |
+    1. Run: node scripts/poller/intra-session-check.mjs
+    2. Check state/inbox/ for new unprocessed items
+    3. Check state/triggers/priority/ for new trigger files
+    4. If a CEO message (from_ceo: true) is found:
+       - Create a priority trigger at state/triggers/priority/
+       - Interrupt current work to process the CEO message
+    5. Report: "[inbox-poll] N new items, M priority triggers"
+```
+
+## File Reference
+
+| File                                      | Purpose                                                          |
+| ----------------------------------------- | ---------------------------------------------------------------- |
+| `scripts/session-start.sh`                | Session start script — run at beginning of every session         |
+| `scripts/poller/intra-session-check.mjs`  | Intra-session inbox check — called by CronCreate every 2 minutes |
+| `scripts/poller/index.mjs`                | External 60s poller — runs via launchd continuously              |
+| `scripts/poller/slack-poller.mjs`         | Full Slack polling logic (channels + DMs)                        |
+| `scripts/poller/trigger.mjs`              | Priority trigger writer (used by external poller)                |
+| `state/triggers/priority/`                | Priority trigger files — checked by intra-session poll           |
+| `state/inbox/`                            | Inbox items — written by pollers, consumed by inbox processor    |
+| `state/dashboards/executive-summary.yaml` | Primary situational awareness dashboard                          |
+| `state/queues/decision-queue.yaml`        | Pending decisions requiring attention                            |
+| `logs/sessions/`                          | Session lifecycle logs                                           |
+| `logs/polling/`                           | Polling event logs                                               |

package/workflows/weekly/hiring-review.yaml

@@ -0,0 +1,169 @@
+# Weekly Hiring Review
+# Runs every Monday at 11:00 GST (UTC+4)
+# Covers all 94 roles across 13 locations
+
+name: hiring-review
+schedule: "0 11 * * 1" # Monday 11:00
+timezone: Asia/Dubai
+description: >
+  Weekly review of the full hiring pipeline across 94 open roles and 13 locations.
+  Scans applicant pipeline, reviews new applications, AI screens candidates,
+  drafts responses, and produces a consolidated hiring status report.
+
+steps:
+  - id: pipeline-snapshot
+    agent: hiring-org-design
+    action: pipeline-status-scan
+    description: Scan the full hiring pipeline across all 94 roles and 13 locations
+    timeout: 600
+    inputs:
+      source: ~/hr-system
+      config: config/hiring.yaml
+      scope: all_roles
+    outputs:
+      file: outputs/briefs/weekly/{date}/hiring-pipeline-snapshot.md
+
+  - id: new-applications-review
+    agent: hiring-org-design
+    action: review-weekly-applications
+    description: Review all new applications received in the past week
+    timeout: 600
+    parallel_with: pipeline-snapshot
+    inputs:
+      sources:
+        - channel: linkedin
+          path: ~/hr-system/applications/linkedin/
+        - channel: website
+          path: ~/hr-system/applications/website/
+        - channel: email
+          path: ~/hr-system/applications/email/
+      period: last_7_days
+    outputs:
+      file: outputs/briefs/weekly/{date}/weekly-applications-review.md
+
+  - id: ai-screening
+    agent: hiring-org-design
+    action: ai-screen-candidates
+    description: Run AI screening on all unscreened candidates from the past week
+    timeout: 900
+    depends_on: [new-applications-review]
+    inputs:
+      candidates: outputs/briefs/weekly/{date}/weekly-applications-review.md
+      screening_config:
+        advance_threshold: 75
+        reject_threshold: 40
+    outputs:
+      file: outputs/briefs/weekly/{date}/screening-results.md
+
+  - id: draft-advance-responses
+    agent: hiring-org-design
+    action: draft-suitable-candidate-responses
+    description: Draft warm, personalised responses for candidates scoring >= 75
+    timeout: 600
+    depends_on: [ai-screening]
+    inputs:
+      screening_results: outputs/briefs/weekly/{date}/screening-results.md
+      category: advance
+      tone: warm_professional
+      voice: sophie
+    outputs:
+      file: outputs/comms/hiring/{date}/advance-drafts.md
+
+  - id: draft-rejection-responses
+    agent: hiring-org-design
+    action: draft-rejection-responses
+    description: Draft gentle, encouraging rejection messages for candidates scoring < 40
+    timeout: 600
+    parallel_with: draft-advance-responses
+    depends_on: [ai-screening]
+    inputs:
+      screening_results: outputs/briefs/weekly/{date}/screening-results.md
+      category: reject
+      tone: kind_encouraging
+      voice: sophie
+    outputs:
+      file: outputs/comms/hiring/{date}/rejection-drafts.md
+
+  - id: draft-hold-responses
+    agent: hiring-org-design
+    action: draft-hold-responses
+    description: Draft hold-for-review messages for candidates scoring 40-74
+    timeout: 300
+    parallel_with: draft-advance-responses
+    depends_on: [ai-screening]
+    inputs:
+      screening_results: outputs/briefs/weekly/{date}/screening-results.md
+      category: hold
+      tone: professional
+      voice: sophie
+    outputs:
+      file: outputs/comms/hiring/{date}/hold-drafts.md
+
+  - id: location-breakdown
+    agent: hiring-org-design
+    action: location-hiring-status
+    description: Produce hiring status breakdown by location
+    timeout: 300
+    depends_on: [pipeline-snapshot]
+    inputs:
+      locations:
+        - Dubai
+        - San Francisco
+        - London
+        - New York City
+        - Singapore
+        - Cayman Islands
+        - Luxembourg
+        - Sydney
+        - Zurich
+        - Toronto
+        - Tel Aviv
+        - Hong Kong
+        - Washington DC
+    outputs:
+      file: outputs/briefs/weekly/{date}/hiring-by-location.md
+
+  - id: synthesise-hiring-report
+    agent: hiring-org-design
+    action: produce-weekly-hiring-report
+    description: Synthesise all inputs into the weekly hiring status report
+    timeout: 600
+    depends_on:
+      [
+        pipeline-snapshot,
+        ai-screening,
+        draft-advance-responses,
+        draft-rejection-responses,
+        draft-hold-responses,
+        location-breakdown,
+      ]
+    inputs:
+      components:
+        - outputs/briefs/weekly/{date}/hiring-pipeline-snapshot.md
+        - outputs/briefs/weekly/{date}/weekly-applications-review.md
+        - outputs/briefs/weekly/{date}/screening-results.md
+        - outputs/comms/hiring/{date}/advance-drafts.md
+        - outputs/comms/hiring/{date}/rejection-drafts.md
+        - outputs/comms/hiring/{date}/hold-drafts.md
+        - outputs/briefs/weekly/{date}/hiring-by-location.md
+      config: config/hiring.yaml
+    outputs:
+      file: outputs/briefs/weekly/{date}/hiring-status.md
+
+  - id: notify-ready
+    action: notify
+    description: Signal that the weekly hiring report and correspondence drafts are ready
+    depends_on: [synthesise-hiring-report]
+    inputs:
+      channel: slack
+      target: "#ceo-office"
+      message: "Weekly Hiring Review ready: outputs/briefs/weekly/{date}/hiring-status.md — candidate correspondence drafts queued for approval."
+      approval_required: false
+
+on_failure:
+  action: log-and-notify
+  message: "Weekly hiring review failed at step {failed_step}"
+  notify: sophie-chief-of-staff
+  severity: high
+
+final_output: outputs/briefs/weekly/{date}/hiring-status.md