A worked example — the designed flow
Illustrative catalog entry
One catalog of every agent you run. Troupe registers each agent with its signed manifest, its owner, and its scope — so 'what agents do we have?' always has an answer.
An agent joins the catalog with a signed manifest: what it is, who owns it, what it may touch.
The entry binds to the agent's Namesake identity and its Referee policy template — no orphan listings, no mystery agents.
Anyone on the team answers 'what agents do we run?' from one catalog: owner, scope, status, history.
New versions, scope changes, and retirements flow through the same human gates as everything else on the platform.
Troupe is in build. This is the designed run, stage by stage.
One entry, fully bound
Identity from Namesake, policy from Referee, status live — the catalog entry carries the same record the rest of the platform enforces.
Scope change requested — a widening goes to the named owner and security — the same gate as a new registration
Retirement — the agent is retired in the catalog, its identity revoked through Namesake, the record kept
Illustrative catalog entry