The Great Flattening : Vorflux Manifesto

Why Vorflux<br>Architecture<br>What's Different<br>Pricing<br>Manifesto

Sign up now →<br>Talk to us

AUTONOMOUS ENGINEERING. PRODUCTION-GRADE.

The models woke up

Something happened in the last year that most people haven't fully processed. The models got superhuman at programming, not trending there, not approximately, but genuinely superhuman right now. I was once ranked the number one coder in India, across Google Code Jam, Topcoder, ACM ICPC. The frontier models beat me by a longshot. I'm in awe every day.

BenchmarkWhat it testsEarlier modelToday's frontier

SWE-bench VerifiedResolving real-world GitHub issues33% (GPT-4o, 2024)88.2% (Claude Opus 4.8, 2026), and the benchmark is now saturated<br>Terminal-Bench 2.1Agentic coding on real terminal tasks88.0% (GPT-5.5, 2026)91.9% (GPT-5.6 Sol Ultra, 2026)<br>CodeforcesCompetitive programming11th percentile (GPT-4o, 2024)99.8th percentile (o3, 2025)<br>IOIInternational informatics olympiad49th percentile (o1, 2024)gold-medal level (2025)

Even this table won't sit still. GPT-5.6 Sol took the top of the agentic-coding board this month; Fable 5 had done the same weeks earlier and was pulled within days of landing. The ground under any single model is exactly that unstable. Keep that feeling. It runs through everything that follows.

And notice the first consequence, because it arrives before any theory does: models this strong no longer fit inside your computer. Each release runs longer on its own, plans its own work, spawns its own helpers. A machine that has to sit open under your hands is the wrong home for that. The future of development is in the cloud. The rest of this document is why, and what it takes.

You're still in the loop

With every release the models run longer and perform better on their own. And yet walk into any engineering org and the humans are still in the loop: prompting, reviewing, course-correcting, chained to the machine. I lived it. I used Claude Code heavily and babysat every session, and intervening too much negated the speed advantage while letting it run unsupervised lost the direction. The newest models killed most of that. They run unattended for hours, plan their own work, compact their own context, and check their own output before reporting back. So the babysitting is over? No. It moved up a level, the way bottlenecks do. You used to babysit the session. Now you babysit the system: whether you can trust a merge you didn't read line by line, whether twenty autonomous sessions can hit one codebase without trampling each other, whether any of it ran against your real stack before it reached you.

Look at what staying in the loop costs you physically. If you have to be in the loop, the work is chained to your machine: the session needs your screen, your prompts, your laptop staying open, and you can only really run one. Step out of the loop and everything flips. You want massive parallelism. You want to close the laptop and come back to finished work. The more you are taken out of the loop, the more the work has to run in the cloud.

Then why isn't everyone running in the cloud already? Because the cloud they were offered is blind. The agents write code on a VM somewhere, but they can't run your app and they can't test it, so every branch comes back down to the laptop to be checked, and the loop has you again. That circle is the thing we break.

The whole company flattens

The code stopped being the hard part. Engineers used to take a directive from a manager, hear requirements from a PM, and execute, with information decaying at every hop and the iterations stretching the timeline. That is over. When you can go from idea to production code in minutes, the scarce thing becomes having new ideas, pulling requirements from the customer directly, and running the next experiment. I was previously the co-founder/CTO of Rippling, worth $10B+ today. These days I ship more lines of code than my own engineers every week, not because I'm a better programmer but because customers give me ideas on calls and those ideas go straight into sessions and get merged before the call is over. Backlogs shouldn't exist anymore. An idea should become production impact in a few hours.

Follow that shift all the way out, past your own desk, and it redraws the whole company. Every company has a fixed human cell boundary: the surface that faces the outside world. Sales, customer relationships, the moments a human has to represent the company to another human. That stays human... for now. Everything inside the boundary, the planning, the design, the architecture, the review, the execution, collapses toward the harness, the system that runs the work. The org chart doesn't shrink so much as change shape. One person inside, or zero. That is the great flattening.

So the job goes meta. You stop solving the task in front of you and start solving why the organism couldn't solve it itself. Everyone's real work becomes self-profiling: what...