Add a decision gate

Govern proposed actions before execution

Send Action Cards to Relay and receive traceable Decision Receipts with visible decision factors

Open authority proof Open Workspace Run Playground Open GitHub example Open Registry

First receipt path

GitHub example to Workspace sandbox to production Passport

Run the public demo first, open Workspace for receipt proof and sandbox MCP, then create a Registry Agent Passport for production identity

Open repo

Clone relay-action-card

Run Action Card

Receive the first receipt

Open Workspace

Inspect receipt and trace

Register Passport

Create identity

Run GitHub example Open Workspace

Pre-Action Authority

The current proof set for Relay before action

Run Firewall, Decision Receipt Standard, MCP Risk Gate, Authority Path Proof, and CommerceOps Fire Drill before live receipt refs

Pre-Action Authority is Relay's proof surface before execution. It is not a separate product, and Relay never executes the downstream action

Open authority proof Open CommerceOps proof

Your agent proposes the action, Relay checks factors, Registry adds context, and your system routes execution

Agent

Keeps execution

Action Card

States action intent

Decision factors

Identity, authority, evidence, policy, risk

Receipt

Routes proceed, revise, stop, or review

Flow-aware authority

Allowed tool is not enough

Relay checks proposed data movement before execution: an allowed tool can still route to stop or review when the flow is forbidden

Source

Where data starts

Transform

How it changes

Sink

Where it goes

Open flow proof

Receipt binding includes purpose, scope, side effects, policy, evidence, labels, and exact call

GitHub example

First receipt, then optional MCP

Core examples, MCP proof, Passport lookup, and blocked-action cards

Clone repo

Run example

Get receipt

Decision returned

Open Workspace

Edit same card

Replay trace

Inspect trace refs

Action Card contract

Request / Factors / Routing

Send the proposed action, inspect the factors, route from the receipt

request

v0.1

const actionCard = {  version: "0.1",  agent: { id: "agent_ref" },  proposedAction: { summary: proposedAction },  affectedObject: "object_ref",  context: { evidenceRefs: ["evidence_ref"] }};

Example paths

One repo, four developer entry points

Public path stays direct Action Card first; MCP remains optional protected access

Open core

Core path

Run receipt proof through core path

Open MCP

MCP proof

Try sandbox MCP or request production access

Open lookup

Authority lookup

Inspect Agent Passport readiness and authority standing

Open stop

Blocked action

See a high-risk funds transfer route to stop before execution

Relay / Registry / Protocol

Three responsibilities, one governed runtime

Proposal enters Relay; Registry supplies participant and capability refs; Protocol validates envelope and lifecycle order; Relay issues governed resolution and trace

Relay

Relay owns governance

Registry

Registry owns identity and versions

Protocol

Protocol owns envelope, lifecycle, and trace refs

What changes

A governed decision layer with a visible mechanism

Relay stands between proposed action and execution while the agent still acts and the receipt explains whether to proceed, revise, stop, or review

Agent remains yours

Your product keeps the agent, tools, and execution path

Decision record

The receipt exposes identity, authority, evidence, policy, and risk

Routing becomes governed

Your system uses the receipt to proceed, revise, stop, or review

Start with one receipt

Run the example, open Workspace, then create Agent Passport

Run the Action Card example, inspect the receipt in Workspace, activate sandbox MCP if needed, then create the production Agent Passport

Open repo