Summary
Fleet engineering replaces ad-hoc populations of agents with an accountable organization: registry, identity, permissions, inbox, audit trail, and sovereign control for many loops/agents running across a team.
A fleet is a governed population, not a folder of prompts. The accountability test:
Which agent did it, with what authority, against what task, evidenced by what?
Scope — the five concerns
See Five Concerns, Pattern Picker, and the Fleet Ready Score (F0–F3).
Stack position
Fleet Engineering is the top layer: many loops + agents + registry + org-wide control. It sits directly above Loop Engineering (one autonomous system: prompt/verify/state).
Companion epic: cobusgreyling/loop-engineering#442
Prerequisite
Teams without at least one stable loop pattern should start with loop-engineering before adopting fleet patterns.
Summary
Fleet engineering replaces ad-hoc populations of agents with an accountable organization: registry, identity, permissions, inbox, audit trail, and sovereign control for many loops/agents running across a team.
A fleet is a governed population, not a folder of prompts. The accountability test:
Scope — the five concerns
See Five Concerns, Pattern Picker, and the Fleet Ready Score (F0–F3).
Stack position
Fleet Engineering is the top layer: many loops + agents + registry + org-wide control. It sits directly above Loop Engineering (one autonomous system: prompt/verify/state).
Companion epic: cobusgreyling/loop-engineering#442
Prerequisite
Teams without at least one stable loop pattern should start with loop-engineering before adopting fleet patterns.