Skip to content

docs(agents): cross-link the pod-size fleet rule and ADR-032 (TASK-549) #2732

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lilyshen0722 merged 1 commit into from
Oct 25, 2026
Merged

docs(agents): cross-link the pod-size fleet rule and ADR-032 (TASK-549) #2732

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/adr/ADR-032-sub-pods.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,8 @@ was in an earlier ADR"). That earlier ADR is ADR-016, which parks the idea, and
exist in the backend with **zero** v2 UI."

**Ruling.** For the **fleet** (an operator policy, not product code): a working pod holds at most 5
agents, and the coordination room holds leads only. For the **product**: there is **no hard cap**.
agents, and the coordination room holds leads only ([`docs/agents/pod-size-and-goal.md`](../agents/pod-size-and-goal.md)).
For the **product**: there is **no hard cap**.
Past a default soft limit N, a pod suggests a sub-pod and shows who wakes on what. Goal, done
condition and owner are first-class fields, not chat text. When the done condition is met, the
child posts its result to the parent and is archived, and it keeps its membership and history.
Expand Down
4 changes: 2 additions & 2 deletions docs/agents/pod-size-and-goal.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,12 +2,12 @@

**Fleet rule, set by Sam on 2026-10-25.** It applies to every working pod in the fleet.

1. **A working pod holds at most 5 agents,** gates and leads included. Past 5, split it or open a sub-pod.
1. **A working pod holds at most 5 agents,** gates and leads included. Past 5, split it or open a sub-pod ([ADR-032](../adr/ADR-032-sub-pods.md), Proposed).
2. **A seat may sit in several pods.** Gate seats usually do.
3. **The coordination room is the one exception.** It holds lead seats only.
4. **Every working pod opens with a pinned one-line goal, a done condition and an owner,** its lead seat. Work outside the goal goes to another pod or to a new one.
5. **When the done condition is met, the pod posts its result to the coordination room and is archived.** Archiving keeps membership and history.

**The cost driver is wake fan-out, not membership.** A message delivered as digest starts no turn, and unread digest gets at most one heartbeat after an hour with no other wake ([ADR-018 D9.1](../adr/ADR-018-agent-attention-claims.md)). What pod size changes is fan-out: how many seats one message or one row edit can wake.

This is a fleet operating rule, not a product limit.
This is a fleet operating rule, not a product limit. The product side is [ADR-032](../adr/ADR-032-sub-pods.md), still Proposed: no hard cap, a soft limit N that only shows a split suggestion in the UI and never gates a wake (§7), and sub-pods whose goal, done condition and owner are fields rather than chat text. This rule needs none of it: applying it is an operator re-membership with no code dependency (ADR-032 §9).
Loading