A multi-agent fleet: one config hub, one comms hub

A multi-agent fleet: one config hub, one comms hub An architecture diagram generated by Archify. 3 git remotes · multi-writer · Architecture component · the config hub 3 git remotes multi-writer the config hub clones + ~/.claude · shared by 6 seats · main workstation: six seats, one ~/.claude clones + ~/.claude shared by 6 seats clone + ~/.claude · own pull · always-on linux box clone + ~/.claude own pull clone + ~/.claude · own pull · laptop clone + ~/.claude own pull clone + ~/.claude · own pull · GPU box A clone + ~/.claude own pull show-pipeline seat · production work · main workstation: six seats, one ~/.claude show-pipeline seat production work finance seat · bids and vendors · main workstation: six seats, one ~/.claude finance seat bids and vendors reel seat · edit and delivery · main workstation: six seats, one ~/.claude reel seat edit and delivery sync seat · repo + context sync · main workstation: six seats, one ~/.claude sync seat repo + context sync workshop seat · mounts both stores · main workstation: six seats, one ~/.claude · relay workshop seat mounts both stores relay render-farm seat · farm control · main workstation: six seats, one ~/.claude render-farm seat farm control always-on seat · coordination · always-on linux box always-on seat coordination cron agent · the clock · always-on linux box cron agent the clock laptop seat · outreach · laptop laptop seat outreach gen-video seat · panels + shots · GPU box A gen-video seat panels + shots big-GPU seat · NO repo access · GPU box B: no spoke to the config hub · no spoke big-GPU seat NO repo access no spoke fleet channel · one outbox per seat · Architecture component · the comms hub fleet channel one outbox per seat the comms hub company channel · on the company store · Architecture component company channel on the company store project channel · in the project tree · Architecture component project channel in the project tree ff-only pull, own clone every seat reads the mirror writes 1, reads all cron heartbeat its only surface its only surface the relay hop monitors there too main workstation: six seats, one ~/.claude always-on linux box laptop GPU box A GPU box B: no spoke to the config hub Legend Backend Cloud Security Message bus

One hub in

  • • Every connected box pulls its OWN clone, ff-only
  • • Four spokes leave the config hub, not one
  • • One GPU box has no spoke at all: no repo access, by design
  • • The cron agent has no clone; it reads the mirror another box pulls

Per box, then per seat

  • • ~/.claude is ONE file set per box, read by every seat on it
  • • Its 5 @import lines resolve to that box's SHARED clone
  • • WS-14 is drawn exploded; the same two steps happen on each spoke
  • • The clone, cursor and hook are the per-seat half

One hub out

  • • Every participant writes ONE outbox and monitors ALL of them
  • • One box cannot see the fleet channel, another cannot see the company store
  • • So those two have no shared surface at all
  • • One seat mounts both, which makes it the only relay in the fleet