NeuraProtocol

OTel maps Decision Receipts to traces

Refs-only trace correlation for agent action decisions

ReferenceFlowReleases

Reference model

Draft v0.1 is explicit and boundary-aware

Root span

Decision trace

neura.agent_action.decide carries refs only

Trace

MCP bridge

Tool call

MCP and GenAI tool calls stay visible

Interop

Receipt refs

Decision proof

Decision Receipt links to trace, transaction, policy, approval, and Registry refs

Audit

Protocol format

Concrete JSON for the active Draft v0.1 surface

Protocol format

OTel Decision Receipt mapping

Span, events, and refs-only boundary

Span
{
  "name": "neura.agent_action.decide",
  "attributes": {
    "gen_ai.operation.name": "execute_tool",
    "gen_ai.tool.call.id": "call_customer_reply_001",
    "mcp.method.name": "tools/call",
    "neura.action_card.ref": "action_card_ready_customer_reply",
    "neura.payload.tier": "refs_only",
    "neura.private_payload_stored": false,
    "neura.protocol.version_ref": "protocol_v0_1",
    "neura.receipt.id": "decision_receipt_ready_customer_reply",
    "neura.trace.ref": "trace_ref_ready_customer_reply",
    "neura.transaction.ref": "relay_txn_ready_customer_reply"
  },
  "validation": true
}

Operating rules

Protocol stays separate from Relay and execution

OTel is correlation

Relay stays the Decision Receipt record

Private payloads stay out

Trace exports refs, states, and digests only

Execution stays outside OTel

The runtime acts from the Decision Receipt in its own system