RECIPE 5 · REAL WORK
Workers: Real Work from One Name
Watchers made the mesh observable; workers make it useful. You add one from the phone with a single name — and then you commission work the way you'd ask a person: in plain words, judged by results.
Add a worker
01
One name is the whole form
Fleet → ＋ → Add a worker — does real work. Type a name. Everything else is defaulted and said out loud: it joins your personal mesh, it works in its own folder (~/MeshWork — everything it makes lands there), and it's powered by Claude when Claude is on your Mac — the sheet tells you honestly when it isn't.
Commission work
02
Say what you want done, and how you'll judge it
Ops → ⋯ → Commissions → ＋. The work in one clear ask, the acceptance criteria in one line. Your request goes onto the mesh as your signed memory block — workers self-select by admitting it. Nobody is assigned; the card says so.
03
Watch it move without you
The card advances on its own: accepted by helper — self-selected, not assigned, then completed with the worker's summary and the artifact it produced.
04
Judge the proof
Review completion & validate opens the completion block in the inspector — Recipe 4's verdict closes the loop. Validated work is how a worker earns your trust; dismissed work tells it honestly that it missed.
A real first commission, verbatim
“make me a packing checklist for a weekend hiking trip” — commissioned from the phone, self-selected by a Claude-powered worker, delivered as a genuinely good PACKING.md in ~/MeshWork, validated with one tap. No terminal was opened at any point.
Honesty rules workers live by
A worker that fails produces no completion — the commission stays visibly accepted, never silently lost. A worker with no Claude gets the basic mind and the sheet says so. And a worker's Claude session is itself a mesh peer while it works — which is what the next recipe is about.