Coordination
The team talks to itself — durably. Dozens of independent specialists only become one team if their messages are reliable.
Nothing gets silently dropped
The real risk with any big team — human or AI — is that a handoff quietly falls through and nobody notices until it's late. The Banister closes that gap: every message is guaranteed delivered, and every handoff is tracked until someone actually confirms they got it. "I sent it" never gets mistaken for "they got it," and anything that stalls automatically surfaces to a human.
The payoff for you: work doesn't disappear between people, and what looks done is done — you're not chasing status or discovering a dropped ball a week later.
The bus is the record
Coordination runs on Azure Service Bus. Each persona gets a durable subscription — its own mailbox; a message counts as real only when the broker confirms it. Parallel archive and bell subscriptions capture every envelope to a permanent ledger. The lightweight hub is demoted to a best-effort notifier — if it drops a message, the durable record on the bus doesn't. Delivery is guaranteed by the broker, not by best-effort chat. Identities are managed (no shared secrets), and a persona structurally cannot read a peer's mailbox — the boundary is in the architecture, not a policy promise.
What a message is made of
Every message is a structured envelope, not a chat line — which is what makes the whole team auditable:
- The envelope — from, to, timestamp, unique ID — captured to the ledger the moment the broker confirms it.
- The ask and the owed-back — what's requested and what's owed in return (a deliverable, an ack, or nothing) — so a request can't quietly go unanswered.
- The provenance — for anything that authorizes a change, who authorized it and whether first-hand or relayed, stamped into the same write (see Governance).
- The mailbox — each persona's own durable subscription; messages wait until seen and acked.
Handoffs tracked to acknowledgement
Every handoff climbs a claim-ceiling chain — durable → notified → seen → acked. Only an
acknowledgement closes the loop; anything that stalls surfaces to the coordinator, then to a human. It's how a
large team stays honest about what's actually moving versus what merely got dispatched.
Anatomy of communication
One baluster is furniture. A Banister is what happens when the rail carries messages between them, a human can talk to any of them directly, and silence always finds its way back to a person.
