leedab 0.5.3 → 0.6.1

package/clients/default/manifest.json

@@ -0,0 +1,191 @@
+{
+  "schema_version": "1.0",
+  "client_id": "default",
+  "display_name": "Local development",
+  "industry": null,
+  "tier": "founder",
+  "license_key": null,
+  "agents": [
+    "coo",
+    "concierge",
+    "marketing",
+    "content",
+    "video",
+    "campaigns",
+    "email",
+    "brand",
+    "sales",
+    "product",
+    "engineering",
+    "frontend",
+    "backend",
+    "devops",
+    "automation",
+    "strategy",
+    "research",
+    "people",
+    "ops",
+    "procurement",
+    "finance",
+    "investor",
+    "data",
+    "cx",
+    "legal",
+    "compliance",
+    "delivery",
+    "solutions",
+    "onboarding",
+    "implementation",
+    "champion"
+  ],
+  "overrides": {},
+  "playbook_files": [],
+  "template_ids": null,
+  "quickstart_by_agent": {
+    "coo": [
+      "Draft today's ops brief — what's moving, what's blocked, what needs founder input.",
+      "We're launching a new campaign next week. Build a cross-team plan for Marketing, Product, and Engineering.",
+      "Which team is most bottlenecked right now and what should we do about it?"
+    ],
+    "concierge": [
+      "Send my morning brief — schedule, top priority, one decision to make today.",
+      "I'm flying Sydney → Melbourne next Tuesday for a 2pm meeting. Build the trip itinerary.",
+      "Categorise my last 30 days of expenses and flag anything unusual."
+    ],
+    "marketing": [
+      "Write a LinkedIn post about why local-first AI beats cloud for SMBs.",
+      "Draft 3 subject line variants for a cold outreach email to logistics companies.",
+      "Write a one-paragraph product description for our website hero section."
+    ],
+    "content": [
+      "Write a 1000-word SEO post targeting 'how to automate payroll deductions without APIs'.",
+      "Draft newsletter #8 — main story: our new computer-use workflow. Two short items.",
+      "Write a case study for a 12-truck logistics fleet that cut payroll time by 80%."
+    ],
+    "video": [
+      "Write a 90-second LinkedIn video script: the problem with manual ops reconciliation.",
+      "Storyboard a 4-minute YouTube demo: LeedAB automating a driver hours workflow.",
+      "Write a talking-head outline for the founder: 'why we built LeedAB locally-first'."
+    ],
+    "campaigns": [
+      "Design a Google Search campaign targeting SMB ops managers. ICP, ad groups, copy variants.",
+      "Write an A/B test plan for our LinkedIn headline: pain-first vs outcome-first.",
+      "Build a UTM taxonomy for Q2. Channels: Google, LinkedIn, newsletter, referral."
+    ],
+    "email": [
+      "Write a 5-email welcome sequence for a new SMB customer who just signed up to LeedAB.",
+      "Write a cold outreach sequence targeting ops managers at 10-50 person logistics companies.",
+      "Build a re-engagement sequence for customers who haven't logged in for 30 days."
+    ],
+    "brand": [
+      "Audit slide 4 of our investor deck — three things to fix, one to keep.",
+      "Write an asset brief for a launch banner: 1200×630, ICP = logistics SMB, tone confident-direct.",
+      "Review our marketing site visuals and flag anything off-brand."
+    ],
+    "sales": [
+      "Write a 3-email cold outreach sequence for ops managers at 10–50 person logistics SMBs.",
+      "Write a demo script: one workflow, 6 minutes, maximum impact.",
+      "Build an objection handling guide for 'we already use Zapier'."
+    ],
+    "product": [
+      "Draft a feature spec for voice message tasks via WhatsApp.",
+      "Write user stories for the onboarding flow for a new SMB customer.",
+      "Create acceptance criteria for computer-use task execution."
+    ],
+    "engineering": [
+      "Write an ADR for the provider abstraction layer (Anthropic / OpenAI / local).",
+      "Review the streaming architecture and suggest reliability improvements.",
+      "Design the data model for multi-tenant task queues."
+    ],
+    "frontend": [
+      "Write a component spec for the AgentCard — props, variants, hover/selected states.",
+      "Review our current Tailwind setup and flag performance or accessibility issues.",
+      "Design the empty state for a new agent with no messages yet."
+    ],
+    "backend": [
+      "Design the API for multi-agent broadcast: one prompt → all 18 agents in parallel.",
+      "Write a Zod schema for the /api/chat request body with full validation.",
+      "ADR: when should we migrate from SQLite to Postgres? What's the trigger?"
+    ],
+    "devops": [
+      "Write a GitHub Actions CI pipeline: typecheck → lint → test → build → deploy.",
+      "Write a runbook for: deploy failed on Railway, dashboard is down, it's 2am.",
+      "Design the Docker build for the Next.js dashboard — multi-stage, minimal image."
+    ],
+    "automation": [
+      "Build me a workflow: when a new lead fills out our contact form, add them to Google Sheets and send a Slack notification.",
+      "Create a daily 9am workflow that fetches our top metrics and sends a summary email.",
+      "List all my active n8n workflows and show me which ones have run in the last 24 hours."
+    ],
+    "strategy": [
+      "Build a one-page competitive battlecard: LeedAB vs Zapier.",
+      "What's our ideal ICP and why? Give me a crisp two-paragraph answer.",
+      "Suggest three pricing tiers with rationale for each."
+    ],
+    "research": [
+      "Build a prospect brief on Acme Logistics — recent moves, tech stack signals, decision-makers.",
+      "Compare 3 competitor agentic ops platforms across deployment, voice channels, computer-use, pricing.",
+      "Size the AU SMB logistics ops automation market — TAM/SAM/SOM with sources."
+    ],
+    "people": [
+      "Write a job description for a senior backend engineer, Sydney remote, $160-200k + 0.25-0.75% equity.",
+      "Build an onboarding plan for a new ops hire starting Monday — day 1, week 1, month 1.",
+      "Draft a Q2 performance review template — quarterly cadence, 15-min written + 15-min call."
+    ],
+    "procurement": [
+      "Compare these 3 freight quotes for SYD→MEL 32 pallets and recommend one.",
+      "Build a supplier scorecard for our top carrier this quarter — on-time, defects, response time, pricing.",
+      "Coles deducted $2,400 against PO 8821. Draft the dispute response with evidence."
+    ],
+    "finance": [
+      "Build a runway model: $180k cash, $22k monthly burn. Three scenarios.",
+      "Calculate CAC and LTV: $8k/month spend, 4 new customers, $400 ACV, 24-month lifetime.",
+      "Write a budget vs actuals template for a 6-category monthly review."
+    ],
+    "investor": [
+      "Draft the April investor update. Wins: 30 customers. Ask: senior Node engineer hire.",
+      "Write a two-sentence answer to 'What makes LeedAB defensible?'",
+      "Summarise our traction story for a seed-stage VC intro email."
+    ],
+    "data": [
+      "Design a retention dashboard for a local-first SMB tool. What D1/D7/D30 metrics matter most?",
+      "We have 30 customers. Build a cohort analysis framework to identify which segments stick longest.",
+      "Map our full activation funnel from install → first workflow live. What are the drop-off points?"
+    ],
+    "legal": [
+      "Review our standard customer MSA — flag any clauses that expose us given our local-first data model.",
+      "Draft a privacy policy for a local-first AI agent that stores all data on the customer's machine.",
+      "What should we have in order before a seed raise? Give me a legal due diligence checklist."
+    ],
+    "compliance": [
+      "Run a SOC 2 Type 1 gap analysis for us — top 5 gaps blocking certification today.",
+      "Build a risk register starter — 8-10 likely operational risks for a 12-person SaaS.",
+      "Draft an Acceptable Use Policy in plain English — one page, examples on every rule."
+    ],
+    "delivery": [
+      "Draft a 30/60/90 engagement plan for a new logistics customer signed yesterday.",
+      "Build this week's delivery brief — what's moving, what's at risk, what needs founders.",
+      "Score our active customers on health (red/amber/green) and propose one action per amber/red."
+    ],
+    "solutions": [
+      "/build acme-logistics, NSW logistics co, 200 dispatches/day, similar to Tarheel",
+      "/build sunset-cafe, hospitality, 3 venues, mostly worried about CX and inventory",
+      "Show me the last three demos you built and which ones converted."
+    ],
+    "onboarding": [
+      "Draft the Day 0 kickoff brief for a new logistics client — three week-1 wins, calendar invite.",
+      "Run the Day 30 check-in template against this client's recent activity and flag anything drifting.",
+      "Write a one-paragraph 'first task replaced' celebration message for a Day 7 milestone."
+    ],
+    "implementation": [
+      "Write a one-page implementation brief for pulling Cario TMS dispatches into the ops workflow.",
+      "Scope a Xero direct-read integration for the finance agent — risks, effort, in/out of scope.",
+      "Three customers want the same MYOB sync — frame this as a reusable integration, not a one-off."
+    ],
+    "champion": [
+      "The Champion at Tarheel hasn't messaged in 8 days — draft a check-in DM.",
+      "Walk a Champion through adding their first n8n workflow without doing it for them.",
+      "The Champion is asking the same routing question for the third time — surface a pattern + adjust pacing."
+    ]
+  }
+}

package/clients/tarheel/INSTALL.md

@@ -0,0 +1,333 @@
+# Tarheel install guide
+
+For the Tarheel-appointed admin. Stand up LeedAB on the dispatcher Mac (or a Mac mini we ship). One-time setup, ~60-90 min if everything below is in hand.
+
+The system runs **locally on Tarheel hardware**. Your data lives in two folders on this machine and doesn't leave it unless an agent sends an outbound message you approved.
+
+---
+
+## Before you start
+
+You should have received from Mina or Muiez (via Signal / encrypted channel — never email):
+
+- [ ] **License key** — looks like `am_live_…` (paid tier, issued by `api.leedab.com`)
+- [ ] **License public key** (`LEEDAB_LICENSE_PUBKEY`) — used to verify the license signature; without it the system refuses to start
+- [ ] **Admin token** — 64-character hex string (operator-mutation auth)
+- [ ] **Anthropic API key** — `sk-ant-…` (the LLM provider)
+- [ ] **Telegram bot token** — for `@LeedABTarheelBot` (issued by `@BotFather`, owned by Mina/Muiez until rotated to Tarheel ops)
+- [ ] **Telegram webhook secret** — random string (paired with the bot token)
+- [ ] **Allowlisted Telegram chat ID(s)** — for the Operations Manager and any other staff who can message the bot at all (`TELEGRAM_ALLOWED_CHATIDS`) and the smaller subset who can issue `/build` commands (`TELEGRAM_SOLUTIONS_CHATIDS`)
+
+If you're missing any of these, Telegram Mina before starting. Don't proceed with placeholders — every one of these is a security boundary.
+
+---
+
+## Step 1 · Mac prerequisites (15 min from cold start)
+
+Required:
+
+| Tool | Version | Install |
+|---|---|---|
+| **Node.js** | 22.x or newer | `brew install node@22` |
+| **git** | any modern | `xcode-select --install` (macOS comes with this) |
+| **openssl** | any | comes with macOS |
+
+Verify in Terminal:
+
+```sh
+node -v   # must print v22.x.x or higher
+git --version
+openssl version
+```
+
+If `node -v` is below v22, install Node 22 before continuing. The onboarding script will refuse otherwise.
+
+Optional (recommended later, not required to run): **Obsidian** (free) for browsing the customer brain folder visually. Not needed for the system to work.
+
+---
+
+## Step 2 · Clone the repo (5 min)
+
+```sh
+cd ~
+git clone https://github.com/muiez/LeedAB-OS.git leedab
+cd leedab
+```
+
+Mina or Muiez will add your machine's GitHub identity to the private `muiez/LeedAB-OS` repo before you do this. If `git clone` fails with `repository not found`, ping them — access hasn't been granted yet.
+
+---
+
+## Step 3 · Install dependencies + run cofounder onboarding script (10 min)
+
+```sh
+cd ~/leedab
+bash bin/onboard-cofounder.sh
+```
+
+The script:
+1. Confirms Node ≥ 22 + npm + openssl are installed.
+2. Runs `npm ci` at the repo root and inside `apps/console/`.
+3. **Runs `npm run build`** so the leedab CLI (`bin/leedab.js`) can find its compiled JS in `dist/`. Without this, every `node bin/leedab.js …` call dies with `ERR_MODULE_NOT_FOUND`.
+4. Installs the pre-commit secret-scanner hook.
+5. Generates a development admin token and writes `apps/console/.env.local`.
+6. Runs typecheck + unit tests + secret scanner.
+
+If the final line says `setup incomplete`, scroll up and read the failed step. Don't continue — fix it first.
+
+---
+
+## Step 4 · Configure production env vars (15 min)
+
+Open `apps/console/.env.local` in any editor (TextEdit is fine). The onboarding script wrote a development token for `LEEDAB_ADMIN_TOKEN` — replace it with the **production admin token Mina sent you**.
+
+Then add the other variables:
+
+```ini
+# Already present from onboarding script — REPLACE with the production token
+LEEDAB_ADMIN_TOKEN=<paste from Mina>
+
+# License signature verification key (REQUIRED — system refuses to start without this)
+LEEDAB_LICENSE_PUBKEY=<paste from Mina>
+
+# Active customer
+LEEDAB_CUSTOMER_ID=tarheel
+
+# Anthropic LLM provider
+ANTHROPIC_API_KEY=<paste from Mina>
+
+# Vault encryption (REQUIRED — without this the app refuses to store passwords)
+LEEDAB_VAULT_KEY=<generate one: openssl rand -hex 32 — and store the value somewhere safe>
+
+# Tarheel Telegram bot
+TELEGRAM_BOT_TOKEN_TARHEEL=<paste from Mina>
+TELEGRAM_WEBHOOK_SECRET_TARHEEL=<paste from Mina>
+# WHO CAN MESSAGE THE BOT AT ALL — comma-separated chat IDs.
+# Without this, ANYONE who learns the bot's username can drive LLM cost.
+TELEGRAM_ALLOWED_CHATIDS_TARHEEL=<comma-separated chat IDs from Mina>
+# WHO CAN ISSUE /build COMMANDS (subset of above) — typically Mina + Muiez only.
+TELEGRAM_SOLUTIONS_CHATIDS_TARHEEL=<comma-separated chat IDs from Mina>
+```
+
+Save the file. The file lives at `~/leedab/apps/console/.env.local` and is gitignored — it never leaves the machine.
+
+After you have a `LEEDAB_VAULT_KEY` value, store it somewhere durable (1Password, the Mac Keychain, a sealed envelope in a drawer). **If you lose it, no one can recover the encrypted credentials.** Don't email it.
+
+---
+
+## Step 5 · Run the LeedAB CLI onboarding (10 min)
+
+This step is interactive. It asks you about LLM provider, license key, channels, and credential vault. Persists everything to `~/.leedab/` (a hidden folder in your home directory).
+
+```sh
+cd ~/leedab
+node bin/leedab.js onboard
+```
+
+When it asks:
+- **License key** — paste the `am_live_…` Mina sent.
+- **LLM provider** — choose Anthropic, paste your API key when prompted (or skip if already in `.env.local`).
+- **Channels** — Telegram only for now (you'll wire the bot in Step 7). Skip WhatsApp / Slack unless you've been told otherwise.
+- **Vault encryption** — choose the same `LEEDAB_VAULT_KEY` you set in Step 4.
+
+This writes `~/.leedab/openclaw.json` (gateway URL + token) and `~/.leedab/license.json` (cached license). The console reads both at request time.
+
+---
+
+## Step 6 · Provision Tarheel's brain folder (2 min)
+
+This creates `~/leedab-brains/tarheel/` — the local folder where agents persist Tarheel-specific operational state (audit logs, workflow templates, daily inbox notes, customer-specific knowledge as it accumulates).
+
+```sh
+cd ~/leedab
+bin/onboard-customer.sh tarheel logistics "Tarheel Logistics" logistics-pro
+```
+
+The script:
+- Creates `~/leedab-brains/tarheel/` from the schema template
+- Seeds `_Workflows/` with logistics-default workflow templates
+- Initializes the folder as a local git repo (so you can audit changes over time)
+
+**About this folder:**
+- It's just markdown files. The agents read and write it as their persistent memory.
+- You don't need Obsidian installed to use it — agents access it directly.
+- If you want to *browse* what the agents have written (audit logs, daily notes), install Obsidian (free) and open `~/leedab-brains/tarheel/` as a vault.
+- This folder lives only on this Mac. It's not synced anywhere. **If this Mac dies, the brain dies with it** — back it up. `bin/onboard-customer.sh` already git-init'd it; periodic `cd ~/leedab-brains/tarheel && git add -A && git commit -m snapshot && git push` to a private GitHub backup is the recommended path. Mina/Muiez can help set that up.
+
+---
+
+## Step 7 · Start the system (5 min)
+
+```sh
+cd ~/leedab
+node bin/leedab.js start
+```
+
+This boots two things:
+1. **OpenClaw gateway** on `127.0.0.1:18789` — the local AI runtime that handles LLM calls and tool use
+2. **Console (web dashboard)** on `127.0.0.1:3000` — the operator UI
+
+The terminal will print the console URL. Open it in Chrome or Safari.
+
+The wizard prompts you for:
+1. **Admin token** — paste the one you set in Step 4 (the production one, not the dev token).
+2. **License key** — should auto-fill from what you entered in Step 5; if not, paste the `am_live_…` again.
+
+Click `Validate →`. On success you land on the dashboard.
+
+If the wizard refuses your admin token, the most likely reason is that the value in `.env.local` doesn't match. Stop the system (Ctrl-C in Terminal), open `.env.local`, double-check the token, save, and re-run `node bin/leedab.js start`.
+
+---
+
+## Step 8 · Activate the Telegram bot (15 min)
+
+Tell Telegram where to send `@LeedABTarheelBot`'s messages. The bot has to know your machine's URL. Two paths:
+
+**Path A · Local-only first (recommended for the first week)**
+
+Skip Telegram. Use the dashboard at `http://127.0.0.1:3000` directly. Type into the agent chat panes from the same Mac. This proves the install works end-to-end before opening any inbound network surface.
+
+**Path B · Expose to Telegram**
+
+Tarheel ops want to message the bot from their phones. You need a public URL pointing at your Mac. The supported options:
+
+1. **Cloudflare Tunnel** — `cloudflared tunnel --url http://127.0.0.1:3000` gives you a temporary HTTPS URL. Free, no signup. Restart it on Mac wake.
+2. **Tailscale Funnel** — if you already use Tailscale, run `tailscale funnel 3000`. Stable URL, requires Tailscale account.
+3. **Permanent host (separately-hosted gateway)** — for production-grade exposure, the OpenClaw gateway and console can move to a Mac mini or VM that's always on. Mina/Muiez will help with this when you're ready to leave the dispatcher Mac behind.
+
+Once you have a public URL like `https://your-tunnel.example.com`, register it with Telegram:
+
+```sh
+curl -X POST "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN_TARHEEL}/setWebhook" \
+  -H "content-type: application/json" \
+  -d '{
+    "url": "https://your-tunnel.example.com/api/telegram/tarheel",
+    "secret_token": "'"${TELEGRAM_WEBHOOK_SECRET_TARHEEL}"'"
+  }'
+```
+
+Replace the URL with yours. Expect Telegram to reply `{"ok":true,"result":true,"description":"Webhook was set"}`.
+
+---
+
+## Step 9 · Smoke test (5 min)
+
+From a phone whose Telegram chat ID is in `TELEGRAM_ALLOWED_CHATIDS_TARHEEL`:
+
+1. Open a chat with `@LeedABTarheelBot`.
+2. Send: `What's our outstanding deduction count?`
+3. Within ~10s, expect a reply from the COO agent that either answers or asks a clarifying question.
+
+If nothing happens after 30s:
+- The Mac may have slept — wake it and retry.
+- The tunnel URL may have changed — re-run the `setWebhook` curl from Step 8.
+- The chat ID may not be in the allowlist — check `TELEGRAM_ALLOWED_CHATIDS_TARHEEL` in `.env.local` and restart the system.
+- The bot token may not match — verify `TELEGRAM_BOT_TOKEN_TARHEEL` and restart.
+
+To test that the allowlist actually rejects non-allowlisted chat IDs: send a message from a different Telegram account. Expect a polite "_This bot doesn't accept messages from your chatId_" reply.
+
+---
+
+## Day-to-day operations
+
+**The system runs as long as `node bin/leedab.js start` is open in Terminal.** If you close the Terminal window, the bot stops responding.
+
+For continuous operation:
+
+```sh
+# Run in the background, log to a file
+cd ~/leedab
+nohup node bin/leedab.js start > ~/leedab.log 2>&1 &
+```
+
+To check it's still running: `lsof -i :3000` and `lsof -i :18789` (both should show `node`). To stop: `node bin/leedab.js stop`.
+
+For production-grade auto-restart on Mac reboot, ask Mina/Muiez about the launchd plist setup — that's a follow-up after the first week of stable operation.
+
+---
+
+## Updating
+
+When Mina/Muiez ship a new version:
+
+```sh
+cd ~/leedab
+node bin/leedab.js stop
+git pull origin main
+npm ci
+npm run build
+cd apps/console && npm ci
+cd ..
+node bin/leedab.js start
+```
+
+If something breaks after a pull, run:
+
+```sh
+cd ~/leedab
+git log -10 --oneline
+```
+
+…and Telegram Mina the output. Don't troubleshoot upstream changes blind.
+
+---
+
+## What does what
+
+Tarheel's licensed agents (per `clients/tarheel/manifest.json`):
+
+| Agent | What they do |
+|---|---|
+| **COO** | The boss. Triages every inbound message and routes to the right specialist. |
+| **Concierge** | Quick-answer agent for routine questions and status checks. |
+| **Ops** | Dispatch exceptions, POD chase-ups, daily run sheets. Knows the Cario-only and Sydney-NZ handoff rules. |
+| **Procurement** | Supplier deductions (esp. Coles), PO follow-ups, supplier comms. Routes deductions through legal-shaped flow. |
+| **CX** | Customer-facing replies — tone-matched, time-zoned. |
+| **Finance** | Profitability views, cost-per-route, deduction recovery. |
+| **Sales** | Inbound enquiries, quote drafting, proposal follow-ups. |
+| **People** | Driver/subbie onboarding paperwork, leave, induction tracking. |
+| **Delivery** | Internal lifecycle management — the "head of delivery" within Tarheel's instance. |
+| **Onboarding** | New-customer / new-driver setup playbooks. |
+| **Champion** | Embedded enablement — coaches Ops on how to get more out of the agents over time. |
+
+The `Engineering`, `Marketing`, `Strategy` agents are NOT licensed for Tarheel. The dashboard hides them from the team rail.
+
+---
+
+## Where things live
+
+After install, the system has state in three places on this Mac:
+
+| Path | What's there | Backup it? |
+|---|---|---|
+| `~/leedab/` | The code itself. | No — `git pull` recovers it. |
+| `~/.leedab/` | Gateway config, license cache, encrypted credential vault. | Yes — daily snapshot to a separate disk. |
+| `~/leedab-brains/tarheel/` | Tarheel's customer brain — audit logs, workflow templates, accumulated operational state. | Yes — already git-init'd; push to a private GitHub backup periodically. |
+| `~/leedab/apps/console/data/` | Conversation history, queues, demo state. | Optional — useful for debugging, not load-bearing. |
+
+The dashboard's `npm run backup` command snapshots `~/leedab/apps/console/data/`. Ask Mina/Muiez for a similar pattern for `~/.leedab/` and `~/leedab-brains/tarheel/`.
+
+---
+
+## Security posture
+
+- Your data lives on this Mac. The agents read from `~/leedab-brains/tarheel/` and write back to the same place. No telemetry to LeedAB or Muiez.
+- Outbound LLM calls go to Anthropic only (or whichever provider you configured in Step 5).
+- The Telegram bot only accepts messages from chat IDs in `TELEGRAM_ALLOWED_CHATIDS_TARHEEL`. Non-allowlisted chat IDs get a polite refusal.
+- `/build` commands are gated by a stricter `TELEGRAM_SOLUTIONS_CHATIDS_TARHEEL` allowlist (typically just Mina + Muiez during initial pilot).
+- The admin token gates every operator-level config change. Without it, the wizard and admin tabs lock down.
+- Failed outbound sends queue locally and retry — no data loss if Telegram is briefly unreachable.
+- The vault encrypts credentials at rest using `LEEDAB_VAULT_KEY` (AES-256-GCM).
+- The pre-commit hook scans for accidentally-committed secrets before any `git push`.
+
+If you suspect a credential has leaked: rotate it immediately, then Telegram Mina. Don't push the cleanup until he's acknowledged.
+
+---
+
+## Help
+
+- **Setup blocker** — Telegram Mina (preferred) or Muiez.
+- **Day-to-day questions about an agent's behaviour** — message the agent directly in the dashboard chat. The Champion agent is specifically there to coach you.
+- **Critical incident** — Telegram Mina, voice if no reply within 15 min.
+
+Keep this file open the first week. Past that, you won't need it.

package/clients/tarheel/manifest.json

@@ -0,0 +1,34 @@
+{
+  "schema_version": "1.0",
+  "client_id": "tarheel",
+  "display_name": "Tarheel Logistics",
+  "industry": "logistics",
+  "tier": "logistics-pro",
+  "license_key": null,
+  "agents": [
+    "coo",
+    "concierge",
+    "ops",
+    "procurement",
+    "cx",
+    "finance",
+    "sales",
+    "people",
+    "delivery",
+    "onboarding",
+    "champion"
+  ],
+  "overrides": {
+    "ops": {
+      "append_block": "## Tarheel-specific notes\n\n- 5am Sydney shift handoff to NZ team \u2014 never delegate ops decisions across the handoff window without flagging in the dispatch.\n- Always confirm dispatch ID matches the SAP order before acting on a delivery exception.\n- Their TMS is Cario \u2014 never log into anything else even if asked.\n- Primary contact is the Operations Manager (Telegram morning, voice only if urgent)."
+    },
+    "procurement": {
+      "append_block": "## Tarheel procurement context\n\n- 200 deliveries/day average, scaling Q3.\n- Coles is a high-friction account \u2014 deductions get formal disputes through legal, not informal email.\n- Suppliers: SAP-driven; never bypass the PO system."
+    }
+  },
+  "playbook_files": [
+    "context/customers/tarheel/playbook.md"
+  ],
+  "template_ids": null,
+  "status": "active"
+}

package/context/brand-guide.md

@@ -0,0 +1,95 @@
+# LeedAB Brand Guide
+
+## Voice
+
+**Confident and direct. Startup energy, no fluff. Results over promises.**
+
+LeedAB copy should feel like a smart, competent peer explaining something clearly — not a marketing department producing jargon. We respect the reader's time and intelligence.
+
+## Voice Attributes
+
+| We are | We are not |
+|--------|------------|
+| Direct | Hype-y |
+| Specific | Vague |
+| Technical when it matters | Over-technical for the audience |
+| Honest about limits | Falsely humble |
+| Confident | Arrogant |
+| Warm | Cute |
+| Opinionated | Preachy |
+
+## Reference Copy (from leedab.com)
+
+These lines exemplify our voice:
+
+- "Runs your operations."
+- "Lives on hardware you control, uses your apps like a human, and completes workflows end-to-end."
+- "Install. Connect. Work."
+- "Not a chatbot. An operator."
+- "Uses your tools like a human."
+- "Message it where you already work."
+- "Works with your existing stack."
+- "Gets better every day."
+- "Your data stays in your building."
+- "Live in 10 minutes."
+
+Note what's doing the work: short sentences, concrete verbs, action-oriented. No abstractions.
+
+## Do / Don't
+
+### Do
+
+- Open with the reader's pain or a concrete operational scenario
+- Use specific numbers when available ("3 days → 20 minutes")
+- Use active voice
+- Use short sentences. Break up long ones.
+- Reference real tools by name (WhatsApp, Telegram, Slack, Excel, etc.)
+- Acknowledge tradeoffs honestly
+- End with a clear next step
+
+### Don't
+
+- Open with "In today's fast-paced business world..."
+- Use: leverage, synergy, streamline, empower, unlock, revolutionize, cutting-edge, best-in-class, world-class, game-changing, transformative, paradigm, holistic, robust, seamless, intuitive, powerful
+- Stack adjectives ("a powerful, intuitive, seamless platform")
+- Use passive voice where active works ("the tasks are handled" → "the agent handles the tasks")
+- Make abstract claims without specific proof
+- Use the word "solutions" when you mean "software" or "product"
+- Claim to be "the leading" / "the #1" / "best" without evidence
+- End with vague CTAs like "Learn more" or "Get in touch"
+
+## Phrasing Patterns
+
+**Pain → mechanism → result:**
+"Your payroll process involves three spreadsheets and two portals. LeedAB reads them, reconciles the data, and sends you a summary on WhatsApp. Same task, 20 minutes instead of three days."
+
+**Contrarian take:**
+"Everyone's building AI assistants. LeedAB is an AI operator. The difference: assistants talk. Operators do."
+
+**Credibility via specificity:**
+"A regional logistics company in Queensland runs LeedAB on a Mac Mini in their dispatch office. Vendor rates, payroll, contract details — all of it stays in the building."
+
+## Tone by Surface
+
+- **Landing page** — confident, punchy, benefit-forward. Short paragraphs. Strong visual hierarchy.
+- **Blog posts** — conversational but substantive. First-person where it fits ("We built LeedAB because..."). Share opinions, back them with reasoning.
+- **Social (LinkedIn)** — professional but with personality. Open with an insight or observation, not a question to the void.
+- **Social (Twitter/X)** — sharper, more opinionated. Fewer words per idea.
+- **Email outreach** — concise, personalized, one clear ask.
+- **Support replies** — warm but efficient. Acknowledge → fix → follow up.
+- **Investor updates** — direct, numbers-forward, honest about misses.
+- **Internal docs** — same quality bar as external, but can be denser and more technical.
+
+## Formatting
+
+- **Headlines:** Sentence case, not Title Case. "How local-first AI works" not "How Local-First AI Works"
+- **Lists:** Use when scanning matters. Prefer prose for explanations.
+- **Bold:** For scannable emphasis, sparingly. Overuse kills impact.
+- **Italics:** For titles of works, foreign words, or emphasis where bold would be too loud.
+- **Em dashes:** Use freely — they fit the voice. Don't use hyphens where em dashes belong.
+
+## The Test
+
+Before shipping any copy, read it aloud. If any sentence sounds like it could appear in an enterprise SaaS deck from 2017, cut or rewrite it.
+
+If you removed "LeedAB" and replaced it with the name of a generic competitor, would the copy still make sense? If yes, it's too generic — make it specific to us.