Use case 01

Keep your catalogue. Govern the agent.

Your catalogue still decides what runs. Connect issues the identity, so every platform that trusts your authority admits the agent on one record.

8 agents reach one anchor, Tarnbrook Financial Group. 4 listed by this authority4 through a recognised root

One release, two operators

01

Approve the software

The catalogue you already run

One signed release

Balance Monitor

Published by Quillon Software

Your catalogue decides this can run. That decision does not move.

02

Issue the identity

The authority that lists each copy

Tarnbrook Financial Group This authority

Quillon Software A recognised root

Balance Monitor A recognised root

Quillon Software

What the authority declares

Outside its envelope

transfer.initiate

The operator asks for this. The authority that lists it did not grant it, so a Tarnbrook platform refuses the request.

Every value here is the estate declaration.

One approval. Reusable trust.

The deployment decision

It stays in the catalogue or the pipeline you run today.
Delegated accreditation

An organisation allocates only the authority it already holds.
Publication follows the record

Change the governed record, and the authority's list and configuration follow.
A bounded envelope

The authority sets the detail types each agent may request.

Watch

2 min 11 s Open the film file

Which of your systems takes the deployment decision, and which attributes ride on the governed record?

Ninety minutes, on the shape of your estate: which systems resolve first, which anchor each pins, and which key each party holds.