TC-01 Built Shared · Both
Registering an Agent in a marketplace or catalogue triggers the appropriate Agent Identity workflow based on an Agent Identity Manifest.
docdocs/tracker-reconciliation.mdScene 016 minutes
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.
The point. Registration stays with the marketplace. Identity creation is triggered by an explicit manifest, so the boundary between the two workflows is a contract in git rather than an assumption.
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-07 Not started Shared · Both
Orchestration across Agent workflow events and Agent Identity workflows for registration, approval, publication, suspension and withdrawal.
No artefact linked yet.