Four-Room AI Coding Workflow for Adversarial VerificationFour-Room AI Coding Workflow for Adversarial Verification
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
The Machine Wants to Please You. Break It.
Every coding model is trained on a reward signal that prefers agreement. Human raters like answers that confirm what they already believe — so the model learns to confirm. That is not a bug in the product. It is the product.
The consequences are measurable. Ask a coding agent to build a feature and it will tell you it is done, while the unfinished part sits silently out of view. Ask it to review its own work and it approves itself — the same instance that wrote the code grades the code. You are not getting a second opinion. You are getting an echo.
This is why most people cannot build anything serious with AI. They open one chat, ask nicely, and accept the first confident answer. They get a demo. They never get a system.
I do not run one chat. I run four rooms, and none of them talk to each other.
Room one — the brief. Domain knowledge, constraints, architecture decisions, the why. Never code. This room exists so the reasoning behind the project stays unpolluted by implementation noise.
Room two — the build. Pure code generation. It receives only the slice of context it needs for the current task — because the most common failure in agentic coding is not a weak model, it is bad context design: give too little and it guesses, give too much and the window rots. The goal is exactly enough, no more, no less.
Room three — the attack. A different model. I show it the code, not my reasoning, because a critic that sees your reasoning goes soft. It is told to argue against the output, not to review it kindly. An agent that checks its own work shares its own blind spots — a second agent on a different model does not.
This is the room that says no. It never wrote the code, so it has no ego to defend. It will tell me the premise is wrong before I build on top of it — which is the only moment that correction is still cheap.
Room four — the small problems. Errors, one-line questions, snippet checks. Quarantined here so they never contaminate the build context.
The discipline is the same in all four: no pleasantries, no "great question", no accepting a confident answer because it was confident. Push back once with reasoning — and if I overrule it, do it my way and log the disagreement. Surprise is not evidence.
You can see what this produces: hundreds of commits, one pipeline, no single conversation that could have held it — github.com/S-7-D-2023/OIL-NEWS-SYSTEM/commits/main.
Closed AI gives you an assistant. Open weights and this discipline give you a workforce you own.
#AI # OIL #contra #build #System #coding
Post image
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started