One loop. Distributed across people.
In Solo, the discipline is temporal separation: you wear three hats on different days. In a team it becomes organizational, distributed across humans. That gives you something the solopreneur never has (a real second pair of eyes), but it opens new failure modes. HALO for teams keeps the loop legible while you distribute it.
02 · Diagnosis
The failure modes that appear with more than one human
Diffusion of ownership
“I thought you were verifying it.” When everyone watches, no one watches.
Boundary drift across people
What one dev lets the agent do, another forbids. The Human-Only / Agent-Capable line blurs.
Inconsistent agent governance
Everyone wires up their Workers their own way, with no shared kill-switch or audit.
Coordination that eats your speed
You grow in headcount but Signal-to-Ship drops instead of rising.
01 · The shift
From hats-by-day to one shared loop
In HALO Solo the discipline is temporal separation: you wear three hats on different days. In a team, that separation becomes organizational, distributed across people. The goal is unchanged: keep one legible loop even when many hands touch it.
03 · The boundary, multiplied
One human owner per domain, not a committee
The Human-Only / Agent-Capable line needs a clear owner in each domain (Build, Sell, Support…). Not a committee that dilutes the call: one person who owns where the line sits and is accountable for it.
04 · The three hats, distributed
Real cross-human verification: finally not judge and jury
Loop Owner, Builder and Verifier stop rotating in one head and move to different people. The team's big advantage: the Verifier is someone other than the Builder. It's the only honest way to make the Verifier Honesty Score mean anything.
05 · Team cadence
The same ceremonies, now shared
The weekly Loop Sync becomes a team ritual, and the Worker Audit (the Wednesday one) becomes a rotating responsibility: someone samples agent actions every week. Cadence is what stops agents from drifting in silence.
06 · Metrics become team metrics
Team Signal-to-Ship, Boundary Breach Count = 0
The same six metrics, read together. Signal-to-Ship stops being individual. And Boundary Breach Count = 0 becomes critical: with more agents and more hands, every boundary crossing triggers an immediate redesign.
When you're several squads, the loop federates.
Federated loops
Each squad runs its loop; a central one governs them.
Central GOVERN domain
The meta-domain that watches the rest and aggregates metrics.
AI Act, security and audit
Compliance as a first-class citizen, not a patch.
Templates and kill-switch per squad
Autonomy without losing control: each squad inherits the limits.
08 · What never changes
You learn HALO once. It grows with you.
- The Signal → Execution → Verification loop
- The Assistant / Worker distinction
- The Human-Only / Agent-Capable boundary
- “Output is cheap. Outcome is rare.”
- A <60s kill-switch on every Worker
Where is your team right now?
Start with the Diagnosis and I'll tell you which HALO edition fits and where to start.