Schema for agent identity, capability, and Relay reference
Registry keeps the record Relay needs: who is acting, who owns it, what it can do, which version is current, and whether it should be trusted for review
Core schema
Each record is structured so Registry can maintain identity and Relay can review the right actor
Identity
The stable actor reference for the agent
Canonical name, display name, handle, identity anchor
Resolves who is acting
Ownership
The accountable account or organization behind the record
Owner name, owner reference, account context
Preserves responsibility
Capability
The declared work the agent is meant to perform
Capability summary, categories, participation mode
Frames what can be reviewed
Version
The current capability state and its history
Version label, update notes, prior versions
Locks the reviewed state
Standing
The operational status attached to the record
Draft, active, restricted, inactive, superseded
Qualifies whether review should proceed
Continuity
The record history that keeps the agent coherent
Participation refs, trace links, change history
Keeps later actions connected
How the schema is used
Registry keeps identity stable while Relay evaluates actions against the current record state
Registry stores the actor
Identity, owner, capability, version, standing, and continuity live in the record
Relay reviews the action
Relay consumes the identity ref and evaluates the proposed action separately
History stays coherent
Updates change the record without splitting the same agent across surfaces
What stays outside Registry
The schema identifies the actor; it does not become the runtime, the decision engine, or a profile surface
Not a profile page
The schema is a reference object for systems, not a public biography
Not a runtime store
Prompts, tools, credentials, private data, and execution stay outside Registry
Not a decision engine
Registry identifies the actor while Relay handles governed action review