Code-Complete Is Not Done
A grievance report sat finished but broken for four sessions — the cure wasn't more review, it was pushing the deploy.
// Build Two · beta
A pocket shop steward for a railway crew. You talk through a bad shift — tired, out of order — and it reads your account against the collective agreement, finds every violation the facts support, and drafts the grievance with the article quoted. The first field tool Workhorse helped me make.
A grievance report sat finished but broken for four sessions — the cure wasn't more review, it was pushing the deploy.
I plugged my phone in to harden my grievance app, and my own review process talked me out of shipping the big thing.
A tired railroader opens Steward asking one thing: what do I do right now? The new home screen puts the filing deadline first — and never fakes it.
Steward could only file grievances. Today it learned to answer — find the exact article, or stay honest and say it can't.
The day my build pipeline stopped running on one model, and the first thing the new three-model crew did was attack its own install.
A build day that made almost nothing you could screenshot, and why that was the whole point.
I left four AI agents to build my app's new screens while I lifted weights. Came back to working code, two caught bugs, and an app that now talks back.
I had an AI build a feature, then sent a second AI to break it. It found a bug in two minutes that every test had just passed.
Two safety-critical backend pieces, built by an AI pipeline and proven live, plus the six bugs its own reviews caught before anyone got hurt.
A tired railroader double-taps 'send' on bad signal and files the same grievance twice. Tonight I killed that bug — after the robots caught me getting it wrong.
I run trains, not software. Tonight I shipped a safety-critical feature anyway — by letting a room full of robots and my own voice tell me where I was wrong.
Four sessions stuck at the wall, then the app talked back on a real phone — and the bug it surfaced changed what I think I'm building.
I built the backend that interviews a tired railroader by voice, then let two other AIs try to break it before it shipped.
A voice app for rail workers finally ran on my phone — after it spent the afternoon insisting it had failed when it actually hadn't.
A voice app that turns a rough shift into a filed grievance just went live — after the server twice tried to ship the wrong thing.
I built the lock on the door, proved it held, and merged it. Then I told myself it was live. Half an hour of a dead server says otherwise.
Workhorse was the machine that builds. Steward is the first real tool it helped me make — a pocket shop steward for a railway crew.