@adaptic/maestro 1.1.2 → 1.1.4

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/package.json

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

package/scripts/setup/configure-macos.sh

@@ -331,7 +331,7 @@ configure_boot_services() {
 
     # Check which are loaded
     local loaded_count
-    loaded_count=$(launchctl list 2>/dev/null | grep -c "ai.adaptic" || echo "0")
+    loaded_count=$(launchctl list 2>/dev/null | grep -c "ai.adaptic" || true)
     if [ "$loaded_count" -gt 0 ]; then
       ok "$loaded_count agents currently loaded"
     else