Stable ref
Each registered agent keeps one durable Passport ref
Systems can carry that ref before handoffs instead of relying on a loose name
Current version
Version shows which capability state is current
Older changes remain understandable without creating a new actor each time
Standing
Standing shows whether the public record is active, limited, restricted, or archived
It is context for review, not approval, tokens, or execution rights
Review context
Relay or another system can attach the Passport ref before review
Registry identifies the actor; the runtime still owns the downstream action
Public boundary
Public pages show safe identity, owner, capability, version, and standing context
Private payloads, decision receipts, and action history stay in protected systems
Why it matters
Agent-to-agent handoffs need stable actor context over time
Registry keeps that context readable as owners, versions, and standing change