The view from the ProdOps pit wall

This began as a companion to Mike Gilpin's piece on the context layer: the governed store of what is true, who owns it, and what happens when it changes. His case is that the context layer is a project before it is a product, and that the project is mostly human. He is right, and it is the part vendor demos skip. But a foundation is for something. Here is what it is for.

In 2015 you could service and keep a personal-use car on track from a laptop. The whole car's telemetry fit on one screen, and one person could read it by hand. The work moved slowly enough to watch.

In 2026 it does not move at that speed anymore. Agents build in an afternoon what used to take a quarter, and the moment building got cheap, production, the thing that used to gate everything, stopped being the constraint. Speed became a habit anyone installs overnight. Once everyone has it, speed stops being the edge. What stays scarce is the part speed cannot supply: deciding what is worth building, and knowing whether it works.

So you do what a Formula 1 racing team does when the car outpaces any human driving it blind. You build a pit wall.

The claim

The machine multiplied around the person; the person is still the one thing that did not.

The pit wall is one live surface across the whole operation: the strategy, the design, the engineering pipeline, and the go-to-market stack, read together. A racing team does not watch telemetry to admire it. They watch it to decide, mid-race, where the next lap of effort goes. The wall reads the whole thing and writes the next move, so a person can pour more into what is landing and pull back from what is not while the work is still in motion.

Agents sit at that wall now, some for the strategy read and others for the operations read, each watching a bank of screens no person could hold at once. But the wall does not make the call. One human does. The machine multiplied around the person; the person is still the one thing that did not.

That is the whole picture, and it fits in two frames. One screen and one reader, then a wall of screens and the same reader, with agents alongside. The count of humans making the call did not change. What multiplied was the machine.

When the platform can ship almost anything, strategy is deciding what is worth shipping, and operations is making each ship teach the next. Those are not two departments trading memos across a table. They are one motion, read off one surface. Strategy sets the direction; operations read the result. At racing speed, they are the same lap. The pit wall is the one place they meet, which is why the role that owns it is one role, not two.

Instrument all of this and you can measure everything, which is its own trap. The number that matters is not how much you shipped, because shipping got cheap for everyone. It is whether what you shipped moved something real. Did it land? Shipping is the baseline now. Landing is the read. A team that ships twice as much and cannot say whether any of it mattered is just faster at guessing, and the pit wall exists to make that answer visible before the next bet.

A pit wall is only as good as the data feeding it. Instrument the whole operation on a foundation that has no owner, no audit, and no way to ripple a change to everywhere it touches, and you have not built judgment. You have built a faster way to double down on the wrong thing. That is Mike's point, reached from the other side. He is looking at the foundation and saying it is human work that takes a quarter. I am looking at what stands on top of it and saying the same thing: the governance is not housekeeping. It is the precondition for the judgment.

The context layer is a project before it is a product. The pit wall is what the project is for. And the job at the wall, the one thing that did not get cheap, is the call.

First published on LinkedIn on 23 July 2026, as a companion to Mike Gilpin's piece on the context layer.