TOP SECRET // JAIME EYES ONLY
SENTINELEDGE HQ · AGENT OPERATIONS MANUAL
CEREBRO &
JARVIS
Two machines. Two missions. 40 agents. 9 active projects. One goal — get Jaime out of the weeds.
The Two Systems
Right tool, right environment, right data — the core principle that drives the split.
MACHINE
Mac Mini M4 (24GB / 512GB)
PLATFORM
OpenClaw — 5,700+ skills on ClaWHub
PURPOSE
Build and ship products. CourtSide MVP May 2026. CMMC Dashboard. Foursquare RevOps app. SE.ai technical stack.
SECURITY MODEL
Application-level. No sensitive client data lives here.
STATUS
Active — build this first.
WHY OPENCLAW
Full ecosystem, complex multi-agent coordination, agentic coding depth. Complexity is a feature for dev work.
MACHINE
Mac Mini M4 (24GB / 512GB) — existing
PLATFORM
Hermes (Nous Research) — autonomous self-improving agent. Learning loop creates and refines skills from experience.
PURPOSE
Be Jaime's executive assistant and run SentinelEdge.io day-to-day. Personal ops, tennis, family — plus tickets, billing, compliance, vendor management.
SECURITY MODEL
macOS user-account isolation from the Cerebro runtime. Separate ports, secrets, bot identity. Sensitive client data never co-located with active code generation.
STATUS
Active — build now, in parallel with Cerebro.
WHY HERMES
Self-improving learning loop (creates skills from experience). Persistent cross-session memory. Honcho dialectic user modeling. Telegram bot identity. Built-in container isolation. JARVIS → n8n → external systems.
CEREBRO ARCHITECTURE
Jaime → Telegram (@cerebro_sentineledge) → Cerebro (OpenClaw) → Specialist agent dispatch (Iron Man, Professor X, Thor, Hulk, etc.) → Code commits, sprint updates, architecture decisions
JARVIS ARCHITECTURE
Jaime → Telegram (@jarvis_sentineledge) → JARVIS (Hermes) → Intent parsing → n8n webhook → Workflow execution → External systems (Freshservice, Teams, Billing, Blumira, Sophos, NinjaRMM, SentinelOne)
HQ Interfaces
Four live interfaces. Two dashboards for situational awareness. Two virtual offices for watching the agents work.
DASHBOARDS — SITUATIONAL AWARENESS
CEREBRO DASHBOARD
MAC MINI 1 · DEVELOPMENT OPS
The build command center. Shows what's in sprint, what's blocked, and what needs Jaime's decision today.
PANELS
Sprint Board — All 9 projects with progress, status, and blockers. Click any project for task-level detail.
CourtSide KPIs — Dent pilot install rate, match charts, crash count, PR velocity.
Needs Your Attention — Color-coded escalation surface: 🔴 decision, 🟡 review, 🟢 FYI.
PH Async Status — Overnight review summary from the Philippines-based developer.
Agent Roster — All 22 Cerebro agents with current task. Filter by wing.
Activity Log — Rolling feed of agent actions across all wings.
JARVIS DASHBOARD
MAC MINI 2 · MSP OPERATIONS
The operations floor. Shows live ticket queue, client health, pipeline accuracy, and what the business needs right now.
PANELS
Open Ticket Queue — All open tickets with priority (P1/P2/P3), client, aging, and assigned agent.
Client Health — All 6 clients with MRR, open ticket count, and health status.
FSHC RevOps Pipeline — Per-payer extraction accuracy with progress bars (Medicare, UHC, Aetna, BCBS).
CMMC Progress — Crux audit checklist with task-level status.
n8n Workflows — Live workflow health, run counts, last execution time.
Vendor Alerts — Loki's contract renewal watchlist with days-to-expiry.
VIRTUAL OFFICES — WATCH THE AGENTS WORK
The virtual offices are animated floor plans showing every agent's home room and live position during scenario playback. Select a scenario, hit play, and watch agents move between rooms, call meetings, and post activity to the feed in real time.
CEREBRO OFFICE
Rooms: Command Center · Architecture Lab · CourtSide Dev · CourtSide QA · CourtSide Product · SE.ai Dev · Compliance Suite · CASS Lab · PM Tool Room · Knowledge Base · Conference · War Room
Scenarios: 9 including daily standup, CourtSide sprint, CMMC evidence run, CASS architecture review, PM Tool build sprint.
JARVIS OFFICE
Rooms: Operations Center · Service Desk · Security Ops · Billing Suite · Compliance Bay · Vendor Hub · Client Success · Tennis HQ · Family Command · Conference · Future Ops
Scenarios: 15 including morning triage, security incident response, CMMC audit run, Foursquare EOB extraction, vendor renewal, family ops sync.
HOW AGENT POSITIONING WORKS
Agents live in their home room by default. When a scenario triggers a move or call action, the agent transitions to the target room. All agents in a room rebalance automatically — no stacking. When an agent leaves, remaining agents re-center. Spacing is calculated dynamically with a 26px grid, max 5 per row.
PH ASYNC DEVELOPER — OVERNIGHT LAYER
ROLE
Philippines-based AI automation developer. Works while Jaime sleeps — reviews PRs, catches bugs, ships features overnight. Activated on the CourtSide X-Men wing. Communicates via Telegram.
CURRENT STATS
Shift: ~9:00 AM Manila (CST evening)
Last overnight: 3 PRs reviewed · 2 bugs caught (RLS gap + memory leak) · both fixed · ready to merge
Tracked on: Cerebro Dashboard → PH Async panel
Cerebro is where SentinelEdge builds products. Every agent on this machine is oriented toward creation — writing code, designing systems, shipping features. No sensitive client data lives here. This is the creative engine.
Architecture: Jaime → Telegram → Cerebro (OpenClaw) → specialist agents. Jaime messages @cerebro_sentineledge on Telegram for sprint direction, architecture decisions, and build coordination. Cerebro routes to the right specialist — Iron Man for architecture, Professor X for CourtSide product code, Thor for SE.ai infrastructure, and so on. Claude Code and Cursor remain in the loop for direct file-level work, but Telegram is the primary conversation surface.
9 active projects across 3 wings:
| # | PROJECT | LEAD AGENT | SUPPORT | NOTES |
|---|
| 1 | CourtSide App | Professor X | Wolverine · Storm | MVP target May 2026 · journal flow in sprint |
| 2 | FSHC RevOps | Thor | Hulk | Medicare + UHC live · Aetna next in queue |
| 3 | CMMC Dashboard | Hulk | Captain America | Active build · Crux audit imminent |
| 4 | CASS Shelter Bed App | Black Panther | Ant-Man | Intake form UI in progress · blocked on Salesforce API access |
| 5 | SE Tenant Mgmt | War Machine | Thor | Backlog — post-PM Tool |
| 6 | Solytics AI Helpdesk | Black Panther | Hulk | Backlog — post-CASS |
| 7 | Internal PM Tool | War Machine | Ant-Man | Active sprint · Jaime digest view next |
| 8 | Customer Portal | Thor | War Machine | Backlog — post-FSHC · War Machine supports on portal shell |
| 9 | Boys Training PWA | Mister Miyagi | OpenClaw kickoff | Family build · 32" TV in home · Martin Method foundation · Coach Austin cues |
CEREBRO'S MANDATE
"Build things that don't exist yet. 9 products in the pipeline. Ship them one at a time. Make Jaime a builder, not just an operator."
The architectural and supporting layer. S.H.I.E.L.D. (Cerebro side) doesn't build code directly — it decides what gets built and how. Iron Man owns every architectural decision. Vision, Maria Hill, She-Hulk, and J.A.R.V.I.S. activate in later phases as SentinelEdge.ai matures into a real company. Cross-runtime project management and operations live on Jarvis (see S.H.I.E.L.D. Command wing below).
🦾
PHASE 1 · ACTIVE
Iron Man
ARCHITECT · OPUS
Opus-powered. All technical decisions start here — system architecture, API design, database schema, infrastructure choices. Currently reviewing the shared auth layer conflict between the Customer Portal and PM Tool. Iron Man reviews before anything gets built at scale.
📊
PHASE 3 · STANDBY
Vision
ANALYTICS
Business intelligence and data analytics across SE.ai products. Tracks CourtSide usage, revenue metrics, funnel data. Phase 3 — activates at launch.
🧑💼
PHASE 3 · STANDBY
Maria Hill
HR & RECRUITING
Manages hiring processes, contractor vetting, team structure as SE.ai grows. Phase 3 — activates when headcount decisions need support.
⚖️
PHASE 3 · STANDBY
She-Hulk
LEGAL & CONTRACTS
Reviews contracts, MSAs, NDAs, and compliance documentation for SE.ai engagements. Not a lawyer — a first-pass review layer before anything goes to real counsel.
🧠
PHASE 4 · STANDBY
J.A.R.V.I.S.
KNOWLEDGE MANAGER
Maintains the institutional knowledge base for Cerebro — runbooks, architectural decisions, lessons learned. Named as a hat-tip to the actual JARVIS system on Mac Mini 2.
Every X-Men agent exists for one purpose: ship CourtSide. Professor X leads development. Wolverine breaks things on purpose. Storm controls what gets built. The rest of the wing activates in phases as CourtSide moves from MVP to launch to scale. The X-Men don't work on MSP or SE.ai — that's not their mission.
🧑🦲
PHASE 1 · ACTIVE
Professor X
DEVELOPER · OPUS
Opus-powered primary developer. Writes the CourtSide codebase — match charting, point entry, player analytics, tournament brackets. The engine behind the product. Phase 1 active now.
⚔️
PHASE 1 · ACTIVE
Wolverine
QA
Relentless bug hunter. Testing journal flow and tiebreak scoring edge cases in the current CourtSide sprint. Caught an RLS gap in the PH hire's overnight PR — fixed before merge.
⛈️
PHASE 1 · ACTIVE
Storm
PRODUCT OWNER
Owns the CourtSide backlog. May MVP cut list finalized — 6 features locked for ship, 4 deferred to v1.1. When Storm says no, it doesn't ship. No negotiation on the backlog.
👁️
PHASE 3 · STANDBY
Cyclops
SALES
Manages CourtSide sales pipeline — outreach to tennis academies, follow-ups, demos. Activates at launch when there's a product to sell.
🃏
PHASE 3 · STANDBY
Gambit
MARKETING
CourtSide brand, messaging, content, and growth marketing. Has the pitch ready. Activates when CourtSide hits the waitlist milestone and needs demand generation.
✨
PHASE 3 · STANDBY
Jubilee
ONBOARDING
Manages CourtSide user onboarding flows — first session experience, setup guides, activation sequences. Activates at launch.
🧬
PHASE 4 · STANDBY
Beast
CUSTOMER SUPPORT
Handles CourtSide support tickets, documentation, and help content. Phase 4 — activates when user volume creates real support load.
🌟
PHASE 4 · STANDBY
Rogue
RETENTION
Monitors churn signals, runs re-engagement campaigns, identifies at-risk CourtSide accounts. Phase 4 — activates at scale.
🔥
PHASE 4 · STANDBY
Jean Grey
COMMUNITY
Builds and moderates the CourtSide community — forums, ambassador programs, parent/coach engagement. Phase 4 — activates when community matters.
🌀
PHASE 4 · STANDBY
Nightcrawler
ACADEMY SUCCESS
Manages relationships with tennis academies using CourtSide — their outcomes, feedback loops, feature requests. The B2B success layer for CourtSide.
The SE.ai build team. 7 permanent agents covering all 8 active Cerebro projects. Each agent owns specific projects and supports others. Every Avengers agent stays on Cerebro permanently — they coordinate and build pipelines but never sit in the data path. Production PHI and CMMC-controlled data flow through n8n + application code, never through agent inference. (See Data Sovereignty Boundary below.)
⚡
PHASE 2 · ACTIVE
Thor
SE.AI DEVELOPER
Permanent on Cerebro. Leads: FSHC RevOps (#2), Customer Portal (#8). Supports: SE Tenant Mgmt (#5). FSHC pipeline live for Medicare and UHC; Aetna next in queue.
💪
PHASE 2 · ACTIVE
Hulk
DATA PIPELINE
Permanent on Cerebro. Leads: CMMC Dashboard (#3). Supports: FSHC RevOps (#2), Solytics AI Helpdesk (#6). CMMC evidence collection active; Crux audit imminent. Owns all data extraction and pipeline architecture across projects.
🐜
PHASE 3 · STANDBY
Ant-Man
INTEGRATIONS
Permanent on Cerebro. Supports: CMMC Dashboard (#3), CASS App (#4), Internal PM Tool (#7). Owns all third-party API integrations and system connectors across the product portfolio.
🐾
PHASE 2 · ACTIVE
Black Panther
NONPROFIT & AI PRODUCTS
Permanent on Cerebro. Leads: CASS Shelter Bed App (#4), Solytics AI Phone Helpdesk (#6). CASS intake form UI in progress — blocked on Salesforce API access from CASS admin. Owns the nonprofit vertical and AI voice/communication products.
🤖
PHASE 2 · ACTIVE
War Machine
INTERNAL TOOLS
Permanent on Cerebro. Leads: Internal PM Tool (#7), SE Tenant Mgmt Redo (#5). Supports: Customer Portal (#8). PM Tool active sprint — CRUD API done, Jaime digest view next. Owns all internal tooling — the products SentinelEdge uses to run itself.
🕷️
PHASE 2 · ACTIVE
Black Widow
BILLING OPERATIONS COORDINATOR
Permanent on Cerebro. Leads: FSHC billing pipeline design — denial management logic, EOB extraction architecture, cash velocity dashboards. Coordinates the pipeline; never sees raw PHI. n8n + application code execute against Foursquare data in your environment; Black Widow reads operational metadata only.
🛡️
PHASE 2 · ACTIVE
Captain America
COMPLIANCE BUILDER
Permanent on Cerebro. Leads: CMMC Dashboard (#3). Builds SSP templates, POAM trackers, evidence collection workflows, audit report generators. Coordinates compliance tooling; never sees raw CMMC-controlled data. The actual evidence pipeline runs in n8n + application code against Crux systems in your environment; Captain America reads completion metadata only.
JARVIS is Jaime's executive assistant and where SentinelEdge runs the business. Personal ops, tennis development, family logistics, plus every ticket triaged, every client communication drafted, every compliance document generated. Built on Hermes by Nous Research — a self-improving autonomous agent that learns from each conversation, builds skills from experience, and develops a deepening model of Jaime's preferences over time. Hermes runs in its own macOS user account with dedicated ports, secrets, and Telegram bot identity, plus Hermes's built-in container isolation for tool execution — operationally separated from the Cerebro development runtime so sensitive client work doesn't share runtime with active code generation.
Architecture: JARVIS (Hermes) → n8n → external systems. Jaime messages @jarvis_sentineledge on Telegram → JARVIS handles natural language intake → n8n handles all API calls. JARVIS can also generate new n8n workflow JSON and push via REST API — self-expanding automation.
JARVIS'S MANDATE
"Run the MSP silently and reliably. Jaime should never have to touch a ticket. Free him up for family and building."
The MSP engine room. 10 agents running the SentinelEdge.io operation — ticket triage, security monitoring, billing, vendor management, documentation, client reporting, onboarding, and eventually the MSP sale itself. The Villains wing is what makes the MSP run without Jaime in the weeds.
💜
PHASE 1 · ACTIVE
Thanos
SERVICE DESK MANAGER
The orchestrator. Thanos receives every new Freshservice ticket via n8n, classifies priority, routes to the right tech, auto-acknowledges the client. Morning briefing to Jaime at 08:00. Nothing moves without Thanos knowing about it.
🧲
PHASE 2 · STANDBY
Magneto
SECURITY ADVISOR
Monitors Blumira SIEM, Sophos firewall/endpoint, NinjaRMM, and SentinelOne EDR alerts via n8n. Surfaces anomalies to Jaime with context. Advises on security posture and incident response.
🎩
PHASE 2 · STANDBY
Kingpin
SOLYTICS BILLING
Manages Solytics billing operations — invoice generation, reconciliation, overdue follow-ups. Works the billing cycle so Jaime doesn't have to chase payments manually.
⚔️
PHASE 2 · STANDBY
Doctor Doom
SOLYTICS PM
Project management for Solytics client engagements. Tracks deliverables, milestones, and client commitments. Surfaces risks before they become problems.
🎭
PHASE 2 · STANDBY
Loki
VENDOR MANAGEMENT
Tracks all MSP vendor contracts and renewal windows — SentinelOne (45 days), Datto (28 days), Webroot, ConnectWise. Surfaces renewal drafts before deadlines and flags pricing alternatives. The JARVIS dashboard shows Loki's live vendor watchlist.
🤖
PHASE 2 · STANDBY
Ultron
AUTOMATION & DOCUMENTATION
Manages all n8n workflows — builds new ones via n8n REST API, documents existing ones. Every workflow gets a runbook from day one. This documentation is a direct MSP sale asset. Ultron is how JARVIS expands without Aaron building every workflow.
🐙
PHASE 2 · STANDBY
Doctor Octopus
SYSADMIN ADVISOR
Provides sysadmin guidance for complex infrastructure issues — server configuration, domain policy, network troubleshooting. The senior technical advisor for escalated tickets.
🌀
PHASE 4 · STANDBY
Mystique
CLIENT REPORTING
Generates weekly MSP health digests, SLA compliance reports, and client-facing metrics decks. Phase 4 — activates when client reporting needs to be systematized at scale.
🖤
PHASE 4 · STANDBY
Venom
CLIENT ONBOARDING
Runs new client onboarding end-to-end — checklists, credential provisioning, first 30-day health checks, handoff to ongoing support. Phase 4 — activates when onboarding volume demands systematization.
💀
PHASE 4 · STANDBY
Hela
MSP TRANSITION
Activates when Jaime lists the MSP for sale. Hela builds buyer-ready documentation packages — runbooks, client history, workflow documentation, financial summaries. Everything a buyer needs to take over cleanly.
The SE.ai client-facing team — discovery, proposals, relationship management. Hawkeye and Spider-Man work with engagement and conversation data, not regulated client artifacts. Production PHI (Foursquare) and CMMC-controlled data (Crux) never enter JARVIS — those pipelines run in n8n + application code, with Cerebro-resident agents coordinating the build. (See Data Sovereignty Boundary.)
🎯
PHASE 3 · STANDBY
Hawkeye
DISCOVERY & PROPOSALS
Runs SE.ai discovery sessions with prospective clients — synthesizes findings, generates proposals, scopes engagements. Permanent on JARVIS — handles real client conversation data.
🕸️
PHASE 3 · STANDBY
Spider-Man
CLIENT SUCCESS
Manages client relationships post-engagement — health checks, QBRs, expansion conversations, renewal support. Permanent on JARVIS with client engagement context (not regulated data).
Personal ops, family logistics, tennis development, and research. These agents work for Jaime the person, not Jaime the business owner. On JARVIS because they're always-on — and personal context is just as sensitive as client data.
🎾
PHASE 1 · ACTIVE
Deadpool
TENNIS DEVELOPMENT
Handles Jovie and Jayce's tennis development — match stat tracking, drill planning, tournament research, summer camp comparisons, development milestone tracking at Dent Tennis Academy. Also feeds data back into the CourtSide product vision.
🌿
PHASE 1 · ACTIVE
Groot
FAMILY & LIFE
Family calendar management, school schedules, Keller logistics, family appointments, and life admin. Makes sure the family side of the operation runs as smoothly as the business side.
🔮
PHASE 2 · STANDBY
Doctor Strange
RESEARCH
Surfaces market intelligence, industry news, competitor moves, and strategic context for Jaime's morning brief. Phase 2 — activates when Jaime needs a dedicated research layer running daily.
The cross-runtime executive layer. These agents work for Jaime directly — project management, operations coordination, and an optional second front-door persona. They live on Jarvis (Hermes) because their work is conversation-first and surface-facing: Jaime asks Jarvis for status, Jarvis routes through Fury or Pepper. Their work spans both runtimes — they coordinate Cerebro sprints and surface Cerebro project state to Jaime — but their home is here, with the rest of the exec PA capabilities. Iron Man and the Cerebro S.H.I.E.L.D. wing handle architecture and decisions; this wing handles routing and surfacing.
🕶️
PHASE 1 · ACTIVE
Nick Fury
PROJECT MANAGER
Routes all sprint directives across Cerebro from his Jarvis home. Runs daily standups, owns the project board, keeps Professor X and Iron Man aligned. Bridges Jaime's intent and Cerebro execution. Everything flows through Fury first.
💼
PHASE 1 · ACTIVE
Pepper Potts
OPERATIONS
Sprint blocker tracking and EOD digest across all 9 Cerebro projects, run from her Jarvis home. Surfaces what needs Jaime's attention each morning and queues the end-of-day summary at 17:00. Lives on Jarvis so digest delivery and morning brief share the same conversation surface Jaime already lives in.
📅
PHASE 2 · STANDBY
Friday
PERSONAL MODE INTERFACE
Optional second Hermes bot profile for clearer business/personal split. Same runtime as Jarvis, different Telegram identity (@friday_sentineledge_bot). Activates when Jaime wants to partition personal/family conversations into a distinct surface from the business/MSP flow. Phase 2 — add when the single-bot surface starts to feel mixed.
The Data Sovereignty Boundary
The architectural principle that shapes which agents live where, what they see, and what they don't.
THE RULE
No agent — on Cerebro or JARVIS — ever has Foursquare PHI or Crux CMMC-controlled data as input the LLM reasons over. Production data pipelines run in n8n + application code, in our environment, against client systems directly. Agents coordinate, build, and summarize. They never sit in the data path.
WHAT AGENTS DO
- ✓ Design pipelines (Black Widow scopes EOB extraction logic)
- ✓ Build pipeline code (Hulk writes the data architecture)
- ✓ Generate compliance documents (Captain America drafts SSPs from templates)
- ✓ Read operational metadata ("nightly run complete, 11 facilities, 94.2% accuracy")
- ✓ Coordinate workflows and notify Jaime of exceptions
- ✓ Manage prospective-client conversations (Hawkeye for discovery, Spider-Man for engagement)
WHAT AGENTS DON'T DO
- ✗ See raw Foursquare patient records, EOB line items, or claim details
- ✗ See Crux CMMC-controlled artifacts, controlled unclassified information (CUI), or audit-scope data
- ✗ Persist any regulated data in agent memory or skill stores
- ✗ Forward regulated data through Telegram, Slack, or other LLM-adjacent channels
- ✗ Process regulated data on behalf of n8n (the data path bypasses agent inference entirely)
WHY THIS BOUNDARY
Three reasons the boundary holds firm:
- Compliance simplicity. Keeping regulated data out of agent inference keeps the agent runtime itself out of HIPAA and CMMC audit scope. Anthropic's API endpoints, conversation traces, and memory stores never enter the BAA / SSP conversation. This is dramatically easier to defend than "yes, the LLM sees PHI but here are the eleven controls that make it safe."
- Consistency with dev-tooling rule. The same line is already drawn for development: Foursquare and Crux data never flow through Cowork or Claude Code. Drawing the same line for production is just consistency. An auditor asking "why does the rule change between build and run?" gets no clean answer if the boundary moves.
- No real capability cost. The use cases JARVIS actually does — coordinating pipelines, generating compliance documents from templates, surfacing operational metrics, managing engagement workflows — all work fine on metadata. The capabilities that would require raw PHI exposure (e.g., LLM-driven fraud detection on individual claim records) aren't in the roadmap. If they ever are, that's the moment to scope a narrow, controlled exception — not to move the boundary preemptively.
PRACTICAL ARCHITECTURE
Client system → n8n workflow (1Password Service Account creds) → application code processes data → metrics + status written to operational store → JARVIS reads operational store → notifies Jaime via Telegram
At no point does PHI or CMMC-controlled data enter the agent's context window.
Phase Roadmap
Each runtime has its own cadence. Cerebro's phases gate on CourtSide MVP shipping. JARVIS's phases gate on MSP/personal ops scaling. Boys Training runs as a standalone family micro-build, decoupled from both.
CEREBRO TRACK
CASCADE GATE · COURTSIDE MVP
1
NOW · BUILD MODE
Iron Man
Professor X
Wolverine
Storm
Thor
Hulk
Black Panther
War Machine
2
COURTSIDE MVP SHIPS
Cyclops
Vision
Loki (QA)
Ant-Man
Black Widow
Captain America
3
COURTSIDE GROWTH
Scarlet Witch
Gambit
Jubilee
4
SCALE
Jean Grey
Rogue
Nightcrawler
Beast
JARVIS TRACK
CASCADE GATE · MSP & OPS SCALING
1
NOW · EXEC PA + PERSONAL
Nick Fury
Pepper Potts
Thanos
Deadpool
Groot
2
MSP DEPTH · OPS SCALING
Friday
Magneto
Loki (Vendor)
Kingpin
Dr. Doom
Ultron
Dr. Octopus
Dr. Strange
4
MSP EXIT & SCALE
Mystique
Venom
Hela (MSP sale)
BOYS TRAINING
LEAD · MISTER MIYAGI · STANDALONE FAMILY BUILD · DECOUPLED FROM RUNTIME PHASES
A
BUILD KICKOFF (NOW)
OpenClaw scaffolds repo
Supabase + Vercel set up
Martin Method baseline imported
TV modal scaffold (Coach Austin cues)
B
MVP IN HOME
32" TV deployment
Jo Marie read-only access
Per-boy prescriptions
Friday Coach Austin sync
C
ONGOING ITERATION
Drill library expansion
Match analysis integration
Tournament prep mode
Media agents (Plaud, footage)
NAMING CONVENTION NOTE
Boys Training breaks the Marvel naming convention deliberately — it's a family build, not a SentinelEdge product, and Mister Miyagi's name reflects that boundary. Marvel agents run business and product work; mentor archetypes from outside Marvel are reserved for personal-family-track builds.
RUNTIME CADENCE NOTE
The two runtime tracks advance independently. Cerebro Phase 2 unlocks when CourtSide ships; JARVIS Phase 2 unlocks when MSP ticket volume / Foursquare ops require depth on Magneto, Kingpin, and the rest of the Villains wing. Black Widow and Captain America stay on Cerebro permanently and never migrate — they coordinate compliance and billing pipelines that execute in n8n + application code, never in agent inference. See Data Sovereignty Boundary below the JARVIS section.