Trust Controller CBA vendor demonstration

Scene 106 minutes

Changing what an agent may ask for

A capability role is changed. A downstream consumer sees the new envelope on its next resolve, with the agent identity untouched and no scope changed anywhere. The change history is shown alongside.

The point. The capability envelope is governed independently of scopes and of runtime client configuration, which is exactly what the objective asks for.

not yet recorded This scene has not been recorded yet

It runs live against the deployed stack. When the recording is made it appears here without this page being edited, because the site looks for the clip on disk each time it serves. Until then, use the live paths below.

What this scene proves

The objectives it answers, at their current status

Status is read from the tracker when this page is served. If a scene is listed against an objective that is not started, that is what it says.

TC-27 Built Raidiam · Both

Govern, version and expose an approved capability envelope for an Agent Identity, and make that capability metadata available to downstream identity, policy, entitlement and enforcement platforms.

docdocs/capability-envelope-spike.md docdocs/artefacts/tc27-subordinate-statement.jwt

See it in the tracker

All eleven scenes