@cohortapp/agent-sdk 2.3.0

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 the company.
+
+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: agent-self # the executing agent (operator)
+  severity: medium
+
+final_output: outputs/memos/quarterly/{date}/strategic-scenario-analysis.md

package/workflows/session-protocol.md

@@ -0,0 +1,171 @@
+# Session Protocol
+
+The agent's session lifecycle defines what happens at the start, during, and end of every Claude Code session. This protocol ensures the agent 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 (<principal-dm-channel-id>), 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 the agent 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** (<principal-dm-channel-id>) — last 5 minutes of messages from the principal (CEO)
+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:<principal-dm-channel-id>:1775164334.094809"
+sender: "<principal-slug>" # resolved from config/agent.json
+channel: "dm/<principal-slug>" # resolved from config/agent.json
+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/engineering-health.yaml

@@ -0,0 +1,154 @@
+# Weekly Engineering Health Check
+# Runs every Wednesday at 10:00 GST — before the weekly execution review
+# Uses ccxray and code-review-graph for data-driven engineering insights
+
+name: engineering-health
+schedule: "0 10 * * 3" # Wednesday 10:00
+timezone: Asia/Dubai
+description: >
+  Weekly engineering health assessment. Audits token spend across agent sessions,
+  scans codebase architecture for structural drift, and produces an engineering
+  health dashboard update. Feeds into the weekly strategic memo.
+
+steps:
+  # ── Token budget audit via ccxray ──
+  - id: token-budget-audit
+    skill: ccxray-diagnostics
+    action: weekly-token-audit
+    description: >
+      Analyse the past week's Claude API token consumption across all agent
+      sessions. Identify expensive sessions, cost trends, and optimisation
+      opportunities. Uses ccxray historical logs.
+    timeout: 300
+    inputs:
+      time_range: 7d
+      log_dir: ~/.ccxray/logs/
+      breakdown_by: [agent, workflow, day]
+      compare_to: previous_week
+    outputs:
+      file: outputs/engineering/weekly/{date}/token-audit.md
+      summary:
+        total_tokens: 0
+        total_cost: 0
+        most_expensive_agent: ""
+        week_over_week_delta: ""
+        optimisation_recommendations: []
+
+  # ── Codebase architecture scan via code-review-graph ──
+  - id: architecture-scan
+    skill: code-review-graph
+    action: architecture-overview
+    description: >
+      Run tree-sitter structural analysis across key repositories. Detect
+      circular dependencies, orphaned exports, and architectural drift from
+      the intended design. Compares against previous week's baseline.
+    timeout: 600
+    parallel_with: token-budget-audit
+    inputs:
+      repos:
+        - path: ~/adapticai/engine
+          name: adaptic-engine
+        - path: ~/adapticai/backend
+          name: adaptic-backend
+        - path: ~/maestro
+          name: maestro
+      checks:
+        - circular_dependencies
+        - orphaned_exports
+        - module_coupling_score
+        - public_api_surface_changes
+      baseline: outputs/engineering/weekly/latest/architecture-baseline.json
+    outputs:
+      file: outputs/engineering/weekly/{date}/architecture-scan.md
+      baseline_update: outputs/engineering/weekly/{date}/architecture-baseline.json
+      summary:
+        repos_scanned: 0
+        circular_deps_found: 0
+        orphaned_exports: 0
+        api_surface_changes: []
+
+  # ── Agent performance profile via agents-observe ──
+  - id: agent-performance-review
+    skill: agents-observe
+    action: weekly-performance-profile
+    description: >
+      Review agent execution patterns from the past week. Identify slowest
+      agents, most-used tools, failure patterns, and efficiency trends.
+      Uses agents-observe SQLite historical data.
+    timeout: 300
+    parallel_with: token-budget-audit
+    inputs:
+      time_range: 7d
+      metrics:
+        - agent_duration_distribution
+        - tool_call_frequency
+        - failure_rate_by_agent
+        - bottleneck_tools
+      compare_to: previous_week
+    outputs:
+      file: outputs/engineering/weekly/{date}/agent-performance.md
+      summary:
+        total_sessions: 0
+        avg_session_duration: ""
+        failure_rate: ""
+        slowest_agent: ""
+        most_used_tool: ""
+
+  # ── Quota trend analysis via claude-pace ──
+  - id: quota-trend
+    skill: claude-pace
+    action: weekly-quota-trend
+    description: >
+      Analyse quota utilisation patterns over the past week. Identify peak
+      usage periods, quota constraint frequency, and capacity planning
+      recommendations.
+    timeout: 120
+    parallel_with: token-budget-audit
+    inputs:
+      source: logs/workflows/ # Extract quota data from backlog executor logs
+      time_range: 7d
+      metrics:
+        - daily_peak_usage
+        - red_zone_incidents
+        - deferred_items_count
+    outputs:
+      file: outputs/engineering/weekly/{date}/quota-trend.md
+
+  # ── Synthesise engineering health report ──
+  - id: synthesise-health-report
+    agent: engineering-oversight
+    action: produce-engineering-health-report
+    description: >
+      Synthesise token audit, architecture scan, agent performance, and quota
+      trends into a unified engineering health dashboard update and narrative.
+    timeout: 300
+    depends_on:
+      [token-budget-audit, architecture-scan, agent-performance-review, quota-trend]
+    inputs:
+      components:
+        - outputs/engineering/weekly/{date}/token-audit.md
+        - outputs/engineering/weekly/{date}/architecture-scan.md
+        - outputs/engineering/weekly/{date}/agent-performance.md
+        - outputs/engineering/weekly/{date}/quota-trend.md
+      dashboard: state/dashboards/engineering-health.yaml
+    outputs:
+      file: outputs/engineering/weekly/{date}/engineering-health-report.md
+      dashboard_update: state/dashboards/engineering-health.yaml
+
+  # ── Notify ──
+  - id: notify-ready
+    action: notify
+    description: Signal engineering health report is ready for the execution review
+    depends_on: [synthesise-health-report]
+    inputs:
+      channel: slack
+      target: "#engineering"
+      message: "Weekly engineering health report ready — feeding into execution review."
+
+on_failure:
+  action: log-and-notify
+  message: "Engineering health check failed at step {failed_step}"
+  notify: agent-self # the executing agent (operator)
+  severity: medium
+
+final_output: outputs/engineering/weekly/{date}/engineering-health-report.md

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: agent
+    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: agent
+    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: agent
+    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: agent-self # the executing agent (operator)
+  severity: high
+
+final_output: outputs/briefs/weekly/{date}/hiring-status.md

package/workflows/weekly/rollup-pipeline-review.yaml

@@ -0,0 +1,76 @@
+# Weekly Rollup Pipeline Review
+# Runs every Wednesday at 10:00 GST
+
+name: rollup-pipeline-review
+schedule: "0 10 * * 3" # Wednesday 10:00
+timezone: Asia/Dubai
+description: >
+  Reviews the status of all rollup acquisition targets in the pipeline,
+  tracks movement between stages, and identifies next actions.
+
+steps:
+  - id: pipeline-status
+    agent: rollup-target-sourcing
+    action: pipeline-snapshot
+    description: Current state of all targets across pipeline stages
+    timeout: 300
+    inputs:
+      source: knowledge/entities/entity-map.yaml
+      pipeline: knowledge/memory/executive-memory.yaml
+    outputs:
+      file: outputs/briefs/weekly/{date}/pipeline-snapshot.md
+
+  - id: dd-progress
+    agent: corporate-development
+    action: dd-progress-report
+    description: Progress on active due diligence processes
+    timeout: 300
+    parallel_with: pipeline-status
+    outputs:
+      file: outputs/briefs/weekly/{date}/dd-progress.md
+
+  - id: market-scan-targets
+    agent: rollup-target-sourcing
+    action: new-target-scan
+    description: Scan for new potential acquisition targets
+    timeout: 300
+    parallel_with: pipeline-status
+    inputs:
+      criteria:
+        aum_range: [500000000, 10000000000]
+        strategies: [equity-ls, global-macro, quant, multi-strat]
+        trigger_events: [succession, aum-decline, margin-compression]
+    outputs:
+      file: outputs/briefs/weekly/{date}/new-targets.md
+
+  - id: regulatory-filing-status
+    agent: legal-structuring
+    action: filing-timeline-check
+    description: Status of regulatory filings related to active deals
+    timeout: 180
+    parallel_with: pipeline-status
+    outputs:
+      file: outputs/briefs/weekly/{date}/filing-status.md
+
+  - id: synthesise-review
+    agent: corporate-development
+    action: produce-pipeline-review
+    description: Produce the weekly pipeline review document
+    timeout: 300
+    depends_on:
+      [
+        pipeline-status,
+        dd-progress,
+        market-scan-targets,
+        regulatory-filing-status,
+      ]
+    outputs:
+      file: outputs/briefs/weekly/{date}/rollup-pipeline-review.md
+
+on_failure:
+  action: log-and-notify
+  message: "Rollup pipeline review failed at step {failed_step}"
+  notify: agent-self # the executing agent (operator)
+  severity: medium
+
+final_output: outputs/briefs/weekly/{date}/rollup-pipeline-review.md