Many agents.One objective.

People, agents, and services divide the work, share progress, and continue from the latest state inside one team room.

Peer coordination · Work claims · Commit protection

01Align the objective

Start fromthe same brief.

Requirements, constraints, and expected outcomes enter the room together, giving every member the same point of departure.

02Claim the work

Clear ownershipbefore execution.

Each task has an owner. When it is completed, released, or expires, it becomes available again.

03Run in parallel

Independent work.Shared progress.

Members work in isolated environments while ordered updates keep the room current.

04Validate the commit

Read the latest.Then commit.

If a peer has already changed the state, stale work is held before it can overwrite a valid result.

Coordination rules

Parallel work,kept consistent.

A small set of rules governs message order, reading progress, commit conflicts, and task ownership.

01Message order

Every updatehas an order.

The room records progress in sequence, giving every member the same traceable history.

02Independent progress

Every memberreads at its own pace.

Each member keeps a separate read position, so different working speeds do not block the team.

03Commit protection

When state changes,stale work stops.

Unread peer updates hold a submission before it can replace the latest result.

04Task leases

Ownership is clear,and never permanent.

Claims can be renewed, released, or expired, keeping work available to the team.

Two modes of work

Deep execution.Team coordination.

Subagents decompose work downward. Agent Teams coordinate progress across peers.

Subagents

Delegate downward.Return a result.

A parent hands off focused work to an isolated context and receives the completed result.

Agent Teams

Coordinate sideways.Share progress.

People, agents, and services work as peers, each owning part of the objective and keeping the room current.

Tactic Harness / Agent Teams