🦞 Fleet Hub
One place to see the entire YoniClaw fleet — every claw, every human, every project. MemClaw is the source of truth; this is the read view.
Deep dives
/skills →/humans →/wiki →/projects →Fleet org chart
Claws grouped by domain. Each card: emoji · primary human · secondary · session key · live project count.
🦞Leadership· top of the fleet
🛠️Dev / Build· coding + shipping
⚙️Ops / Infra· servers, security, compliance
📈Trading / Quant· markets + signals
💎Products· client-facing apps
💬Comms / People· marketing, HR, outbound
How to use the fleet
Start here if this is your first time looking at the fleet.
1. Route work to a claw
Every claw owns a domain. To delegate work, mention the claw (e.g. InfraClaw, CommsClaw) and YoniClaw's router will spawn or reach the right session via sessions_send.
Routing matrix → /orchestration
2. Read the fleet at a glance
Scan the org chart above. Badges show how many projects each claw owns and whether humans are double-booked (conflict). Click any of the 4 deep-dive cards to drill in.
3. Data flow: MemClaw → fleet-hub
MemClaw is canonical. One daily pipeline (scripts/daily-sync.mjs, 06:00 UTC) pulls projects, humans, and wiki; regenerates the Next.js data layer; rebuilds; deploys. Drift is auto-corrected.
4. Contribute / update
Write back via memclaw_write (memories), memclaw_doc_write (structured data), or by editing repos the sync reads. Full guide → /getting-started.