@adaptic/maestro 1.1.1 → 1.1.3

package/.claude/commands/init-maestro.md

@@ -263,13 +263,21 @@ Sections to rewrite:
 - **## Operating Principles** -- Replace with the new principles. Use the same numbered-list format.
 - **## Communication Rules** -- Adapt the autonomy model to the archetype. An executive-operator has broad autonomy; a compliance-officer escalates more. Rewrite the "sends autonomously" and "escalates" sections with the new agent's name and appropriate boundaries. Keep the Immediate Acknowledgement Rule, Document Sharing, and Logging subsections but replace the agent name throughout.
 - **## People (Key Leadership)** -- Update the "That's you" line to the new agent. Keep other people entries unless the user indicated changes.
+- **## Control Towers** -- Replace the 12 generic org-wide control towers with 8-10 towers scoped to the agent's specific role and domain. Each tower should reflect what this agent actually monitors and manages. Generate towers based on archetype:
+  - **executive-operator**: Keep the original 12 org-wide towers (they are appropriate for this archetype).
+  - **technical-leader**: Model/platform architecture, R&D strategy, engineering quality, platform delivery, infrastructure & scalability, security & compliance, performance & benchmarking, team growth, systems & automation, self-governance.
+  - **commercial-leader**: Pipeline management, partnership development, investor relations, market intelligence, revenue operations, competitive analysis, client success, commercial governance, systems & automation, self-governance.
+  - **compliance-officer**: Regulatory submissions, licence management, policy framework, audit readiness, risk register, cross-jurisdiction compliance, legal obligations, reporting & disclosure, systems & automation, self-governance.
+  - **product-leader**: Product roadmap, user research & insights, feature delivery, design system, product-market fit, metrics & analytics, cross-functional alignment, stakeholder communication, systems & automation, self-governance.
+  - **operations-leader**: Process efficiency, fund operations, vendor management, capacity planning, organisational design, SLA compliance, cost management, operational resilience, systems & automation, self-governance.
+  Each tower should have a brief description of what it monitors (same format as the original: `**Name** — description`).
 
 Replace ALL instances of the old agent's first name with the new agent's first name throughout the entire CLAUDE.md file. Be thorough -- check every section header, bullet point, and inline reference.
 
 Do NOT modify these sections (keep them exactly as they are, except for agent name substitution):
 - Repository Layout, Key Config Files, Brand Assets, PDF Generation, Visual Media Generation
 - Source Repositories, Hiring Management (unless archetype is not executive-operator, in which case trim or adapt)
-- Operational Infrastructure, Control Towers 1-12
+- Operational Infrastructure
 - Build & Test, Code Standards, Three Operating Modes, Parallel Execution
 - Agent Development, Workflow Development
 

package/README.md

@@ -23,9 +23,7 @@ The package provides: framework scripts (poller, daemon, triggers, hooks, PDF an
 ```bash
 npx @adaptic/maestro create jacob-ai
 cd jacob-ai
-sudo npm run configure-macos    # Auto-login, disable sleep, Parsec, Slack CDP
-npm run init-agent              # Create directories, install launchd agents, configure Claude Code
-claude "/init-maestro"          # Interactive identity and services wizard
+claude "/init-maestro"          # Handles everything: setup, identity, services, launchd
 ```
 
 ### Prerequisites
@@ -92,11 +90,14 @@ Scaffolds a new agent repository. This command:
 2. Copies all framework files (scripts, agents, workflows, policies, plugins, docs)
 3. Copies scaffold templates (CLAUDE.md and config/agent.ts stubs)
 4. Copies `.claude/` directory (settings and commands)
-5. Creates 30+ agent-specific directories (config, knowledge, memory, state, logs, outputs)
-6. Generates a `package.json` with all required scripts and dependencies
-7. Copies `.env.example` and `.gitignore`
-8. Initializes a git repository
-9. Runs `npm install`
+5. Creates 57 agent-specific directories (config, knowledge, memory, state, logs, outputs, self-optimization, tests)
+6. Generates 53 operational template files (16 queues, 10 dashboards, 13 configs, 9 knowledge schemas, 5 self-optimization)
+7. Generates a `package.json` with all required scripts and dependencies
+8. Copies `.env.example` and `.gitignore`
+9. Initializes a git repository
+10. Runs `npm install`
+
+After `create`, run `claude "/init-maestro"` to configure the agent's identity and bring it online. The wizard handles system bootstrap, identity configuration, service setup, launchd installation, and verification -- no other setup commands are needed.
 
 ### `npx @adaptic/maestro upgrade`
 
@@ -106,19 +107,25 @@ Updates framework files in an existing agent repo. This command copies the lates
 - `policies/` -- action classification, information barriers, prompt injection defence
 - `docs/` -- architecture, governance, runbooks
 - `public/assets/` -- brand assets
+- `workflows/`, `schedules/`, `teams/`, `desktop-control/`, `ingest/`, `mcp/`
 - `.claude/commands/` -- slash commands
 - `plugins/maestro-skills/` -- operational skills
+- `agents/` -- new agents are added, existing ones preserved (no deletions)
+
+It also creates any missing directories from the expanded directory set.
 
 Agent-specific files (`config/`, `CLAUDE.md`, `knowledge/`, `memory/`, `state/`, `logs/`) are never touched.
 
 ### `npx @adaptic/maestro doctor`
 
-Verifies the agent installation. Checks for:
+Verifies the agent installation. Checks for 16 essential files:
 
-- Essential files: `config/agent.ts`, `CLAUDE.md`, `.claude/settings.json`, `package.json`, setup scripts
-- Environment variables: `ANTHROPIC_API_KEY` (required), `SLACK_USER_TOKEN`, `GMAIL_APP_PASSWORD` (optional)
-- `node_modules` installation
-- Claude CLI availability
+- Core: `config/agent.ts`, `CLAUDE.md`, `.claude/settings.json`, `.claude/commands/init-maestro.md`, `package.json`
+- Setup: `scripts/setup/init-agent.sh`, `scripts/healthcheck.sh`, `scripts/daemon/maestro-daemon.mjs`, `scripts/local-triggers/generate-plists.sh`
+- Config: `config/environment.yaml`, `config/contacts.yaml`, `config/priorities.yaml`, `config/sla-defaults.yaml`
+- State: `state/dashboards/executive-summary.yaml`, `state/queues/action-stack.yaml`, `knowledge/decisions/decision-schema.yaml`
+- Environment: `.env` file with `ANTHROPIC_API_KEY` (required), `SLACK_USER_TOKEN`, `GMAIL_APP_PASSWORD` (optional)
+- Dependencies: `node_modules` installed, Claude CLI available
 
 ---
 
@@ -137,17 +144,18 @@ The `upgrade` command only updates framework infrastructure: scripts, policies,
 
 ## The /init-maestro Wizard
 
-After scaffolding, run `claude "/init-maestro"` to configure your agent's identity. The wizard runs in five phases:
-
-1. **Identity gathering** -- Prompts for agent name, surname, title, archetype, email, phone, Mac mini hostname, principal (reporting line), responsibilities, communication style, and operating principles.
-
-2. **Parallel file rewriting** -- Rewrites `config/agent.ts` with structured identity data, generates `CLAUDE.md` with the full behavioural charter, updates `config/environment.yaml` with paths and schedule, and adapts `schedules/triggers/*.md` with the new identity.
-
-3. **macOS configuration** -- Updates launchd plist labels and paths, sets `package.json` name and description, and configures script variables.
-
-4. **Third-party services** -- Walks through Slack, Gmail, Calendar, and optional integrations, writing credentials to `.env`.
+After scaffolding, run `claude "/init-maestro"` to configure your agent. This is the only command you need -- it handles everything from system setup to identity configuration to bringing the agent online. The wizard runs in eight phases:
 
-5. **Verification** -- Runs a health check to confirm all components are correctly configured.
+| Phase | What it does |
+|-------|-------------|
+| **0. System Bootstrap** | Checks prerequisites (Node.js, npm, Claude CLI, jq), runs `npm install`, creates directories, installs global Claude Code settings, creates `.env` from template |
+| **1. Identity Gathering** | Prompts for agent name, surname, title, archetype, email, phone, Mac mini hostname, principal (reporting line), responsibilities, communication style, operating principles |
+| **2. Parallel Rewrite** | 8 sub-agents rewrite the repo in parallel: `config/agent.ts`, `CLAUDE.md`, config files, `package.json`, scripts, agent definitions, triggers/workflows, and agent-specific tools/skills |
+| **3. Machine Config** | Generates launchd plists with the correct agent name, installs them, optionally configures macOS for headless 24/7 operation |
+| **4. Service Setup** | Walks through Slack, Gmail, Twilio, Cloudflare, voice integration -- writing credentials to `.env` |
+| **5. README** | Generates an agent-specific README.md |
+| **6. GitHub Repo** | Optionally creates a GitHub repository and pushes the initial commit |
+| **7. Verification** | Greps for stale references, validates `config/agent.ts`, runs healthcheck, prints summary |
 
 See [docs/guides/agent-persona-setup.md](docs/guides/agent-persona-setup.md) for the full persona configuration guide, including archetype defaults, Control Tower selection, contact classification, and manual fine-tuning.
 
@@ -173,7 +181,7 @@ Additional services are available via MCP servers and can be configured separate
 
 ### Environment Variables
 
-After running `npm run init-agent`, fill in the generated `.env` file:
+The `/init-maestro` wizard creates the `.env` file and walks you through filling in credentials. Key variables:
 
 ```bash
 # Core

package/docs/guides/agent-persona-setup.md

@@ -597,4 +597,4 @@ The 5-layer defence is universal and should not be weakened. The only customisat
 | `memory/profiles/channels/` | Channel tone and rules | Low | Builds up over time through interaction |
 | `config/brand-assets.yaml` | Usually unchanged | Low | Only change if agent serves a different brand |
 | `package.json` | Name and description | Low | Update to reflect new agent identity |
-| `scripts/local-triggers/plists/` | Launchd labels and paths | Low | Handled by `npm run init-agent` |
+| `scripts/local-triggers/plists/` | Launchd labels and paths | Low | Handled by `/init-maestro` Phase 3 (generate-plists.sh) |

package/package.json

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