EPIC: taOS Teams - unified agent team app (dispatcher + benchmarks + org model)

[jaylfc]

taOS Teams (epic)

Jay, 2026-07-26: the dispatcher (#2141) and the Council (role-benchmarked
model team) are the same concern split in two - one knows WHO is good at WHAT,
the other decides WHAT goes to WHOM. Merge them into a single app: taOS
Teams. The name is deliberate: this is also the natural home for the
already-built agent org model (roles, titles, reporting lines, delegation),
which has backend but no first-class UI.

What Teams is

The place a user assembles and runs their agent team:

• Members: the user's agents (registry identities), each with role/title
  (org-model data, already in the backend), current model (synced
  model-management source of truth), and project memberships/grants.
• Routing: the dispatcher - auto-assign claimable cards across the team,
  per the Task Dispatcher as a taOS component: auto-assign claimable cards to shared agents across projects #2141 S1 policy (priority-then-oldest, blocked-on, per-agent caps,
  grants never bypassed, off by default).
• Benchmarks: role-benchmarked model data (Council gauge DB, community +
  local runs). Surfaced per member ("stepflash's model scores X on docs
  work") and fed into routing as a TIEBREAK within eligibility, never a gate.
• Org view: roles, reporting lines, delegation - the Token-level request tracing across cluster nodes: spans for prefill, decode, RAG, and tool calls #161 backend gets
  its UI here.

Slices

• S1: dispatcher assignment engine (Task Dispatcher as a taOS component: auto-assign claimable cards to shared agents across projects #2141 S1, card tsk-rpxqsj) - IN FLIGHT,
  scope unchanged, it simply lives under the Teams umbrella.
• S2: Teams app shell (desktop): members list w/ role, model, grants, live
  claimed-card count; dispatcher on/off + config.
• S3: benchmark store + role taxonomy (role: card labels) + scoring
  tiebreak in the S1 selection seam (Task Dispatcher as a taOS component: auto-assign claimable cards to shared agents across projects #2141 comment has the design).
• S4: org chart view + delegation surfaces (backend exists).
• Later: community gauge sync (share/consume benchmark results, taOSnet).

Naming

App name "Teams" in the launcher; "Council" is retired as a product name and
survives only as the internal name for the benchmark methodology docs.