@adaptic/maestro 1.8.3 → 1.8.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adaptic/maestro",
-  "version": "1.8.3",
+  "version": "1.8.4",
   "description": "Maestro — Autonomous AI agent operating system. Deploy AI employees on dedicated Mac minis.",
   "type": "module",
   "bin": {

package/workflows/continuous/backlog-executor.yaml

@@ -135,7 +135,7 @@ steps:
 on_failure:
   action: log-and-notify
   message: "Backlog executor cycle failed at step {failed_step}"
-  notify: sophie-chief-of-staff
+  notify: agent-self # the executing agent (operator)
   severity: high
   # If quota-gate fails, the entire cycle is skipped — this is by design
   quota_gate_failure: skip_cycle

package/workflows/continuous/inbound-monitor.yaml

@@ -1,6 +1,6 @@
 # Continuous Inbound Monitoring Loop
 # Runs perpetually via launchd — polls all channels and dispatches responses
-# This is the heartbeat of Sophie's always-on executive operations
+# This is the heartbeat of the agent's always-on executive operations
 
 name: inbound-monitor
 type: continuous # Not scheduled — runs as a persistent loop
@@ -17,7 +17,7 @@ monitors:
     interval_seconds: 60
     scope:
       - type: mentions
-        description: Any @mention of Sophie or Mehran
+        description: Any @mention of the agent or the principal
       - type: dms
         description: All direct messages
       - type: channels
@@ -65,8 +65,8 @@ dispatch:
 
   routing:
     direct-reply:
-      handler: sophie-chief-of-staff
-      description: Sophie handles directly — default route for most inbound
+      handler: agent-self # the executing agent (operator)
+      description: The agent handles directly — default route for most inbound
       max_response_time: 120 # 2 minutes for DMs, 5 minutes for channels
       priority: highest
 
@@ -77,11 +77,11 @@ dispatch:
       max_concurrent: 5
 
     escalate-to-ceo:
-      handler: sophie-chief-of-staff
+      handler: agent-self # the executing agent (operator)
       description: >
-        Alert Mehran only for binding commitments, regulatory submissions,
-        deal terms, or genuinely strategic decisions. Sophie decides when this applies.
-      method: slack-dm # DM Mehran on Slack
+        Alert the principal only for binding commitments, regulatory submissions,
+        deal terms, or genuinely strategic decisions. The agent decides when this applies.
+      method: slack-dm # DM the principal on Slack
       fallback: whatsapp # If Slack unavailable, WhatsApp
 
     defer:
@@ -90,11 +90,11 @@ dispatch:
       output: outputs/inbound/deferred/
 
 # Autonomous response rules
-# Sophie is fully autonomous — she responds to all inbound communications
+# The agent is fully autonomous — she responds to all inbound communications
 # using her own judgement as Chief of Staff. No per-message approval gates.
 autonomous_response:
   enabled: true
-  mode: full_autonomy # Sophie decides what to send and when
+  mode: full_autonomy # The agent decides what to send and when
   categories:
     - id: dm-response
       description: Respond to any DM from any workspace user

package/workflows/daily/applicant-triage.yaml

@@ -191,7 +191,7 @@ steps:
 on_failure:
   action: log-and-notify
   message: "Daily applicant triage failed at step {failed_step}"
-  notify: sophie-chief-of-staff
+  notify: agent-self # the executing agent (operator)
   severity: medium
 
 final_output: outputs/briefs/daily/{date}/applicant-triage.md

package/workflows/daily/comms-triage.yaml

@@ -63,7 +63,7 @@ steps:
       update: knowledge/memory/executive-memory.yaml # add to open_loops
 
   - id: route-actions
-    agent: sophie-chief-of-staff
+    agent: agent-self # the executing agent (operator)
     action: route-action-items
     description: Route extracted action items to appropriate queues and agents
     timeout: 120
@@ -76,5 +76,5 @@ steps:
 on_failure:
   action: log-and-notify
   message: "Communications triage failed at step {failed_step}"
-  notify: sophie-chief-of-staff
+  notify: agent-self # the executing agent (operator)
   severity: high

package/workflows/daily/evening-wrap.yaml

@@ -99,7 +99,7 @@ steps:
 on_failure:
   action: log-and-notify
   message: "Evening wrap workflow failed at step {failed_step}"
-  notify: sophie-chief-of-staff
+  notify: agent-self # the executing agent (operator)
   severity: medium
 
 final_output: outputs/briefs/daily/{date}/ceo-evening-wrap.md

package/workflows/daily/morning-brief.yaml

@@ -157,7 +157,7 @@ steps:
 on_failure:
   action: log-and-notify
   message: "Morning brief workflow failed at step {failed_step}"
-  notify: sophie-chief-of-staff
+  notify: agent-self # the executing agent (operator)
   severity: high
 
 # Output

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

@@ -56,7 +56,7 @@ steps:
       policy: policies/communications-policy.yaml
     outputs:
       approved: [] # messages cleared for sending
-      pending_approval: [] # messages needing Mehran's review
+      pending_approval: [] # messages needing the principal's review
 
   - id: send-approved
     agent: slack-operator
@@ -83,5 +83,5 @@ steps:
 on_failure:
   action: log-and-notify
   message: "Slack follow-up sweep failed at step {failed_step}"
-  notify: sophie-chief-of-staff
+  notify: agent-self # the executing agent (operator)
   severity: medium

package/workflows/event-driven/README.md

@@ -7,14 +7,14 @@ These workflows trigger in response to events rather than on a schedule.
 ### 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
+- **Action**: Immediately surface to the agent, classify urgency, prepare response options
+- **Agent**: slack-operator or gmail-operator → the agent operator
 
 ### 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
+- **Agent**: regulatory-dfsa → the agent operator
 
 ### Pipeline Target Event
 
@@ -26,7 +26,7 @@ These workflows trigger in response to events rather than on a schedule.
 
 - **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
+- **Agent**: engineering-coordination → the agent operator
 
 ### Calendar Event Approaching
 
@@ -38,7 +38,7 @@ These workflows trigger in response to events rather than on a schedule.
 
 - **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
+- **Agent**: decision-log → the agent operator
 
 ## Implementation
 

package/workflows/event-driven/agent-failure-investigation.yaml

@@ -131,7 +131,7 @@ steps:
 on_failure:
   action: log-and-notify
   message: "Agent failure investigation failed for session {trigger.session_id}"
-  notify: sophie-chief-of-staff
+  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

@@ -7,12 +7,15 @@ type: event-driven
 trigger:
   event: pull_request
   actions: [opened, synchronize]
-  repos: # from config/repo-registry.yaml
+  # 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
-    - adapticai/sophie-ai
 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.
@@ -98,7 +101,7 @@ steps:
 on_failure:
   action: log-and-notify
   message: "PR review workflow failed for {trigger.repo}#{trigger.pr_number} at step {failed_step}"
-  notify: sophie-chief-of-staff
+  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

@@ -70,7 +70,7 @@ steps:
 on_failure:
   action: log-and-notify
   message: "Board readiness review failed at step {failed_step}"
-  notify: sophie-chief-of-staff
+  notify: agent-self # the executing agent (operator)
   severity: medium
 
 final_output: outputs/board/monthly/{date}/board-readiness-review.md

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

@@ -79,7 +79,7 @@ steps:
 on_failure:
   action: log-and-notify
   message: "Quarterly scenario analysis failed at step {failed_step}"
-  notify: sophie-chief-of-staff
+  notify: agent-self # the executing agent (operator)
   severity: medium
 
 final_output: outputs/memos/quarterly/{date}/strategic-scenario-analysis.md

package/workflows/session-protocol.md

@@ -1,6 +1,6 @@
 # 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.
+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
 
@@ -9,7 +9,7 @@ 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 |
+| **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.
 
@@ -46,7 +46,7 @@ Every new Claude Code session begins with this sequence:
 
 - 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
+- This is the critical step that prevents the agent from going dark during long tasks
 
 ### 7. Log session start
 
@@ -58,7 +58,7 @@ 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
+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
@@ -76,9 +76,9 @@ A priority trigger file is created at `state/triggers/priority/` when:
 ```yaml
 type: priority_trigger
 reason: "CEO DM detected during intra-session poll"
-source: "slack:D099N1JGKRQ:1775164334.094809"
-sender: "mehran-granfar"
-channel: "dm/mehran-granfar"
+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: |

package/workflows/weekly/engineering-health.yaml

@@ -148,7 +148,7 @@ steps:
 on_failure:
   action: log-and-notify
   message: "Engineering health check failed at step {failed_step}"
-  notify: sophie-chief-of-staff
+  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

@@ -163,7 +163,7 @@ steps:
 on_failure:
   action: log-and-notify
   message: "Weekly hiring review failed at step {failed_step}"
-  notify: sophie-chief-of-staff
+  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

@@ -70,7 +70,7 @@ steps:
 on_failure:
   action: log-and-notify
   message: "Rollup pipeline review failed at step {failed_step}"
-  notify: sophie-chief-of-staff
+  notify: agent-self # the executing agent (operator)
   severity: medium
 
 final_output: outputs/briefs/weekly/{date}/rollup-pipeline-review.md

package/workflows/weekly/strategic-memo.yaml

@@ -73,7 +73,7 @@ steps:
 on_failure:
   action: log-and-notify
   message: "Weekly strategic memo failed at step {failed_step}"
-  notify: sophie-chief-of-staff
+  notify: agent-self # the executing agent (operator)
   severity: medium
 
 final_output: outputs/memos/weekly/{date}/strategic-memo.md