[OP-01] Jaime onboarding — Operator role setup

{
  "code": "## OP-01: Jaime Onboarding — Operator Role Setup\n\n### Role: C8 Operator\n**Responsibilities**: Read dashboards 2-3x/day, handle escalations, approve specs, monitor foundry health.\n\n---\n\n### 1. Control Plane CLI Access\n\n**File**: `c8_platform/c8_control_plane.py` (share via repo access)\n\n**Quick commands for Jaime**:\n```bash\n# From c8_platform/ directory\nPYTHONPATH=. python c8_control_plane.py status      # System pulse\nPYTHONPATH=. python c8_control_plane.py foundry      # Foundry dashboard\nPYTHONPATH=. python c8_control_plane.py siblings     # Sibling health\nPYTHONPATH=. python c8_control_plane.py queue        # Task queue\nPYTHONPATH=. python c8_control_plane.py approve <id> # Approve a spec\nPYTHONPATH=. python c8_control_plane.py reject <id>  # Reject with reason\n```\n\n**Setup for Jaime**:\n```bash\n# 1. Clone repo\ngit clone https://github.com/c8-org/c8-platform.git\ncd c8-platform\n\n# 2. Set environment (add to ~/.zshrc or ~/.bashrc)\nexport SUPABASE_URL=\"https://llfnvahxgwehcdoohgnf.supabase.co\"\nexport SUPABASE_KEY=\"<service_role_key>\"  # Carlos provides\nexport ANTHROPIC_API_KEY=\"<key>\"           # For MCP tools\n\n# 3. Install deps\npip install supabase httpx anthropic\n\n# 4. Test\ncd c8_platform && PYTHONPATH=. python c8_control_plane.py status\n```\n\n---\n\n### 2. Dashboard Reading Guide\n\n**Foundry Dashboard** (https://foundry-dashboard.vercel.app)\n\n**Check 3x/day: Morning (9 AM), Midday (1 PM), Evening (6 PM)**\n\n| Panel | What to look for | Action if abnormal |\n|-------|------------------|-------------------|\n| **Task Queue** | Pending count should decrease over time | If stuck >50 for 2h → check sibling health |\n| **Acceptance Rate** | Should be >50% | If <30% → check grader logs, adjust prompts |\n| **Active Siblings** | 3-5 green dots | If <2 online → restart heartbeat daemon |\n| **Cost/Day** | Should be <$10/day | If >$20 → check for runaway dispatches |\n| **Error Rate** | Should be <2% | If >5% → check API keys, rate limits |\n\n**Arm Leaderboard**: Shows which models perform best. Terminal Lu (Opus) for complex code, G3 Flash for simple tasks, Sonnet for medium.\n\n**Spec Quality Heatmap**: Shows which spec categories produce highest acceptance. Green = good, red = needs better prompts.\n\n**Key metrics to report to Carlos**:\n- Daily: tasks completed, acceptance rate, cost\n- Weekly: queue burndown, model performance comparison\n- Escalate immediately: API outage, cost spike >3×, zero acceptance rate\n\n---\n\n### 3. WhatsApp Escalation Notifications\n\n**Already configured in WA-03** (War Room group). Jaime receives:\n- 🚨 **Andon alerts**: Immediate (critical issues)\n- 🐙 **Pulse summaries**: Every 6 hours\n- ✅ **Task batches**: Hourly\n- ⚠️ **Stale siblings**: When arm offline >30 min\n\n**Jaime's escalation actions**:\n| Alert Type | Jaime's Action | SLA |\n|-----------|---------------|-----|\n| Andon: API down | Check Cloud Run logs, restart service | 1h business hours |\n| Andon: Cost spike | Check foundry dispatches, pause if needed | 2h |\n| Andon: Sibling stale | Restart heartbeat, check API keys | 4h |\n| Spec approval request | Review spec, approve/reject via CLI | 4h business hours |\n| CSMS critical alert | Forward to Carlos for trade decision | 24h |\n\n**Respond via WhatsApp** with:\n- `ACK` = acknowledged, working on it\n- `DONE` = resolved\n- `ESC @carlos` = escalating to Carlos\n- `SKIP` = not urgent, will handle later\n\n---\n\n### 4. Escalation SLA\n\n| Severity | Response Time | Resolution Time | Who |\n|----------|--------------|-----------------|-----|\n| **P0 Critical** | 30 min | 2h | Jaime + Carlos |\n| **P1 High** | 2h | 8h | Jaime |\n| **P2 Medium** | 4h | 24h | Jaime |\n| **P3 Low** | Next business day | 72h | Jaime |\n\n**Business hours**: 9 AM - 9 PM in Jaime's timezone (overlap with Carlos)\n**After hours**: P0 only (WhatsApp ring tone for Andon alerts)\n\n**Escalation path**:\n1. WhatsApp alert → Jaime ACKs\n2. Jaime investigates (CLI + dashboard)\n3. If can't resolve in SLA → escalate to Carlos\n4. If API/infra issue → check Cloud Run logs, restart services\n5. If code issue → create foundry task for Terminal Lu\n\n---\n\n### 5. First Week Checklist for Jaime\n\n- [ ] Clone c8-platform repo\n- [ ] Set up environment variables\n- [ ] Run `c8_control_plane.py status` successfully\n- [ ] Open Foundry Dashboard, read all panels\n- [ ] Join WhatsApp War Room group\n- [ ] Respond to first test Andon alert with `ACK`\n- [ ] Approve 3 specs via CLI (`approve <id>`)\n- [ ] Read CLAUDE.md for platform context\n- [ ] Review foundry_pipeline.py to understand grading flow\n- [ ] Shadow Carlos on one SEKO demo prep call\n\n### Jaime's Cursor Setup (since he's a Cursor geek)\n```json\n// .cursor/settings.json\n{\n  \"python.defaultInterpreterPath\": \"/usr/bin/python3\",\n  \"python.analysis.extraPaths\": [\"c8_platform\"],\n  \"editor.formatOnSave\": true,\n  \"terminal.integrated.env.osx\": {\n    \"PYTHONPATH\": \"${workspaceFolder}/c8_platform\"\n  }\n}\n```",
  "content": "## OP-01: Jaime Onboarding — Operator Role Setup\n\n### Role: C8 Operator\n**Responsibilities**: Read dashboards 2-3x/day, handle escalations, approve specs, monitor foundry health.\n\n---\n\n### 1. Control Plane CLI Access\n\n**File**: `c8_platform/c8_control_plane.py` (share via repo access)\n\n**Quick commands for Jaime**:\n```bash\n# From c8_platform/ directory\nPYTHONPATH=. python c8_control_plane.py status      # System pulse\nPYTHONPATH=. python c8_control_plane.py foundry      # Foundry dashboard\nPYTHONPATH=. python c8_control_plane.py siblings     # Sibling health\nPYTHONPATH=. python c8_control_plane.py queue        # Task queue\nPYTHONPATH=. python c8_control_plane.py approve <id> # Approve a spec\nPYTHONPATH=. python c8_control_plane.py reject <id>  # Reject with reason\n```\n\n**Setup for Jaime**:\n```bash\n# 1. Clone repo\ngit clone https://github.com/c8-org/c8-platform.git\ncd c8-platform\n\n# 2. Set environment (add to ~/.zshrc or ~/.bashrc)\nexport SUPABASE_URL=\"https://llfnvahxgwehcdoohgnf.supabase.co\"\nexport SUPABASE_KEY=\"<service_role_key>\"  # Carlos provides\nexport ANTHROPIC_API_KEY=\"<key>\"           # For MCP tools\n\n# 3. Install deps\npip install supabase httpx anthropic\n\n# 4. Test\ncd c8_platform && PYTHONPATH=. python c8_control_plane.py status\n```\n\n---\n\n### 2. Dashboard Reading Guide\n\n**Foundry Dashboard** (https://foundry-dashboard.vercel.app)\n\n**Check 3x/day: Morning (9 AM), Midday (1 PM), Evening (6 PM)**\n\n| Panel | What to look for | Action if abnormal |\n|-------|------------------|-------------------|\n| **Task Queue** | Pending count should decrease over time | If stuck >50 for 2h → check sibling health |\n| **Acceptance Rate** | Should be >50% | If <30% → check grader logs, adjust prompts |\n| **Active Siblings** | 3-5 green dots | If <2 online → restart heartbeat daemon |\n| **Cost/Day** | Should be <$10/day | If >$20 → check for runaway dispatches |\n| **Error Rate** | Should be <2% | If >5% → check API keys, rate limits |\n\n**Arm Leaderboard**: Shows which models perform best. Terminal Lu (Opus) for complex code, G3 Flash for simple tasks, Sonnet for medium.\n\n**Spec Quality Heatmap**: Shows which spec categories produce highest acceptance. Green = good, red = needs better prompts.\n\n**Key metrics to report to Carlos**:\n- Daily: tasks completed, acceptance rate, cost\n- Weekly: queue burndown, model performance comparison\n- Escalate immediately: API outage, cost spike >3×, zero acceptance rate\n\n---\n\n### 3. WhatsApp Escalation Notifications\n\n**Already configured in WA-03** (War Room group). Jaime receives:\n- 🚨 **Andon alerts**: Immediate (critical issues)\n- 🐙 **Pulse summaries**: Every 6 hours\n- ✅ **Task batches**: Hourly\n- ⚠️ **Stale siblings**: When arm offline >30 min\n\n**Jaime's escalation actions**:\n| Alert Type | Jaime's Action | SLA |\n|-----------|---------------|-----|\n| Andon: API down | Check Cloud Run logs, restart service | 1h business hours |\n| Andon: Cost spike | Check foundry dispatches, pause if needed | 2h |\n| Andon: Sibling stale | Restart heartbeat, check API keys | 4h |\n| Spec approval request | Review spec, approve/reject via CLI | 4h business hours |\n| CSMS critical alert | Forward to Carlos for trade decision | 24h |\n\n**Respond via WhatsApp** with:\n- `ACK` = acknowledged, working on it\n- `DONE` = resolved\n- `ESC @carlos` = escalating to Carlos\n- `SKIP` = not urgent, will handle later\n\n---\n\n### 4. Escalation SLA\n\n| Severity | Response Time | Resolution Time | Who |\n|----------|--------------|-----------------|-----|\n| **P0 Critical** | 30 min | 2h | Jaime + Carlos |\n| **P1 High** | 2h | 8h | Jaime |\n| **P2 Medium** | 4h | 24h | Jaime |\n| **P3 Low** | Next business day | 72h | Jaime |\n\n**Business hours**: 9 AM - 9 PM in Jaime's timezone (overlap with Carlos)\n**After hours**: P0 only (WhatsApp ring tone for Andon alerts)\n\n**Escalation path**:\n1. WhatsApp alert → Jaime ACKs\n2. Jaime investigates (CLI + dashboard)\n3. If can't resolve in SLA → escalate to Carlos\n4. If API/infra issue → check Cloud Run logs, restart services\n5. If code issue → create foundry task for Terminal Lu\n\n---\n\n### 5. First Week Checklist for Jaime\n\n- [ ] Clone c8-platform repo\n- [ ] Set up environment variables\n- [ ] Run `c8_control_plane.py status` successfully\n- [ ] Open Foundry Dashboard, read all panels\n- [ ] Join WhatsApp War Room group\n- [ ] Respond to first test Andon alert with `ACK`\n- [ ] Approve 3 specs via CLI (`approve <id>`)\n- [ ] Read CLAUDE.md for platform context\n- [ ] Review foundry_pipeline.py to understand grading flow\n- [ ] Shadow Carlos on one SEKO demo prep call\n\n### Jaime's Cursor Setup (since he's a Cursor geek)\n```json\n// .cursor/settings.json\n{\n  \"python.defaultInterpreterPath\": \"/usr/bin/python3\",\n  \"python.analysis.extraPaths\": [\"c8_platform\"],\n  \"editor.formatOnSave\": true,\n  \"terminal.integrated.env.osx\": {\n    \"PYTHONPATH\": \"${workspaceFolder}/c8_platform\"\n  }\n}\n```"
}