Agent review stays interoperable
Shared Action Cards, Decision Receipts, trace refs, and rules
What interoperable systems need
Shared refs, lifecycle, validation, and Decision Receipts keep meaning
Action Card envelope
Parse proposed actions
Action Cards and review context stay recognizable
Readable
Lifecycle states
Place proposed actions
Named states preserve review context
Contextual
Validation rules
Check required refs
Compatible checks reject invalid Action Cards
Conformant
Traffic envelope
Connect traffic
Action Cards, Decision Receipts, approvals, and ledger refs stay linked
Auditable
Delegated Authority
Check authority
Registry authority refs bind into Relay Decision Receipts
Controlled
OTel mapping
Correlate traces
Decision Receipts map to OTel traces without payload export
Observable
Boundary clarity
Shared contract, separate authority
Shared grammar
Systems read review messages under one contract
Separate roles
Relay, Registry, Protocol, and runtimes keep distinct authority
Outcomes can differ
Compatibility makes review paths interpretable