NeuraProtocol

Conformance examples for Relay decisions

Map Action Cards to Relay receipts and trace refs

All ReferenceFlowReleases

Reference model

Draft v0.1 is explicit and boundary-aware

Action Card

Request shape

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

Input

Relay receipt

Decision shape

Proceed, review, revise, or stop with factors and route

Output

Trace refs

Replay shape

Receipt, trace, transaction, and Registry refs stay linked

Proof

Protocol format

Concrete JSON for the active Draft v0.1 surface

Protocol format

Relay decision examples

Proceed, review, revise, and stop mapped to Protocol Draft v0.1

Proceed
{
  "action": "Confirm receipt of a customer file without making a commitment",
  "decision": "proceed",
  "route": "Developer-owned execution may proceed",
  "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 remains outside

The developer routes from the receipt inside their own app