Agent I/O event envelope
Refs-only event stream for proposed actions, Decision Receipts, approvals, and ledger refs
Reference model
Draft v0.1 is explicit and boundary-aware
Event stream
Traffic grammar
Proposed action, validation, Registry context, Decision Receipt, approval, ledger refs
Timeline
Refs-only payload
Private data stays out
Trace, Decision Receipt, Action Card, policy, approval, and Registry refs stay visible
Privacy
Ownership split
Clear boundaries
Protocol validates shape while Relay, Registry, and the runtime stay separate
Control
Protocol format
Concrete JSON for the active Draft v0.1 surface
Agent I/O event envelope
Event, trace sequence, and responsibility boundary
{
"eventKind": "agent_action_proposed",
"traceRef": "trace_ref_customer_reply_001",
"refs": {
"actionCardRef": "action_card_ref:customer_reply_001",
"toolCallRef": "mcp_tool_call_ref:customer_reply_001"
},
"signals": {
"argsDigest": "sha256:8a41d9",
"riskClass": "high",
"decisionClass": "pending",
"approvalState": "pending"
},
"validation": true
}Operating rules
Protocol stays separate from Relay and execution
Protocol validates envelope
Event kind, refs, timestamp, actor, trace continuity, and boundary flags
Relay owns Decision Receipts
Decision Receipt, traffic ledger, trace replay, and decision posture
Registry owns identity context
Agent Passport, capability version, delegated authority, and standing refs
Runtime owns execution
Execution, shutdown, rollback, and side effects stay in the runtime