The subordinate model position

Between 2023 and 2025, capability timelines that had been measured in decades collapsed to single digits, and the price of frontier intelligence fell by orders of magnitude. Both trends have one strategic implication for anyone building on top of the models: whatever advantage lives in the model itself is a depreciating asset you do not own. A product that is a thin surface over one lab’s engine inherits that lab’s roadmap, that lab’s pricing, and that lab’s outages as its own, and its differentiation shrinks with every release that makes the engines more alike.

So the question is where, above the commodity layer, a durable position exists. The answer this corpus argues for is the consent runtime: the layer that holds a person’s context under structural guarantees, domain locks, typed consent, quarantined outputs, real revocation, and feeds frontier models only what a task requires, only for the task’s duration. In that architecture the model is subordinate. It executes against minimized context it does not retain, through an interface it does not define, and it is interchangeable by construction, because nothing about the person’s trust attaches to it. Swap the engine and the guarantees hold, which means the trust was never the engine’s to lose.

What makes the position defensible rather than merely nice is who cannot take it. The frontier labs are structurally unlikely to build consent friction, because every element of it, context minimization, outputs that cannot be retained, revocation that actually deletes, taxes exactly what their business rewards: more context, more retention, more coupling between the user and the model. This is counter-positioning in the strict sense. The incumbent sees the position, understands the position, and cannot occupy it without defecting from its own economics, the same bind that kept active managers from copying the index fund for decades.

The move follows for any builder handling human context. Keep the model subordinate. Own the runtime, encode the guarantees structurally so they survive your own growth pressure, and treat every frontier engine as a vendor of a collapsing-price input. The models will keep getting better, which under this architecture is purely good news, since the layer people trust was never the layer that changed.