One release. A governed identity in each environment.

Their superior, their policy operator and their envelope differ.

Quillon signs that record for Balance Monitor 2.4.0, and both entity configurations name it by its digest. The record declares an artefact digest, a software bill of materials and the tools the release offers. The digests are declared rather than computed: no artefact is served at the address the record names on this estate. Read on the wire on 29 September 2026, both configurations carry the same record_digest and the same artefact. The two instances are served by different programs on this estate, and they run different tasks, so the record is what they share.

Your own infrastructure

Callum Reid stands an instance up from the Tarnbrook catalogue. The Tarnbrook authority lists that agent directly, and the agent signs with private_key_jwt on a key Tarnbrook holds. It asks for records.read, transfer.status and review.submit. Two value rows replace that ask: tarnbrook.records.reader gives it records.read and records.annotate, and tarnbrook.review.caller gives it review.submit, which lets this agent ask the Batch Reviewer to review a batch. So transfer.status is dropped and records.annotate is added. The token carries no assurance claim, because the platform admits an identity rather than an instance.

The publisher's platform

Yusuf Demir operates a second instance at Quillon, as a service. Quillon's own root lists that agent, and the Tarnbrook authority recognises that root, so the only chain from Quillon's agent to the Tarnbrook anchor passes through the recognition hop. The agent signs with private_key_jwt on a key Quillon holds, and its token carries no assurance claim either. It holds neither Tarnbrook role the other agent holds.

A value row replaces what the leaf asks for, so it can add a type as well as drop one. A subset_of row keeps only what the leaf asks for and the row allows, so it can only drop.

Quillon's agent asks for records.read, transfer.status and transfer.initiate. The row on tarnbrook.external.reader allows records.read and transfer.status. Resolved at the Tarnbrook anchor on 29 September 2026, the envelope is those two, and transfer.initiate is gone. The chain has five statements, one more than the Tarnbrook agent's four, and the extra one is the hop.

Quillon Software, the publisher. It publishes an entity configuration at its own address, so an operator reads the root there. It generates the root key and supplies the public half; the private half stays with Quillon. It signs one release record for Balance Monitor 2.4.0. It lists its own agent under that root, so the operator's authority never lists it, and it sets private_key_jwt as that agent's method.

Tarnbrook Financial Group, the operator. It recognises the publisher's root with one recognition record at the Tarnbrook authority. It sets the ceiling on that hop as a subset_of row on tarnbrook.external.reader, bounding it to records.read and transfer.status. It grants that role to Quillon's organisation. It does nothing further for a new agent under that root, because every such agent reaches the anchor through the same record. The instance Tarnbrook stands up itself it lists directly, with value rows of its own.