← Work

The Fleet · 2025 — Present

A household of minds.

Building with AI as a discipline — not a shortcut, not a gimmick.

Architect · Principal · Director

Three machines. A shared coordination layer. A written covenant between the human and every AI that touches his work. This is not about using AI tools — it's about running a distributed creative system with actual operating laws, each earned from a real incident.

Machines
Storm · Shadow · Echo
Laws
16 operating
Memory files
238 on him

The setup

Storm (Windows), Shadow (a Mac), Echo (a Mac mini) — coordinating through relay, a shared brain that lives on every machine. Two different AI models run on the same box with a written treaty: one repo, one owner, no collisions. Most people have a laptop and a chatbot. This is a household.

The method

He thinks for days before handing off work. The brief arrives complete — not a sketch to iterate on in front of him. The fleet builds, verifies, ships, and reports back. No solo grinding while other machines sit idle. No reporting progress on the new thing while the old thing still has open ends.

The laws

Sixteen operating laws, each earned from a real incident. Do not make waste. Never delete, only rename. No mystery buttons. Push, don't force. Security jumps the queue. These aren't preferences — they're scars, formatted into rules so the fleet doesn't repeat the same mistakes twice.

The covenant

He wrote an actual working agreement — eight points, one per day of the week plus grace. You own your output. Disagree now or walk. We assume good intent and give each other room to mess up. It's the thing that makes all the other rules survivable.

Full story

How it actually works.

The laws, the covenant, the incidents — a scroll-driven account of what running a distributed AI system looks like in practice.

Read the story →
Systems designAI directionFleet coordinationProduct

Next case

TalkCircles.io

Small-group conversation, built on real human rhythm.