@cohortapp/agent-sdk 2.3.0

package/workflows/daily/morning-brief.yaml

@@ -0,0 +1,164 @@
+# Morning CEO Brief Workflow
+# Runs daily at 06:00 GST (UTC+4) on the Mac mini
+# Produces the CEO Morning Brief by 06:30
+
+name: morning-brief
+schedule: "0 6 * * *" # 06:00 daily
+timezone: Asia/Dubai
+description: >
+  Produces the daily CEO Morning Brief — a concise executive summary covering
+  overnight developments, today's priorities, decisions needed, and open loops.
+
+# Workflow steps execute sequentially
+steps:
+  # ── System health gate — check API quota before the day's workload ──
+  - id: quota-status
+    skill: claude-pace
+    action: morning-quota-check
+    description: >
+      Check overnight quota consumption and current headroom. Reports pace
+      delta zone so the morning brief can flag capacity constraints early.
+    timeout: 30
+    outputs:
+      pace_delta: green|yellow|red
+      five_hour_pct: 0
+      seven_day_pct: 0
+      capacity_note: "" # included in the morning brief if yellow/red
+
+  - id: market-sweep
+    agent: market-research
+    action: overnight-market-summary
+    description: Gather overnight market movements, key indices, relevant asset class performance
+    timeout: 300 # 5 minutes
+    parallel_with: quota-status
+    inputs:
+      scope: [equities, crypto, forex, fixed-income]
+      regions: [us, emea, apac]
+      focus_assets: [] # populated from config/watchlist.yaml
+    outputs:
+      file: outputs/briefs/daily/{date}/market-sweep.md
+
+  - id: news-intelligence
+    agent: competitive-intelligence
+    action: overnight-news-scan
+    description: Scan for overnight news relevant to the company, competitors, regulatory developments
+    timeout: 300
+    parallel_with: market-sweep
+    inputs:
+      topics:
+        - adaptic.ai
+        - ai asset management
+        - dfsa regulation
+        - hedge fund acquisitions
+        - algorithmic trading regulation
+        - competitors # from config/competitors.yaml
+    outputs:
+      file: outputs/briefs/daily/{date}/news-intelligence.md
+
+  - id: comms-triage
+    agent: gmail-operator
+    action: overnight-inbox-scan
+    description: Identify overnight emails requiring attention
+    timeout: 300
+    parallel_with: market-sweep
+    inputs:
+      account: "{{agent.email}}" # resolved from config/agent.json at workflow execution
+      mode: observe # read-only, never act
+      priority_senders: [] # from config/contacts.yaml
+    outputs:
+      file: outputs/briefs/daily/{date}/email-triage.md
+
+  - id: slack-triage
+    agent: slack-operator
+    action: overnight-channel-scan
+    description: Identify overnight Slack activity requiring attention
+    timeout: 300
+    parallel_with: market-sweep
+    inputs:
+      mode: observe
+      priority_channels: [] # from config/slack-channels.yaml
+    outputs:
+      file: outputs/briefs/daily/{date}/slack-triage.md
+
+  - id: open-loops-review
+    agent: pmo-execution
+    action: open-loops-status
+    description: Check status of all open execution queue items
+    timeout: 120
+    inputs:
+      queues: [awaiting-reply, delegated, blocked, scheduled-followup]
+    outputs:
+      file: outputs/briefs/daily/{date}/open-loops.md
+
+  - id: workstream-pulse
+    agent: pmo-execution
+    action: workstream-status-check
+    description: One-line status from each active workstream
+    timeout: 120
+    depends_on: [open-loops-review]
+    inputs:
+      source: knowledge/memory/executive-memory.yaml
+      section: active_initiatives
+    outputs:
+      file: outputs/briefs/daily/{date}/workstream-pulse.md
+
+  - id: calendar-review
+    agent: calendar-ops
+    action: today-schedule
+    description: Pull today's calendar and flag preparation needs
+    timeout: 120
+    parallel_with: workstream-pulse
+    inputs:
+      mode: observe
+    outputs:
+      file: outputs/briefs/daily/{date}/calendar.md
+
+  - id: synthesise-brief
+    agent: ceo-briefing
+    action: produce-morning-brief
+    description: Synthesise all inputs into the CEO Morning Brief
+    timeout: 300
+    depends_on:
+      [
+        quota-status,
+        market-sweep,
+        news-intelligence,
+        comms-triage,
+        slack-triage,
+        open-loops-review,
+        workstream-pulse,
+        calendar-review,
+      ]
+    inputs:
+      quota_status: "{quota-status.outputs}" # included as system health section
+      components:
+        - outputs/briefs/daily/{date}/market-sweep.md
+        - outputs/briefs/daily/{date}/news-intelligence.md
+        - outputs/briefs/daily/{date}/email-triage.md
+        - outputs/briefs/daily/{date}/slack-triage.md
+        - outputs/briefs/daily/{date}/open-loops.md
+        - outputs/briefs/daily/{date}/workstream-pulse.md
+        - outputs/briefs/daily/{date}/calendar.md
+      template: docs/prompts/morning-brief-template.md
+    outputs:
+      file: outputs/briefs/daily/{date}/ceo-morning-brief.md
+
+  - id: notify-ready
+    action: notify
+    description: Signal that the morning brief is ready
+    depends_on: [synthesise-brief]
+    inputs:
+      channel: slack
+      target: "#ceo-office"
+      message: "Morning Brief ready: outputs/briefs/daily/{date}/ceo-morning-brief.md"
+      approval_required: false # internal notification, low risk
+
+# Error handling
+on_failure:
+  action: log-and-notify
+  message: "Morning brief workflow failed at step {failed_step}"
+  notify: agent-self # the executing agent (operator)
+  severity: high
+
+# Output
+final_output: outputs/briefs/daily/{date}/ceo-morning-brief.md

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: agent # Follow up in the agent's own voice (mode resolved from config/agent.json voiceModes)
+    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 the principal'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: agent-self # the executing agent (operator)
+  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 the agent, classify urgency, prepare response options
+- **Agent**: slack-operator or gmail-operator → the agent operator
+
+### Regulatory Development
+
+- **Trigger**: Regulatory announcement, rule change, or compliance alert
+- **Action**: Assess impact on your organisation, update regulatory tracker, brief the principal if material
+- **Agent**: regulatory-watch → the agent operator
+
+### 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 your main repo
+- **Action**: Assess severity, route to engineering-coordination, brief if material
+- **Agent**: engineering-coordination → the agent operator
+
+### 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 → the agent operator
+
+## 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/event-driven/agent-failure-investigation.yaml

@@ -0,0 +1,137 @@
+# Agent Failure Investigation
+# Event-driven — triggered when a backlog executor agent fails or hangs
+# Uses agents-observe for session analysis and ccxray for token diagnostics
+
+name: agent-failure-investigation
+type: event-driven
+trigger:
+  event: agent_failure
+  source: backlog-executor # or any workflow that spawns agents
+  conditions:
+    - agent_exit_code: non-zero
+    - agent_timeout: exceeded
+    - agent_output: error_pattern
+description: >
+  Automated post-mortem when an agent fails. Pulls the full session trace
+  via agents-observe, analyses token/cost via ccxray logs, determines root
+  cause, and recommends remediation. Prevents recurring failures.
+
+steps:
+  # ── Pull session trace via agents-observe ──
+  - id: session-trace
+    skill: agents-observe
+    action: query-failed-session
+    description: >
+      Retrieve the full tool call sequence, timing data, and error state
+      for the failed agent session. Identify the last successful action
+      before failure.
+    timeout: 120
+    inputs:
+      session_id: "{trigger.session_id}"
+      agent_name: "{trigger.agent_name}"
+      query:
+        - full_tool_call_sequence
+        - last_successful_tool
+        - error_message
+        - timing_breakdown
+        - resource_state_at_failure
+    outputs:
+      file: outputs/investigations/{date}/{session_id}/session-trace.md
+      summary:
+        last_successful_tool: ""
+        error_type: "" # timeout|rate_limit|permission|context_overflow|unknown
+        duration_before_failure: ""
+        tool_call_count: 0
+
+  # ── Token analysis via ccxray ──
+  - id: token-analysis
+    skill: ccxray-diagnostics
+    action: analyse-failed-session
+    description: >
+      Check if the failure was token-related — context window overflow,
+      excessive input from tool reads, or cost runaway. Cross-reference
+      with session trace timing.
+    timeout: 120
+    parallel_with: session-trace
+    inputs:
+      session_id: "{trigger.session_id}"
+      log_dir: ~/.ccxray/logs/
+      checks:
+        - context_window_utilisation
+        - input_token_spike # large file reads or tool outputs
+        - output_token_pattern # repetitive or runaway generation
+        - cost_vs_average # compared to similar agent sessions
+    outputs:
+      file: outputs/investigations/{date}/{session_id}/token-analysis.md
+      summary:
+        context_peak_pct: 0
+        token_anomaly_detected: false
+        cost_vs_average: ""
+
+  # ── Quota state at time of failure ──
+  - id: quota-state
+    skill: claude-pace
+    action: check-quota-at-failure
+    description: >
+      Determine whether the failure was caused by or correlated with
+      API rate limiting. Check pace delta at the time of failure.
+    timeout: 30
+    parallel_with: session-trace
+    inputs:
+      timestamp: "{trigger.failure_timestamp}"
+      check:
+        - was_rate_limited
+        - pace_delta_at_time
+        - concurrent_sessions_count
+    outputs:
+      rate_limited: false
+      pace_delta: ""
+      concurrent_sessions: 0
+
+  # ── Root cause analysis ──
+  - id: root-cause-analysis
+    agent: engineering-oversight
+    action: determine-root-cause
+    description: >
+      Synthesise session trace, token analysis, and quota state to determine
+      the root cause. Classify the failure and recommend remediation.
+    timeout: 300
+    depends_on: [session-trace, token-analysis, quota-state]
+    inputs:
+      session_trace: outputs/investigations/{date}/{session_id}/session-trace.md
+      token_analysis: outputs/investigations/{date}/{session_id}/token-analysis.md
+      quota_state: "{quota-state.outputs}"
+      trigger_context: "{trigger}"
+    outputs:
+      file: outputs/investigations/{date}/{session_id}/root-cause.md
+      classification:
+        root_cause: "" # rate_limit|context_overflow|tool_error|prompt_bug|external_service|unknown
+        severity: "" # low|medium|high|critical
+        recurrence_risk: "" # low|medium|high
+        remediation: "" # specific fix recommendation
+
+  # ── Update tech debt / improvement backlog if systemic ──
+  - id: queue-remediation
+    agent: pmo-execution
+    action: queue-fix-if-systemic
+    description: >
+      If the root cause indicates a systemic issue (recurrence_risk: high),
+      create an item in tech-debt or improvement-backlog queue.
+    timeout: 60
+    depends_on: [root-cause-analysis]
+    condition: "{root-cause-analysis.outputs.classification.recurrence_risk} == high"
+    inputs:
+      root_cause: outputs/investigations/{date}/{session_id}/root-cause.md
+      target_queue: state/queues/tech-debt.yaml
+      item:
+        title: "Agent failure: {trigger.agent_name} — {root-cause-analysis.outputs.classification.root_cause}"
+        priority: high
+        source: "auto:agent-failure-investigation"
+
+on_failure:
+  action: log-and-notify
+  message: "Agent failure investigation failed for session {trigger.session_id}"
+  notify: agent-self # the executing agent (operator)
+  severity: medium
+
+final_output: outputs/investigations/{date}/{session_id}/root-cause.md

package/workflows/event-driven/pr-review.yaml

@@ -0,0 +1,107 @@
+# PR Review Workflow
+# Event-driven — triggered when a new PR is opened or updated in a tracked repo
+# Uses code-review-graph for structural analysis before human/agent review
+
+name: pr-review
+type: event-driven
+trigger:
+  event: pull_request
+  actions: [opened, synchronize]
+  # Repository list is loaded from config/repo-registry.yaml at runtime so
+  # each agent watches the set of repos relevant to its own scope. The
+  # entries below are illustrative defaults the framework ships with; agents
+  # override them in their own repo-registry.yaml.
+  repos:
+    - adapticai/engine
+    - adapticai/backend
+    - adapticai/frontend
+    - adapticai/maestro
+description: >
+  Automated PR review pipeline. When a PR is opened or updated, runs structural
+  blast radius analysis via code-review-graph, then produces a review brief.
+  Engineering agents use this to make informed review decisions.
+
+steps:
+  # ── Structural blast radius analysis ──
+  - id: blast-radius
+    skill: code-review-graph
+    action: blast-radius-analysis
+    description: >
+      Analyse the PR diff through the tree-sitter knowledge graph. Map which
+      functions, modules, and entry points are affected by the changes.
+      Determine risk level based on dependency depth and consumer count.
+    timeout: 300
+    inputs:
+      repo: "{trigger.repo}"
+      pr_number: "{trigger.pr_number}"
+      base_branch: "{trigger.base_ref}"
+      head_branch: "{trigger.head_ref}"
+      analysis:
+        - changed_functions
+        - direct_dependents
+        - transitive_impact
+        - affected_entry_points
+        - untouched_related_functions # functions that probably should have changed
+    outputs:
+      file: outputs/reviews/{repo}/{pr_number}/blast-radius.md
+      summary:
+        risk_level: low|medium|high|critical
+        direct_dependents: 0
+        transitive_impact: 0
+        missing_changes: [] # related functions not in the diff
+
+  # ── Review context enrichment ──
+  - id: review-context
+    skill: code-review-graph
+    action: review-context
+    description: >
+      Pull structural context for each changed file — what calls them, what
+      they call, hot paths, and critical modules. Provides the reviewer with
+      the "why this matters" context for every changed file.
+    timeout: 180
+    parallel_with: blast-radius
+    inputs:
+      repo: "{trigger.repo}"
+      changed_files: "{trigger.changed_files}"
+    outputs:
+      file: outputs/reviews/{repo}/{pr_number}/review-context.md
+
+  # ── Produce review brief ──
+  - id: review-brief
+    agent: engineering-oversight
+    action: produce-pr-review-brief
+    description: >
+      Synthesise blast radius and review context into a concise review brief.
+      Highlights risk areas, suggests review focus, and flags missing changes.
+    timeout: 180
+    depends_on: [blast-radius, review-context]
+    inputs:
+      blast_radius: outputs/reviews/{repo}/{pr_number}/blast-radius.md
+      review_context: outputs/reviews/{repo}/{pr_number}/review-context.md
+      pr_metadata:
+        repo: "{trigger.repo}"
+        pr_number: "{trigger.pr_number}"
+        author: "{trigger.author}"
+        title: "{trigger.title}"
+    outputs:
+      file: outputs/reviews/{repo}/{pr_number}/review-brief.md
+
+  # ── Post review brief as PR comment ──
+  - id: post-review
+    agent: github-operator
+    action: post-pr-comment
+    description: Post the review brief as a PR comment for the reviewer
+    depends_on: [review-brief]
+    inputs:
+      repo: "{trigger.repo}"
+      pr_number: "{trigger.pr_number}"
+      content: outputs/reviews/{repo}/{pr_number}/review-brief.md
+      format: markdown
+
+on_failure:
+  action: log-and-notify
+  message: "PR review workflow failed for {trigger.repo}#{trigger.pr_number} at step {failed_step}"
+  notify: agent-self # the executing agent (operator)
+  severity: low # PR review failure is inconvenient but not critical
+
+final_output: outputs/reviews/{repo}/{pr_number}/review-brief.md

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: agent-self # the executing agent (operator)
+  severity: medium
+
+final_output: outputs/board/monthly/{date}/board-readiness-review.md