The Harness-Model Flywheel: Why AI Application Companies Are Not All Depreciating
An investment newsletter argues that harness logic adding intelligence is a depreciating asset, but harnesses selling infrastructure, trust and efficiency appreciate as models improve, and proposes a five-trait test for distinguishing the two.
Every model release eats some of the intelligence that a harness used to patch in. That much is true and has been true for two years. The question Rob May poses in his November 22 newsletter is whether this means the harness business itself is dying. His answer is no, and the distinction he draws between two claims investors tend to merge is the most useful part of the argument.
The first claim is that harness logic which adds coding intelligence is a depreciating asset. May agrees. The second is that harnesses are a depreciating business. He disagrees, and his reasoning runs through what he calls the Model-Harness Flywheel. Harness engineers find where models break and patch it with code. Those patches generate usage data. Labs train on that data, and the next model no longer needs the patch. The harness discovers a skill, the model absorbs it, and the harness must move to the next frontier.
May grounds this in a hardware precedent. In 1989 Intel's 486 pulled the floating-point co-processor onto the main chip. The standalone math chip business faded, and software that leaned on fast floating point became the norm. Absorption killed one layer and fed the next. The analogy is illustrative rather than quantitatively verified, but it captures the structural point: when a capability moves from an external component into the core system, the component vendor loses revenue while the ecosystem built on top of the now-cheaper capability grows.
What makes the harness business different from the floating-point chip business, in May's framing, is that some of what harnesses provide are not skills at all. They are properties of the environment the model runs in. A model cannot train its way into being your audit log, your permissions system, or your cloud bill. Infrastructure, trust and security, and efficiency are not things that get absorbed into model weights. They are things that get more valuable as the model becomes more capable and more widely deployed, because there is more to secure, more to route, and more to optimize.