When the lab becomes the consultant, the only safe layer is the one the client already owns.

A $10 billion venture can hire every engineer in the room. It cannot acquire a source-cited procedure the client owned before the venture arrived.

The events of early May close most of the usual escape hatches. Access to frontier models has been commoditized across the major clouds, and delivery has been internalized by a foundation lab standing up its own $10 billion services venture. Every position that depends on standing between the client and the lab is now exposed to the lab itself. The obvious question is what is left. The answer is the one layer that exists before any delivery vehicle walks into the account.

State it plainly. It is the business-logic procedure that encodes how a client's process runs and how its automated decisions get made, recorded, and replayed. When that procedure is shipped to the client as an artifact the client owns outright, source-cited and structured for review, it is not up for grabs in the next engagement. The Deployment Company can acquire implementation muscle and forward-deployed engineers. It does not, by hiring people, acquire a procedure the client already holds and can operate on its own.

The economics follow from ownership. A client-owned procedure is model-portable: it keeps running when the model is swapped from one lab to another, when the vendor walks, and when the consultants go home. The price is fixed and known up front, because the extraction step burns no tokens and the model step that remains is bounded and priced in. That is the structural opposite of an open-ended relationship that reprices every renewal and bills the bench for the privilege.

This is precisely the layer the intermediary model never built toward, because that model depended on the client not owning it. The firms that shipped client-owned code are not competing for the engagement when the lab enters the field. They are the prior art the new entrant has to work around.