What is recorded, and who can read it?

The pool records what it decided, what it was asked to do, and what it was running when it did it, and the operator reads all of it. The record of every decision Substrate serves, every site task Agency Studio runs, every attestation a node makes before joining the Grid, and every signed update a node loads lives on the operator's hardware inside the operator's network. Who reads it is a matter for the site's own named roles. Element 31 is not one of them and has no path to the record.

What the record contains

Three layers are recorded. The first is decisions: what the pool served to which robot, and when. Substrate includes evaluation and the record as part of the serving system, so a decision is not a transient answer that vanishes once the robot acts on it.

The second is tasks. Agency Studio authors site tasks with bounds, zones, speeds, distances, and stops, versions them, and has them approved by named roles before they run. Every run is recorded and replayable. A safety officer who wants to know why a humanoid moved through a particular zone can replay the task that sent it there and see the bounds it was given and who approved them.

The third is the node itself. Each Czar attests what it is running before it joins a Grid or accepts a task. The integration, sealing, and software load of every node are on record as provenance, and each signed update is recorded when it is loaded. The site can answer where its hardware came from and what it has been running from a record rather than from a reassurance.

Who reads it

The operator does, through the roles it has named. Agency Studio already requires named roles to approve tasks, and the site applies the same discipline to the record: it decides who can read decisions, who can replay tasks, and who can review attestations and updates. An automation lead, a safety officer, and an integrator under contract might each see what the site has chosen to show them.

An auditor the operator invites can read it too. The record is written to be read by someone who was not there, which is what makes it useful after the fact. It is the site's evidence, held by the site.

Element 31 does not read it. Customer appliances never connect to the Element 31 portal, so there is no channel over which the record could travel. A support session is customer-initiated, and on a sovereign site it requires the customer's attestation before an uplink window is approved and carries a hard expiry. What an engineer sees in that window is what the customer chose to show, for as long as the customer allowed.

Why it stays on site

The record is on the same list as everything else that does not leave the building, alongside camera feeds, captures, and adapted model weights. Keeping it on the operator's hardware is what makes it the operator's. There is no copy elsewhere to reconcile against, and no one outside the site who can read it without being let in.

Watchman, the integrity verification in Substrate, lets the site confirm the node is running what it attested to, so the record describes a system that is what it says it is. Who owns the models adapted on site covers the part of the record that concerns adaptation, and Does Element 31 see our data covers the support window in more detail.