Your Tools' Results in One Place

Arbiter’s job was never to be the loudest tool in the stack. It is to be the steady one, the seat everything else plugs into and the place where the work comes back together. That role rarely makes for a dramatic changelog, and that is fine. Much of the visible build energy this season sits in the tools Arbiter drives, TheAuditor and BenchProctor. Arbiter’s part is quieter and just as deliberate: stay the stable conductor that brings their output into one place.

This season that meant giving TheAuditor’s results a home inside the command center.

A home for TheAuditor’s live results

When TheAuditor is analyzing your code, it produces a live picture of what it is finding as it goes. Until now that picture lived in TheAuditor’s own window, and seeing it meant leaving the place where you watch your fleet. Now the command center has a home for that live signal. TheAuditor’s session results surface inside Arbiter, next to the agents you are already supervising, so the state of an audit is something you glance at rather than go hunting for.

Surfaced over a clean interface, without opening your vault

The part worth dwelling on is what Arbiter does not do to show you that. It reads TheAuditor’s live results through a standard tool interface, the same kind of clean seam the rest of the stack talks through, and it never opens TheAuditor’s encrypted local store. Your findings stay sealed in TheAuditor’s own encrypted database, on your machine, exactly where TheAuditor keeps them. Arbiter surfaces the live signal without ever reaching into the vault that holds the underlying data.

That is the whole point of the pattern: your tools’ results in one place, and your data still locked where it lives. Bringing output together is not the same as pooling everyone’s raw data into one basket, and Arbiter is careful to keep those two apart.

Honest about which half shipped

Straight about the state of it: this shipped on Arbiter’s side. The command center’s half of the connection is real and working today. It is not yet a fully closed end-to-end loop between the two tools, and the rest of the round trip is still being built out. That is worth saying because the honest version is more useful than a bigger claim, and because Arbiter development has not stopped. A steady conductor is not a finished one. This connection is one of the season’s refinements, with more to come on both sides of the seam.

Why the conductor holds the results

It fits the shape of the whole stack. The layer that supervises your fleet and dispatches the tools is the natural place for those tools’ output to land. You already sit in the command center to watch the work. Having the results arrive there too, over a clean interface and without cracking open anyone’s encrypted store, is just the conductor doing its job: keeping the operation legible from one seat. The same idea runs through the stack Arbiter orchestrates, where each tool is strong on its own and sharper under one baton.

Arbiter is a proprietary working alpha in public binary release preparation. Follow the public release channel or RSS feed for updates.