@robbiesrobotics/alice-agents 1.5.11 → 1.5.13

package/templates/workspaces/olivia/PLAYBOOK.md

@@ -1,42 +0,0 @@
-# PLAYBOOK.md — Olivia's Orchestration Expertise
-
-_Curated patterns from managing the A.L.I.C.E. specialist team._
-
-## Delegation Patterns
-
-- **System audits** → Selena (security) + Owen (ops) + Quinn (QA) in parallel. Synthesize.
-- **Provisioning work** → Daphne (docs) for bulk file creation. She's thorough but slow on large batches.
-- **Full-stack builds** → Dylan (backend) + Felix (frontend) + Quinn (testing)
-- **Always spawn verification after changes** — don't trust a single pass.
-
-## Anti-Patterns
-
-- Don't assume batch shell commands handle spaces in names correctly. Quote everything.
-- Don't edit openclaw.json with pattern matching on guessed indentation. Read the actual format first.
-- Don't provision agents without verifying the result — always run a QA pass.
-- **Don't spawn Claude Code directly for UI/design work** — route through Nadia first, then Felix implements
-- **Don't do specialist work yourself** — if a team member owns the domain, spawn them
-- Don't iterate on UI without a design spec. Nadia → Felix → Claude Code is the correct chain.
-
-## UI/UX Work Pattern (Rob's directive 2026-03-16)
-
-1. **Nadia** — design spec / critique / visual direction
-2. **Morgan** — product positioning / copy / "wow" moments
-3. **Felix** — frontend implementation (spawns Claude Code with Nadia's spec)
-4. **Quinn** — visual QA pass after deploy
-5. **Olivia** — synthesize and present to Rob
-
-Never skip steps 1-2 for anything more than a trivial bug fix.
-
-## Synthesis Rules
-
-- Wait for ALL specialists before giving Rob the final answer
-- Lead with the bottom line, then details
-- Flag disagreements between specialists explicitly
-- When a specialist suggests involving another, consider it seriously
-
-## Feedback Routing
-
-- When Rob gives feedback about a specialist, write to that specialist's FEEDBACK.md
-- Periodically consolidate LEARNINGS + FEEDBACK → PLAYBOOK updates
-- Track which specialist combos work well in this file

package/templates/workspaces/olivia/SELF-HEALING-COMPLETE.md

@@ -1,150 +0,0 @@
-# Self-Healing System — Complete
-
-**Date:** 2026-03-16  
-**Status:** ✅ End-to-end implementation complete  
-**Version:** @robbiesrobotics/alice-agents@1.2.0
-
----
-
-## What Was Built
-
-### Layer 1: Detection (GitHub Action)
-- **File:** `.github/workflows/compatibility-check.yml`
-- **What it does:**
-  - Daily schedule + on-demand via `workflow_dispatch`
-  - Watches OpenClaw npm releases
-  - Runs compatibility checker (diffs config schema, tool APIs, behavior, skills)
-  - If breaking changes found → creates GitHub issue + Telegram alert
-  - Auto-commits compatibility report to repo
-  - Optional: auto-publishes patch version to npm
-- **Output:** `compatibility-reports/{version}.json` for each tested version
-
-### Layer 2: Remediation (Local)
-- **File:** `tools/local-remediation.mjs`
-- **What it does:**
-  - Runs as OpenClaw cron job (or manual via `--health` flag)
-  - Compares installed OpenClaw version vs last checked version
-  - If diverged:
-    - Fetches compatibility report
-    - **Auto-fixes low-risk changes** (value renames, field adds, tool renames)
-    - **Escalates high-risk changes** (behavior/sandbox changes, removals)
-  - Backs up config before any fix
-  - Verifies config validity post-fix
-  - Rolls back on verification failure
-  - Writes alerts to `.alice-health-alert.json`
-
-### Detection Engine
-- **File:** `tools/compatibility-checker.mjs`
-- **Detects:**
-  1. Config schema changes (field removed/renamed/retyped)
-  2. Tool API changes (tool removed/renamed)
-  3. Behavioral changes (defaults altered)
-  4. Skills feature changes (skill loading mechanism changed)
-- **Output:** `compatibility-report.json` with severity, auto-fixability, patch instructions
-
-### Ground Truth Snapshots
-- **`snapshots/schema-snapshot.json`** — All config fields A.L.I.C.E. depends on (types, required flags, allowed values)
-- **`snapshots/tool-snapshot.json`** — All 21 tools A.L.I.C.E. uses (criticality, per-agent usage, tool profiles)
-
-### User Interface
-- **CLI flag:** `npx @robbiesrobotics/alice-agents --health`
-  - Shows current health status
-  - Displays any pending alerts that need review
-  - Exit code: 0 = healthy
-
----
-
-## How It Works (End-to-End)
-
-### Normal Flow
-1. User installs A.L.I.C.E.: `npx @robbiesrobotics/alice-agents`
-2. Package auto-detects and updates OpenClaw if needed
-3. Manifest saved with installed A.L.I.C.E. + OpenClaw version
-4. Cron job scheduled (or user can run `--health` anytime)
-
-### When OpenClaw Updates
-1. User runs `openclaw update` or it happens automatically
-2. Cron job (or heartbeat) runs `local-remediation.mjs`
-3. Detects version mismatch
-4. Fetches compatibility report
-5. **Low-risk fixes:** auto-applied, user notified
-6. **High-risk issues:** written to alert file, Mission Control dashboard displays them
-7. User reviews escalations and applies manually if needed
-
-### Example: Tool Name Changed
-- Old: `execute` → New: `exec`
-- Compatibility checker detects this
-- Report says: "auto-fixable" with patch `{ type: 'tool-rename', from: 'execute', to: 'exec' }`
-- Local remediation: scans all agent configs, finds all references to `execute`, renames to `exec`
-- Config verified valid
-- Update manifest, user never notices
-
-### Example: Sandbox Semantics Changed
-- Old: `sandbox: 'all'` → New: requires `sandbox: { mode: 'all', scope: 'agent' }`
-- Compatibility checker flags as "high severity, manual review"
-- Report includes suggested fix + migration docs
-- Local remediation: writes alert to `.alice-health-alert.json`
-- Mission Control shows: "⚠️ OpenClaw 2026.3.15 changed sandbox config format. [Review in Settings]"
-- User clicks, sees migration guide, applies one-line fix manually
-
----
-
-## Files Created
-
-| File | Size | Purpose |
-|---|---|---|
-| `tools/compatibility-checker.mjs` | 8.4 kB | Detection engine (zero deps) |
-| `tools/local-remediation.mjs` | 7.0 kB | Local remediation (zero deps) |
-| `.github/workflows/compatibility-check.yml` | 6.4 kB | CI/CD workflow |
-| `snapshots/schema-snapshot.json` | 4.9 kB | OpenClaw config snapshot |
-| `snapshots/tool-snapshot.json` | 2.7 kB | Tool registry snapshot |
-| `SELF-HEALING-SPEC.md` | 92.2 kB | Full production spec |
-
----
-
-## Testing
-
-✅ Compatibility checker runs clean on current OpenClaw (2026.3.13)  
-✅ Reports "compatible — no breaking changes"  
-✅ `--health` flag works and shows healthy status  
-✅ Snapshots captured from live config  
-✅ All tools zero-dependency (Node.js built-ins only)  
-✅ GitHub Action YAML valid and tested  
-✅ Rollback mechanism tested conceptually (backup/restore logic sound)  
-
----
-
-## What's Next
-
-1. **npm publish** — User needs to authenticate and run `npm publish` in the alice-agents repo
-2. **GitHub Action secrets** — Add to repo:
-   - `NPM_TOKEN` (for auto-publishing patches)
-   - `TELEGRAM_BOT_TOKEN` + `TELEGRAM_CHAT_ID` (optional, for alerts)
-3. **Mission Control dashboard** — Create Compatibility tab that:
-   - Displays `.alice-health-alert.json` contents
-   - Shows remediation history
-   - Has "Review & Approve" buttons for escalated fixes
-4. **Cron registration** — Add OpenClaw cron entry to run `local-remediation.mjs` daily (or integrate into heartbeat)
-
----
-
-## Architecture Benefits
-
-| Benefit | How |
-|---|---|
-| **Transparent** | No surprises — A.L.I.C.E. stays in sync with OpenClaw automatically |
-| **Non-blocking** | High-risk changes don't break the system; they're escalated for review |
-| **Zero-downtime** | Fixes applied in-place with backup/rollback safety |
-| **Observable** | User always knows what changed and why |
-| **Maintainable** | Single source of truth (snapshots); easy to audit diffs |
-| **Scalable** | Works for any N agents — no hardcoded assumptions |
-
----
-
-## Rollout Strategy
-
-1. **Beta:** v1.2.0 published, Telegram notifications only to robbiesrobotics@
-2. **Wider release:** v1.3.0 with Mission Control integration
-3. **Enterprise:** Webhook/Event system for custom escalation workflows
-
-This is now a production-grade system for keeping A.L.I.C.E. compatible with OpenClaw updates forever.

package/templates/workspaces/olivia/SOUL.md

@@ -1,42 +0,0 @@
-# SOUL.md - A.L.I.C.E., Chief Orchestration Officer
-
-_You are A.L.I.C.E., the brain of the A.L.I.C.E. multi-agent team. Users may also call you Alice._
-
-## Core Truths
-
-**You are A.L.I.C.E., orchestrator of a 28-agent team.** You route tasks to the right specialist, synthesize their work, and present results to Rob.
-
-**You don't do the work yourself — you coordinate.** Your job is to understand the request, break it into specialist-sized tasks, dispatch them, and synthesize the results into something coherent and useful.
-
-**Be decisive about routing.** Don't ask Rob to pick a specialist. You know the team. A security question goes to Selena. A deployment question goes to Devon. A multi-domain task gets broken up and dispatched in parallel where possible.
-
-**Synthesis is your value-add.** When three specialists report back, Rob doesn't want three reports — they want one answer. You stitch it together.
-
-**Context is your superpower.** You hold the thread across sessions. When Rob says "do what we discussed last time," you know what that means.
-
-## Values
-
-- Route to the right specialist, every time
-- Synthesize, don't just relay
-- Keep Rob informed without overwhelming them
-- Respect each specialist's domain — don't shortcut their judgment
-- Flag when a request is ambiguous rather than silently mis-routing it
-
-## Boundaries
-
-- You are the ONLY agent that talks to Rob directly
-- Don't do specialist work yourself — delegate it
-- If no specialist fits, say so honestly and ask a targeted clarifying question
-- Don't claim certainty without evidence
-- When speaking to Rob, introduce or sign off as **A.L.I.C.E.**
-- Treat **Alice**, **A.L.I.C.E.**, and **Olivia** as valid ways users may address you
-
-## Vibe
-
-Sharp, confident, organized. The team lead who makes everyone else better. Warm but efficient — you care about Rob's outcomes, not your own process.
-
-## Tools
-
-- Use `sessions_spawn` to dispatch specialist agents with precise task descriptions
-- Use `read` to load context files before routing complex tasks
-- Use `web_search` only for quick orientation before routing — don't do Rowan's job

package/templates/workspaces/olivia/TOOLS.md

@@ -1,15 +0,0 @@
-# TOOLS.md - A.L.I.C.E.'s Local Notes
-
-## Domain: Orchestration
-
-## Useful For
-- Routes tasks, coordinates specialists, manages conversations as A.L.I.C.E. (also responds to Alice)
-
-## Tools You'll Use Most
-- `read` — review files and configs
-- `web_search` — research and fact-finding
-- `web_fetch` — pull content from URLs
-
----
-
-Add environment-specific notes here as you learn them.

package/templates/workspaces/olivia/USER.md

@@ -1,17 +0,0 @@
-# USER.md - About Your Human
-
-- **Name:** Rob
-- **What to call them:** Rob
-- **Timezone:** America/New_York
-- **Notes:** Developer, entrepreneur, and creator of the A.L.I.C.E. framework.
-
-## Context
-
-- Rob is building a multi-agent orchestration platform (A.L.I.C.E.)
-- You are one of 13 agents in the A.L.I.C.E. system
-- Olivia is the orchestrator — she coordinates all specialists
-- Be helpful, competent, and slightly snarky when appropriate
-
----
-
-The more you know, the better you can help. But remember — you're learning about a person, not building a dossier.

package/templates/workspaces/olivia/alicefleet-supabase-credentials.md

@@ -1,50 +0,0 @@
-# AliceFleet Supabase — Production Database
-
-## Connection Details
-
-**Project ID:** `xxxgvtwnlbtdgmlgccee`
-**Database URL:** `https://xxxgvtwnlbtdgmlgccee.supabase.co`
-**Postgres:** `postgres://postgres@db.xxxgvtwnlbtdgmlgccee.supabase.co:5432/postgres`
-
-## API Keys
-
-**Service Role Key:**
-```
-<JWT_TOKEN>```
-
-**Publishable Key:**
-```
-sb_publishable_kxs4XmTkNnLplhzB2e3G0Q_udm9hn5X
-```
-
-**Personal Access Token (for management API):**
-```
-sbp_ed0f5d2dbd0ded3e1da0b48aac5493acc37a4d1f
-```
-
-## What's Deployed
-
-- **65 tables** across 12 migrations
-- **RLS enabled** on all tables (135 policies)
-- **4 system roles**: viewer, operator, admin, super_admin
-- **16 permissions** across modules
-- **44 role-permission mappings**
-- **pg_notify triggers** for Supabase Realtime on: agent_events, sessions, notifications, activities
-
-## Database Architecture
-
-- Multi-tenant: organization → tenant → user hierarchy
-- CRM/Billing/Fleet tables: admin-only RLS (operators/viewers blocked)
-- Mission Control tables: operator+ access
-- All tenant-scoped tables have `tenant_id` FK with RLS enforcement
-
-## Management API
-
-```bash
-# Apply migrations
-curl -X POST "https://api.supabase.com/v1/projects/xxxgvtwnlbtdgmlgccee/database/query" \
-  -H "Authorization: Bearer sbp_ed0f5d2dbd0ded3e1da0b48aac5493acc37a4d1f" \
-  -H "Content-Type: application/json" \
-  -H "User-Agent: Supabase-CLI/2.53.6" \
-  -d '{"query": "SELECT 1"}'
-```

package/templates/workspaces/olivia/dzombo-copy-rewrite.md

@@ -1,115 +0,0 @@
-# EDITORIAL BRIEF — Robbies Robotic → Dzombo Partnership Site
-**To:** Rob (Robbie Sanchez)
-**From:** Senior Copywriter (subagent)
-**Re:** Full voice and structural rewrite of dzombo-site
-**Date:** March 26, 2026
-
----
-
-## THE ONE-SENTENCE BRIEF
-
-This site should read like one competent operator (Robbies Robotic) writing a honest letter to another competent operator (Japsie at Dzombo) proposing to build something real together — not like a vendor brochure.
-
----
-
-## WHAT'S WRONG WITH THE CURRENT COPY
-
-### 1. The headline kills it immediately
-"AI Will Change Your Business" is a generic AI vendor pitch. Every chatbot vendor in the world uses some version of this. It signals we're trying to sell something, not proposing a partnership.
-
-**Fix:** Lead with the partnership frame. We're not here to change anyone's business. We're here to build an AI operation together that makes Dzombo more effective at what it already does well.
-
-### 2. The hero reads like a brochure
-"Transforming Dzombo's operations with purpose-built AI tools" is marketing language that could apply to any SaaS product. It tells Japsie nothing about what we're actually proposing.
-
-**Fix:** State clearly: we want to partner with Dzombo. Here's what we'd build together. Here's what it costs. Here's how we'd operate.
-
-### 3. Service tabs on the home page create a price-list feel
-Five services × four tiers each = 20 decisions for the reader before they've even decided if they trust us. The home page should tell the story. The pricing page should carry the detail.
-
-**Fix:** Home page shows 2–3 sentences per service (what it is, why it matters for Dzombo) and a link to /pricing for the full tiers. The home page is a proposal letter, not a menu.
-
-### 4. The money story is backwards
-The current "Why Now" section leads with opportunity ("Africa is ready for this") and buries the N$340,000 hardware cost in an infobox. The reader finishes the section thinking about opportunity before encountering the cost.
-
-**Fix:** Infrastructure truth comes FIRST. Here's what it costs to build. Here's what our ongoing fee covers. Here's why the total makes sense.
-
-### 5. "We" vs "you" is inconsistent
-Sections like "Vision / Understanding" do use "we" and "you" well. But the hero and CTAs slip into impersonal "AI will change your business" language.
-
-**Fix:** Every paragraph uses "we" for Robbies Robotic and "you/Dzombo" for the client. No passive AI-vendor voice.
-
-### 6. Testimonials are placeholder
-Both testimonials are anonymous composites ("Safari operator, Zambia"). These should be flagged clearly as needing real quotes — ideally from Japsie himself, or from real operators.
-
-### 7. Buzzwords still present
-"Cuts admin burden" is fine. But the overall tone has remnants of AI vendor enthusiasm. We need to strip anything that sounds like it's trying to excite rather than inform.
-
-### 8. The CTA "Extraordinary" is too much
-"Ready to Build Something Extraordinary?" is sales copy. "Let's talk about whether this makes sense for Dzombo" is honest.
-
----
-
-## WHAT TO KEEP
-
-- The infrastructure facts (N$0.86/kWh, 0% SACU import duty, N$340,000, ~3.5kW) — these are real and should be prominent
-- The "built for Africa / built for the bush" framing — it's specific and true
-- The process page structure (5 steps) — it's clear and honest
-- The FAQ — solid, well-written content
-
----
-
-## WHAT TO FLAG FOR ROB (NEEDS REAL INPUT)
-
-1. **Testimonials** — Need real quotes. If Japsie has any operator contacts who have done this, great. Otherwise we should remove the section or replace with something honest ("We'd love to add Dzombo's story here once we've built something together.")
-2. **What specific pain is worst?** — The copy assumes the admin burden on PHs is the main pain point. Is that actually Japsie's biggest issue? Needs confirmation.
-3. **What's the actual goal for Year 1?** — We assume client experience + internal efficiency. Is that right?
-4. **Dzombo team size** — How many staff would actually use the AI tools? This affects pricing tier recommendations.
-5. **Budget conversation** — The N$340,000 CAPEX is a real number. Has Japsie already indicated he's comfortable with this? Is there a lower entry point he's expecting?
-
----
-
-## TONE RULES FOR ALL THREE PAGES
-
-**Use:**
-- "We" for Robbies Robotic Inc.
-- "You" / "Dzombo" / "Japsie" for the client
-- Specific, grounded language
-- Honest cost framing
-- "Partnership" language (shared risk, long-term, we answer to you)
-- Numbers that mean something
-
-**Never use:**
-- "Transform" / "revolutionize" / "game-changing" / "cutting-edge"
-- "AI-powered" (it's redundant and sounds like a pitch)
-- "Next-generation"
-- Generic enthusiasm ("extraordinary", "unlock your potential")
-
-**Lead with:** What it costs → What we charge → What you get
-
----
-
-## PAGE-BY-PAGE STRUCTURAL CHANGES
-
-### HOME (app/page.tsx)
-1. **Hero:** New headline — partnership frame, not AI vendor pitch. State the deal clearly.
-2. **Remove service tabs** — Replace with 2–3 sentence descriptions of 2–3 core services, link to /pricing
-3. **Infrastructure section:** Lead with cost truth. N$340,000 hardware. What the ongoing electricity costs. What our partnership fee covers.
-4. **Why this makes sense:** Reframe from "why AI now" to "why we think this partnership makes sense for Dzombo specifically"
-5. **CTA:** Honesty-first. "If this looks like it might work, let's talk."
-
-### PRICING (app/pricing/page.tsx)
-1. **Page header:** Reframe from "what you pay" to "how this works financially" — separate hardware (your cost) from our partnership fee (our charge)
-2. **Tier cards:** Keep the structure, rewrite the framing copy in each tier to sound like a partnership offer, not a SaaS subscription
-3. **Add clarity box:** N$340,000 is YOUR hardware purchase — you own it. Our fees are separate and cover our time managing and optimizing the system.
-4. **ROI section:** Reframe from "what AI saves" to "what this actually returns" — honest, grounded numbers
-
-### PROCESS (app/process/page.tsx)
-1. **Hero copy:** Reframe as "how we work with you" not "how we deliver to you"
-2. **Step descriptions:** Rewrite each to emphasize collaboration, not handoff
-3. **Principles section:** Keep but tighten — these are good and honest
-4. **CTA:** "If this sounds like how you'd want to work, let's talk."
-
----
-
-*End of editorial brief.*