Use case 03 Deployment evidence The two envelopes, read from the authority's statements
Same software. Many environments.
One signed release runs in your estate and on the publisher's platform. Each copy runs as an agent of its own, and your authority sets each agent's envelope.
One release, and the governed identity it has in each environment
One signed release
Balance Monitor 2.4.0
Published by Quillon Software
- Signed once
- declared artefact digest sha256:9c1f…9887
- One release record
-
Your own infrastructure
Operated by Tarnbrook Financial Group
- Governed identity
- Balance Monitor at Tarnbrook
- Listed by
- The Tarnbrook authority, directly
Its envelope
value- records.read
- records.annotate Added
- review.submit
- transfer.status Dropped
-
The publisher's platform
Operated by Quillon Software
- Governed identity
- Balance Monitor at Quillon
- Listed by
- Quillon's root, recognised by the Tarnbrook authority
Its envelope
subset_of- records.read
- transfer.status
- transfer.initiate Dropped
Same everywhere
- One signed release record
- The same record digest in both
- balance-monitor 2.4.0
Different by environment
- Governed identity
- Operator
- The superior that lists it
- The policy operator
- Envelope
-
One signed release
Both agents name the same release record.
-
An agent per operator
Each agent has its own superior and its own key.
-
Your authority sets each envelope
It sets one outright and cuts the other at the hop.
-
Recognise the publisher once
The ceiling sits on the root, so it applies to every agent the root lists.
Watch
Same software, different authority
Which supplier's software runs in both your estate and theirs, and who operates each copy?
Ninety minutes, on the shape of your estate: which systems resolve first, which anchor each pins, and which key each party holds.