Films · Journey 6
How fast can you turn it off, and what exactly turns off?
Chapters 11
Transcript, read from the captions
Ralph Bragg
Hi, I'm Ralph from Raidiam. Trust has to change when the world does. Let me show you what happens when you withdraw an agent.
Every answer expires
Your own APIs and your partners' platforms act on an agent you govern. Each holds a signed answer. Every answer expires, so each consumer reads again. Then something changes. How fast can you turn it off? And what else stops when you do?
More than one source
Those answers come from more than one source. Tarnbrook's authority governs its own agents. The Aldercross scheme accredits across the sector. Raidiam Connect runs both. Other parties publish too: the catalogue, the partners, and an attester that vouches for each running instance. Every consumer chooses the entities it already trusts.
Act where the trust changed
Act where the trust changed. Stop one instance, revoke a key, withdraw an accreditation or an agent, or stop signing for a publisher. Each owner publishes its change. Everything else keeps its authority.
Tarnbrook withdraws one agent
Let me show you. Tarnbrook withdraws Analyst Companion from its own catalogue.
Three parties
The withdrawal reaches three parties. In Connect, its certificate is revoked and its record withdrawn. The catalogue takes the agent's configuration down. And the attester is told to stop any running instance.
Publication follows the record
My favourite part. In Connect, I walk Tarnbrook's trust domain and list every record. Its authority governs this agent's record, and publication follows it with no second step.
How fast
How fast? How fast depends on the layer that changed. On this estate, a consumer keeps its answer for up to five minutes, or one minute if it checks accreditation marks. A session token issued before its next read lasts up to five minutes more. So a running session ends within ten minutes.
Each consumer
Each consumer meets the change at its next read. Every chain through this agent fails its check. Everything else carries on. Want it back? Tarnbrook publishes this agent itself, so the same control restores it on a new key.
Change it where it is governed
My advice? Change it where it is governed. Every consumer that relies on it meets the change inside a window declared in advance.
Thanks for watching
Thanks for watching. I'm Ralph Bragg.
The use case
When something changes. Access adapts.
Choose what changed and read what it reaches. Five scopes, one blast radius each, and the window in which every consumer reads the change. Every bound comes from the estate declaration.
