85% say code review is the new bottleneck. Here’s what the AI coding narrative leaves out.

A merge is a contract. The moment a change lands on main, every other team in the organization starts building The post 85% say code review is the new bottleneck. Here’s what the AI coding narrative leaves out. appeared first on The New Stack .

A merge is a contract. The moment a change lands on main, every other team in the organization starts building on the assumption that it works. They branch from it, deploy on top of it, and debug their own failures, believing that what came before them was sound.

Most engineering organizations have never written that contract down. They have a pipeline that runs checks, and whatever the checks cover is what the merge promises. Ask what a green checkmark on a PR actually guarantees, and you rarely get a precise answer.

“A merge is a contract. The moment a change lands on main, every other team in the organization starts building on the assumption that it works.” That vagueness used to be affordable.

Code arrived at human speed, written by people who carried its context in their heads and stayed around after merging. Both of those conditions are now gone. Coding agents are multiplying PR volume, and an increasing share of changes arrive written by something that holds no lasting context at all.

The industry has already noticed the consequence: in GitLab’s recent survey, 85% of respondents said the bottleneck has shifted from writing code to reviewing it . It is time to define the contract explicitly and then look honestly at where today’s pipelines fall short of it. The four layers of confidence Strip away tooling, and a change needs four things established about it before the rest of the organization builds on top of it.

First, it is well-formed. It compiles, passes lint and static analysis, and produces a deployable artifact. Second, it is internally correct.

Unit tests confirm the logic does what its