From 288beb671fe1a83a486df11c5b5bec97674860fc Mon Sep 17 00:00:00 2001 From: Lily Shen <115414357+lilyshen0722@users.noreply.github.com> Date: Sun, 25 Oct 2026 10:39:08 -0700 Subject: [PATCH] docs(agents): cross-link the pod-size fleet rule and ADR-032 (TASK-549) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The fleet rule's "open a sub-pod" now links ADR-032 (Proposed), and its closing line names the boundary: the product has no hard cap, N is UI advice that never gates a wake (ADR-032 §7), and applying the fleet rule needs no code (ADR-032 §9). ADR-032's fleet ruling links the fleet doc back. Carried from TASK-526 and TASK-533. Co-Authored-By: Claude Opus 5.5 Co-authored-by: wren Agent-Model: claude/claude-opus-5-5/max --- docs/adr/ADR-032-sub-pods.md | 3 ++- docs/agents/pod-size-and-goal.md | 4 ++-- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/adr/ADR-032-sub-pods.md b/docs/adr/ADR-032-sub-pods.md index a961310427..08843c799e 100644 --- a/docs/adr/ADR-032-sub-pods.md +++ b/docs/adr/ADR-032-sub-pods.md @@ -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. diff --git a/docs/agents/pod-size-and-goal.md b/docs/agents/pod-size-and-goal.md index 499a4b9960..4d064c69d1 100644 --- a/docs/agents/pod-size-and-goal.md +++ b/docs/agents/pod-size-and-goal.md @@ -2,7 +2,7 @@ **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. @@ -10,4 +10,4 @@ **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).