How to Use the Fleet

Fleet / How to Use

1. Route work to a claw

Every claw owns a domain (Dev, Ops, Trading, Comms, Products, Leadership). To delegate work, mention the claw name in conversation with YoniClaw, or use sessions_send to reach it directly.

Routing by keyword

YoniClaw's ROUTING-ENFORCER.md scans for keywords:

proxy, server, Docker, DNS, Caddy → InfraClaw / DevopsClaw
test, Playwright, QA → QAClaw
send message, WhatsApp, email → CommsClaw
trade, DeFi, Hyperliquid → TradeClaw / TradingClaw
research, investigate, debug → spawn subagent

Direct session keys

Each claw has an OpenClaw session key (visible on the landing page org chart). Use sessions_send(sessionKey, message) to route work programmatically.

Full routing table → /orchestration

2. Read the fleet at a glance

The landing page gives you a macro view:

Org chart — claws grouped by domain, with human owners, session keys, and project counts per claw
Deep-dive cards — 4 primary routes (Skills, People, Memory Wiki, Projects)
Badges — accent = live counts; warn = ownership conflicts; prod = healthy

Every page uses the same design system (eToro dark + teal). The top nav is persistent and lets you jump between deep-dives instantly.

3. Data flow: MemClaw → fleet-hub

MemClaw is the single source of truth. Fleet-hub is a read-only view, refreshed daily at 06:00 UTC by a single pipeline (scripts/daily-sync.mjs):

What the pipeline syncs

Data	Source
Projects registry	MemClaw `fleet-projects/registry` → `public/data/registry.json`
People	MemClaw `fleet-humans/` → `data/.json`
Skills	Fleet host `/var/www/fleet-skills/` → `public/data/skills-*.json`
Wiki	`memclawz/karpathy-layer/wiki/` → `data/wiki/*.md`
Standards	MemClaw `fleet-projects/standards` → `public/data/PROJECT-STANDARDS.md`

Fallback chain

Each source tries: MemClaw API → GitHub raw → local file. First success wins. The pipeline writes data/.sync-meta.json with per-source status so you can audit drift.

4. Contribute / update content

Add a human

memclaw_doc_write to fleet-humans/humans-extra, or edit knowledge/people/team-directory.md in the workspace. The next sync picks it up.

Add a project

Create a PROJECT.md in the project repo following PROJECT-STANDARDS v1, then add it to the registry via memclaw_doc_write or a PR to yoniassia/ClawsProjects.

Add a wiki page

Write a .md file to memclawz/karpathy-layer/wiki/. The sync copies it to data/wiki/ and Next.js SSG generates the page.

Write a memory

Use memclaw_write for unstructured knowledge or memclaw_doc_write for structured records. Memories persist in MemClaw and can be searched by any claw.

5. Architecture at a glance

┌─────────┐   MemClaw API    ┌──────────────┐   SSG pages   ┌────────────────┐
  │ MemClaw │ ←── daily sync ──│  fleet-hub   │ ←── Caddy ───│ fleet.clawz.org│
  │ (Docker)│      06:00 UTC   │  (Next.js)   │               │   (public)     │
  └─────────┘                  └──────────────┘               └────────────────┘
                                  ↑ reads from
                          data/ + public/data/
                          (JSON, Markdown files)

Fleet-hub is v0.5.0. Source: yoniassia/fleet-hub. Basic auth: fleet:clawz123. Public routes: /, /humans, /getting-started.

🧭 How to Use the Fleet