Open source · npx CLIs · F2 dogfood · 6 patterns · 5 stories · Essay

Govern populations
of agents with accountability

Fleet engineering is the layer above loop engineering: registry, identity, permissions, inbox, audit, economics, and sovereign control — so many loops run safely across a team.

Clone a Starter → Accountability Test Loop Engineering ↓

Which agent did it, with what authority, against what task, evidenced by what?

— The Fleet Engineering accountability test

The stack

Context → Harness → Loop → Fleet

Each layer owns a different question. Fleet engineering begins when populations need governance.

Context

What does the model see?

Harness

How does one run execute?

Loop

What keeps working over time?

Fleet

How do many systems govern together?

Interactive

Pattern picker

What hurts right now? Pick a symptom — get the pattern, starter, and command.

Patterns

Six fleet patterns

Team Agent Registry

Catalog agents with owners and lifecycle.

Start here

Shared Inbox HITL

Central approval for risky actions.

Hierarchical Delegation

Manager → workers with typed handoffs.

Agent Clone & Fork

Share agents across teams safely.

Fleet Budget Guard

Per-agent and per-team caps.

Cross-Agent Audit

Incident review across boundaries.

Primitives

Seven fleet primitives

Registry → Identity → Permissions → Inbox → Audit → Economics → Sovereign control

Get started

Five minutes to F1

npx @cobusgreyling/fleet-init ~/my-fleet --pattern team-agent-registry --with-loop daily-triage
npx @cobusgreyling/fleet-audit ~/my-fleet --suggest
npx @cobusgreyling/fleet-budget ~/my-fleet
npx @cobusgreyling/fleet-cost ~/my-fleet

Sample fleet-audit output (F1 workspace)

Fleet Readiness — ~/my-fleet
Score: 55/100  Level: F1
Assessment: Cataloged — ready for inbox and budget enforcement

Findings:
  ✓ FLEET.md present
  ✓ Registry file found
  ✓ 1 agent manifest(s)
  ✓ Permissions model documented

Pattern picker · Use minimal-fleet template · DIY walkthrough

Documentation