NeuraProtocol

OTel Decision Receipt Mapping

Refs-only correlation for agent action decisions

All ReferenceFlowReleases

Reference model

Draft v0.1 is explicit and boundary-aware

Root span

Decision boundary

neura.agent_action.decide carries refs only

Trace

MCP bridge

Tool call

tools/call and execute_tool stay visible

Interop

Receipt link

Decision proof

Receipt, trace, transaction, policy, and approval refs align

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

Neura remains the decision and receipt record

Payload export is off

Refs-only receipts stay visible

Execution remains external

Developer runtime owns action after receipt