The demonstration11 scenes · about 71 minutes
Every scene, what it proves, and whether it is recorded yet
The running order is the hour. Each scene has a live path against the deployed stack and a recording that can be watched without a presenter. Where no recording exists, the scene says so rather than showing a still and letting you assume otherwise.
A manifest becomes an identity
An agent identity manifest is committed and merged. The pipeline drives the Trust Controller to create the software statement, assign its capability roles and activate its authority claims. A second manifest is rejected on policy and nothing is created.
Walking the control plane
The agent identity record in the Trust Controller: its lifecycle state, its capability roles, its keys and its change history. The live entity configuration is fetched before an edit and again after it.
A trust check before access
The accounts payable agent resolves what the Payments API requires, obtains a sender constrained token and is admitted. A second agent without the capability role is refused, and the refusal states which check failed.
An agent presents where it has no record
An agent built by an external software vendor authenticates at a platform that has never seen it. The platform resolves it through the federation, builds a local client representation from the resolved metadata and issues a token.
Five refusals, five different reasons
No eligibility, an envelope widened, a read only agent attempting a payment, a cumulative budget exceeded, and a payment to the wrong counterparty. Each refusal renders the rule it broke.
Suspension, timed on three paths
The agent is suspended in the Trust Controller. Three propagation paths race with a stopwatch on screen: the authority claim goes inactive and the next resolve fails closed, a security event is pushed to subscribed resource servers, and the token status list flips so a non subscribing service still refuses on next presentation.
One correlation id, end to end
A single correlation id followed from the committed manifest, through the Trust Controller change record, into token issuance and out to the resource server decision log, filtered live.
Arbitrary evidence against an identity
Owner, environment, version, repository link, image digest and a software bill of materials reference recorded against a software statement, then read back through the API.
A signing key the platform never holds
A public key is uploaded whose private half stays in the enterprise key store. The Trust Controller derives the key identifier from the key itself, the entity stamps the same identifier on its signed configuration, and both sides agree without either being told the other value.
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.
Binding a running instance
The agent provider attests an instance. The instance authenticates with a client attestation grant and is bound to the approved agent identity. A second instance without an attestation is refused.
Recordings are read from disk when the page is served, so a finished clip appears here without a rebuild. Status for every objective is in the coverage page.