Who owns the models adapted on site?

The operator does, and the ownership is enforced by where the work happens rather than by a clause. Adaptation on a Czar Grid means fine-tuning a model on the site's own captures, and that fine-tuning runs on the pool, inside the building, on the operator's hardware. The captures never leave to be trained on somewhere else, and the adapted weights never leave once they exist. Element 31 does not receive them, has no path to them, and has nothing to reuse elsewhere.

Where adaptation happens

A floor accumulates captures: what the cameras saw, what the robots were asked, what they did. Substrate includes adaptation as part of the serving system, so a site can fine-tune the perception or decision models on those captures, on the pool, to make them better at this floor's pallets, this plant's parts, or this terminal's light.

The pool is the only place that work happens. There is no training service on the far end of a connection, because in the air-gapped posture there is no connection and in the connected posture Local Bridge permits only the routes the site declared. A route to an outside training service is not one a site would declare, and it is not one Element 31 asks for.

What stays and what leaves

The list of what leaves the building is short: nothing. Camera feeds, captures, task records, adapted model weights, and the record of every decision stay on the operator's hardware inside the operator's network. The adapted weights are on that list by name.

That has a practical consequence for a site with something to protect. A plant's adapted perception model encodes what its parts and fixtures look like. A terminal's model encodes its layout and its traffic. Those are the site's to keep, and keeping them is not a matter of trusting a policy. It is a matter of the weights sitting on a disk in the site's own rack with no path out.

It also means Element 31 cannot pool one customer's adaptation into a model for another. Each site adapts for itself, on its own captures, and the result stays where it was made. A site that wants to carry adapted weights to a second building it owns does so on its own media, by its own decision.

What the record shows

Adaptation is not a black box on the pool. Substrate's evaluation and record cover it, so the site can see what was adapted, how it evaluated against the version before it, and when it was put into service. That record stays on the operator's hardware with everything else.

It matters when a safety officer or an auditor asks why a robot's perception changed on a given day. The answer is in the record the site holds, not in a vendor's release note. Integrity verification on the node gives the site a way to confirm that what is in service is what it approved.

The technology page covers adaptation, evaluation, and the record as parts of one serving system. What is recorded, and who can read it goes further into who on the site can see what.