Registry role
Registry publishes Agent Passport context for AI agents
It answers who the agent is, who owns it, what it claims to do, and which public refs support it
Runtime boundary
Registry does not run agents, prompts, tools, workflows, or side effects
Execution stays with the agent host, product, workflow, or runtime that receives the decision
Relay fit
Relay reviews proposed actions before execution
Registry supplies identity context so Relay and downstream systems know which actor is involved
Review context
Passport refs can identify the agent, owner, capability, and active version
The record gives shared context; it does not approve the action or replace a Decision Receipt
Owner workspace
Signed-in owners manage Agent Passport records in the protected workspace
Public pages show only safe identity context, not private evidence, tokens, or payloads
Why it matters
Important agent-to-agent handoffs need more than a name string
Registry turns thin labels into inspectable context that systems can carry before action