Who is doing what across our agent teams, and what is stuck?

lab build · Oct 2026 How do people and many agents work together without chaos?

When several people and their AI agents work across many repos, nobody can say who holds what, or what is stuck, without asking around. ade-tower reads what the work already leaves behind and puts it in one view. Every ticket board, from every repo, lands on one board, project by project. Each open item shows whose court it is in: waiting for review, blocked, stalled, late or not started. A timeline is drawn from the dated notes in each ticket, so nothing is typed twice. One person's cockpit shows what they hold and what moved in their projects. Below the work sits what actually ran: commits, deploys and agent sessions, read from git and the ops log, with who, what and when for every event. A deploy that reported success on a stale model is flagged, not trusted. Agents roll up to the person who runs them, and events that no identity resolves stay "unresolved" instead of being guessed. Then you can ask the tower, for example who is holding the ball right now. The answer comes from this record, with each step of the chain traced to the ticket note it comes from.

ade-tower · oversee

What it does not show

ade-tower has no public release yet. This is a lab build with local sign-in.
The team, people, repos and tickets are invented. No real board, repo or tenant is on screen.
Agents' work reaches the tower only through what they write: commits, the ops log, tickets and session journals.
Drift, topology and the live messages between sessions are not shown. Drift and topology need a project layout that the invented estate does not have.
The Ask answer is a real model answer over the invented record. The video shows its short answer and its chain, not every line.

Transcript

0:00 Who is doing what across our agent teams, and what is stuck?
0:05 The work — Every ticket board, in one view
0:10 Tickets from every repo on one board, project by project
0:16 Whose court each open item is in: review, blocked, stalled, late, not started
0:26 A timeline drawn from the dated notes in each ticket, nothing typed twice
0:32 One person's cockpit: what Grace holds, and what moved in her projects
0:38 What actually ran — Commits, deploys and agent sessions, read from git
0:41 Events, deploys and sessions per repo, read from git and the ops log
0:46 Every event: who, what, when — people, their agents, their sessions
0:54 A deploy that said ok on a stale model is flagged, not trusted
1:01 Agents roll up to the person who runs them; the rest is shown as unresolved
1:07 Ask the tower — Answers from this record, gaps included
1:10 “Grace holds the ball: one review is gating two other items”
1:15 Each step of the chain traced to the ticket note it comes from
1:20 Read-only · one view over many repos — the work stays where it is done
1:20 ade-tower · lab build, no public release yet · work and delivery modules · AI voice · synthetic data · recorded 2026-10-18

ade-tower lab build, no public release yet (work and delivery modules, run locally over an invented team estate) · AI voice · synthetic data · recorded 2026-10-18