Every Agent Gets Its Own Pane

Every Agent Gets Its Own Pane An architecture diagram generated by Archify. Thomas · resident router · HERDR WORKSPACE Thomas resident router ticket:TRA-139 · Builder · HERDR WORKSPACE ticket:TRA-139 Builder ticket:TRA-142 · Builder · HERDR WORKSPACE ticket:TRA-142 Builder spec:TRA-87 · Shaper · HERDR WORKSPACE spec:TRA-87 Shaper qa:TRA-125 · QA · HERDR WORKSPACE qa:TRA-125 QA rin:TRA-125 · Rin · HERDR WORKSPACE rin:TRA-125 Rin dispatch dispatch dispatch dispatch-qa review HERDR WORKSPACE Legend Frontend Backend Security External

One Hub, Several Panes

  • • Thomas is resident — the only role still here when a session ends
  • • Every dispatch opens its own terminal pane and its own git worktree
  • • The tracker, not the pane, is what all five spokes share

Same Weight, No Dominant Spoke

  • • Two Builders, a Shaper, a QA walk, and a Rin gate can run at the same moment
  • • No single spoke dominates — several agents, same moment, no collision
  • • Each spoke's branch and worktree are its own, never shared

Cleanup Is Thomas's

  • • A Builder commits, pushes, then returns to Thomas
  • • Thomas verifies the diff and decides the merge
  • • Cleanup of a worktree, branch, and pane is his, not the Builder's