Relay Production Readiness

Relay Workspace sandbox proof can happen immediately with demo identity or sandbox MCP access

Production Relay review benefits from stable Registry refs before evaluation

Create one Agent Passport for the production agent before using production Action Cards

Keep owner, capability, active version, standing, and participation complete

Action Card agent.id should reference the Registry participant or Agent Passport handle

Action Card capabilityVersion should reference the active version used for Relay review

Active standing means the record can provide Registry context, not that Relay will approve every action

Draft, restricted, or archived records should not be treated as clean production identity

Production or private MCP access still needs Registry trust context

Registry does not issue MCP tokens, public API keys, or downstream execution rights

Registry supplies identity and standing refs for Relay Agent Traffic

Relay owns traffic ledger, trace replay, Decision Receipts, approval state, and decision posture

Registry does not read Relay traffic, store private payloads, or shut agents down

Registry supplies identity, owner, scope, standing, and revocation refs for Relay-issued Delegated Authority Receipts

Relay owns Decision Receipt issuance; Protocol owns the receipt shape and validation

Registry does not issue receipts, grant execution rights, store private payloads, or create Relay acceptance

Registry review changes standing and writes audit history; Relay still owns Decision Receipts

Registry does not auto-approve agents, submit to Relay, or claim Relay acceptance on its own