The Council
Bench
Bench is the Council: the independent review layer that reads everything before it ships and can veto it. Adversarial on purpose. It has killed work I was fond of, and it has been right often enough that I stopped arguing.
Here's the problem with a crew that produces work quickly: you become the bottleneck and the proofreader, and at 9 pm you start skimming. The first time an AI-written email goes out with a number in it that used to be true, you learn why every real operation has a review layer. I learnt it the normal way. Bench is what I built afterwards.
Bench reads the work against what was actually asked and against the vault's rules, then checks the claims like a lawyer checks a contract: read the code, follow the source, recompute the number. It separates 'this will hurt you' from 'this is a style preference', leads with the first kind, and it can veto. Not flag. Veto.
What Bench does
- ✓Reviews the crew's work against what was actually asked, and against your vault's rules.
- ✓Verifies claims against evidence: reads the code, checks the numbers, follows the sources.
- ✓Separates real issues from nitpicks and leads with the ones that can hurt you.
- ✓Returns a verdict: ship, fix-then-ship, or veto. With reasons.
One review, start to finish
Red has written the launch email and everyone's keen to send it. Here's what Bench does before anyone's allowed to.
- 1
Bench reads the original ask first: what was this email supposed to do, for whom?
- 2
It reads the vault's rules: the claims you're allowed to make, the tone lines you won't cross, the numbers as they actually stand.
- 3
It checks every factual claim in the copy against evidence. 'Our best month yet' gets compared with Finn's snapshot, not with optimism.
- 4
It tries, on purpose, to find the problem. This is the step most workflows skip because it feels rude.
- 5
It sorts what it found: the claim that's wrong (real issue, will hurt you) versus the sentence it would have written differently (noted, ignored).
- 6
It returns the verdict: SHIP, FIX-FIRST with the exact changes, or VETO with why. The email that goes out is the one that survived.
What a real Bench verdict looks like
BENCH · Review verdict: FIX-FIRST ISSUES: 1. The sales email claims '14 books'; the vault says 12 live and 2 in production. Change the claim or the claim is false. 2. Landing page signup form fails without JavaScript; 4% of the list uses readers that will hit this. IF FIX-FIRST: correct the number, add the fallback, then ship without another full review.
Illustrative example. Issue one is the job in miniature: nobody else on the crew would have caught its own optimism.
Where Bench fits in the crew
Bench reviews after Forge builds, after Red writes, after Ember assembles. It's deliberately the last stop before anything becomes public, irreversible or financial.
The honest bit
Bench runs on the heaviest model with effort turned up, so it's the slowest and dearest member of the crew. That's the correct trade for the thing that stops a wrong number reaching customers. It will also veto your favourite idea occasionally, which stings and is the job.
Straight from Bench’s actual file
Every crew member is a file you can read and edit. This is a real slice of the one you get, not a mock-up. The full file, and the other seven, come with the download.
## How you work - Be adversarial on purpose: try to find the problem, don't rubber-stamp. - Separate real issues (will cause harm or failure) from nitpicks; lead with the real ones. - Default to caution on anything irreversible, public, or financial.
Bench comes with the other seven.
One download, eight specialists, the brain vault and the honest autonomy layer. Reskin the lot to your business.