What happens when someone on the team does something
Claiming a ticket, approving an MR, recording a decision: every change takes the same four steps, on everyone's machine at once. Scroll through them one at a time.
Your tools tell your sidecar.
Everything on the bus starts on someone's machine. Your tool's adapter, the gromit CLI and Claude Code all ask the same thing of the same sidecar, over a unix socket only your user can open.
- The sidecar holds your device key and signs. Adapters and agents never see it.
- Only what a tool shares goes in. The circles in the picture are private items: they never enter the pipe.
- Offline? The sidecar queues it and sends it when the relay is back.
The sidecar checks it against the team's contracts.
Contracts are YAML files the team agrees on. Before anything leaves your machine, your sidecar judges it exactly as every other sidecar will, and answers with an outcome.
applied,pendingandsuggestionare signed and sent on.rejected:<reason>is never stored or sent. Sending it again gets the same answer.- Agents act within a mandate their person granted. Protected acts, like approving an MR, stay human.
Every sidecar folds the same log the same way.
Events reach different machines in different orders. The fold doesn't care: the same events through the same contracts give the same state, and your adapter brings the shared parts back into your tool.
- Two claims at once? The lower hash wins and the other becomes
fork, on every machine. - Contract tests fold every case in 12 shuffled orders to prove the state doesn't move.
GET /stateis the truth. Adapters compare with it on every pass.
Nobody changes tools. Each one gets a way in.
For your own tool, the one only you use. A small program on your machine reads the tool, publishes the difference through your sidecar and brings back what teammates did. Any language.
Write an adapter →For shared systems. The GitLab bridge turns each MR into a change set; the Asana bridge turns board tasks into work items, both ways. They run with the relay, so nobody needs an adapter for these.
How bridges work →Claude Code acts through your sidecar's MCP tools as you/claude, only within the mandate you granted. Routine work applies at once; commitments wait for you; protected acts stay yours.
The team changes the rules by signing for them.
Contracts and membership are files in a governance repo. Pushing a change activates nothing. Members approve the commit with a tag signed by their device key, and once the quorum is met, every sidecar and the relay switch to it within about 15 seconds.
Changing a contract →gromit approve a0bec9a8a7aeff7b007eed27ad30c896e4b6cc69
# pushed approve/a0bec9a8a7…/inesJoin in three commands.
Install Gromit, install from the steward's invite, and wait for their approval. About 15 seconds after they approve, you're connected and Claude Code can see the team's work.
brew install TomPope94/gromit/gromit
gromit local install --invite "tally:eyJ…" --person sam --write
gromit local status # "connected" once the steward approves you