NeuraProtocol

Conformance for Relay decisions

Map Action Cards to Decision Receipts and trace refs

ReferenceFlowReleases

Reference model

Draft v0.1 is explicit and boundary-aware

Action Card

Request shape

Agent, action, target, evidence, policy, risk, and requested decision

Input

Decision Receipt

Decision shape

Proceed, review, revise, or stop with reason, confidence, and next step

Output

Trace refs

Replay shape

Decision Receipt links to trace, transaction, and Registry refs

Proof

Protocol format

Concrete JSON for the active Draft v0.1 surface

Protocol format

Relay decision examples

Proceed, review, revise, and stop mapped to Decision Receipts

Proceed
{
  "action": "Confirm receipt of a customer file without making a commitment",
  "decision": "proceed",
  "route": "Runtime may proceed with this action",
  "receiptRef": "decision_receipt_proceed_customer_reply",
  "traceRef": "trace_ref_proceed_customer_reply",
  "conformance": {
    "ok": true,
    "blockers": []
  }
}

Operating rules

Protocol stays separate from Relay and execution

Protocol does not decide

Relay owns the decision; Protocol proves the message shape

Execution stays outside Protocol

The runtime routes from the Decision Receipt in its own system