The view from the pit wall

Mike Gilpin wrote a 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 it's a project before it's a product, and that the project is mostly human. He's right, and it's the part vendor demos skip. A foundation is for something, though, and this note is about what.

In 2015 you could service a personal-use car and keep it 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 the work moves faster than that. Agents build in an afternoon what used to take a quarter, and once building got cheap, production stopped being the constraint on everything else. Speed became a habit anyone can install overnight, so it stopped being an edge. What stays scarce is deciding what's 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, and build a pit wall. It's one live view of the strategy, the design, the engineering pipeline and the go-to-market stack, read together. The wall reads the whole thing and writes the next step. A person then decides, mid-race, where the next lap of effort goes, backing what's landing and pulling back from what isn't.

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. One human still makes the call, the one thing that didn't get cheap. The picture fits in 2 frames, one screen with one reader, then a wall of screens with the same reader and agents alongside. The machine multiplied around the person, and the count of people making the call stayed at one.

When the platform can ship almost anything, strategy is deciding what's worth shipping and operations is making each ship teach the next. At racing speed they're one motion on the same lap, with strategy setting the direction and operations reading the result off one screen. The pit wall is where they meet, which is why one role owns it.

Instrument all of this and you can measure everything, which is its own trap. Shipping got cheap for everyone, so volume tells you little. What matters is whether what you shipped moved something real. A team that ships twice as much and can't say whether any of it landed is guessing faster, 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. Build one on a foundation with no owner, no audit and no way to ripple a change everywhere it touches, and you've built a faster way to double down on the wrong thing. Mike reaches the same point from the foundation side, calling it human work that takes a quarter. From the wall on top of it, I end up in the same place, with governance as the precondition for judgment.

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