Better alone, unfair together

We say it on the front page: brilliant alone, unfair together. The first half is the promise that keeps us honest — every product has to win on its own. The second half is what happens when they stop being separate tools and start being one operation. This post is about the second half.

Each one, alone

Take any of them in isolation and it stands up:

• TheAuditor gives an agent a deterministic picture of your codebase, so it stops guessing about your code. Useful the day you install it, with nothing else in the room.
• BenchProctor tells you what a code scanner can actually find, against an answer key it can’t read off a filename. Run it against any tool — including ours.
• Warden lets agents act safely across providers without torching your context budget. Bring your own subscription; bring your own models.
• Curator remembers — ranking what it keeps by truth, not recency, and running on your own GPU.
• Arbiter dispatches, routes, and recovers long-running work, so a crash or a throttled account doesn’t lose your night’s progress.

None of that requires the others. That’s the point.

Together, unfair

Now picture one ordinary task — an agent fixing a real bug in a real repo — and let the pieces stack.

The agent doesn’t guess at the code; it reads ground truth from TheAuditor. It doesn’t start from zero; Curator hands it the history and decisions that led here. It doesn’t fumble the tools or blow the budget; Warden keeps the action tight and the facts intact. The job runs long, the machine reboots, an account hits a limit — Arbiter brings the work back and routes around the wall. And when a scanner in the loop says “this is fixed,” BenchProctor is why you can believe the verdict instead of hoping.

Every one of those is a help on its own. Composed, they remove failure modes you usually just live with — the silent wrong assumption, the forgotten decision, the wasted context window, the lost run, the unverifiable claim. That’s the unfair part: not a bigger tool, but a smaller surface for things to go wrong.

Start anywhere

There’s no required order and no bundle to swallow. Pick the layer that hurts most today; it’ll earn its place alone. The compounding is there when you want the next one — not a tax you pay up front.

That’s the whole shape of Code Reality Labs: five tools you’d choose on their own merits, built by one house to a single standard, that happen to add up to something none of them is by itself.