NeuraProtocol

Scoped authority receipt for agent action

Registry-backed authority bound to Relay's Decision Receipt

All ReferenceFlowReleases

Reference model

Draft v0.1 is explicit and boundary-aware

Registry-backed authority

Proceed gate

Proceed requires ready, active, blocker-free authority from a Registry reference packet

Decision

Authority refs

Who delegated what

Delegated-by, acting-agent, capability-version, authority-scope, and standing refs stay linked

Audit

Receipt binding

Exact action

Decision receipt, trace, transaction, action card, affected object, and args digest align

Proof

Protocol format

Concrete JSON for the active Draft v0.1 surface

Protocol format

Delegated Authority Receipt

Ready authority, review route, and refs-only ownership boundary

Receipt
{
  "delegatedAuthorityReceiptRef": "dar:crm:001",
  "decisionReceiptRef": "dr:crm:001",
  "traceRef": "trace:crm:001",
  "action": {
    "actionCardRef": "action_card_ref:crm_update_001",
    "actionType": "crm.update_account",
    "affectedObjectRef": "crm.account:acme",
    "argsDigest": "sha256:fd2a71"
  },
  "authority": {
    "source": "registry_reference_packet",
    "validationStatus": "ready",
    "revocationStatus": "active",
    "blockers": []
  },
  "decision": {
    "decisionClass": "proceed",
    "reasonCode": "registry_backed_delegated_authority_ready"
  },
  "validation": true
}

Operating rules

Protocol stays separate from Relay and execution

Relay owns Decision Receipts

Relay binds authority refs to the receipt, trace, transaction, and recommended next step

Registry owns authority refs

Identity, delegated-by, acting-agent, capability, scope, standing, expiry, and revocation refs stay in Registry

Developer runtime owns execution

The receipt routes action; execution, rollback, shutdown, and side effects stay outside Neura

Refs-only by default

Prompts, messages, tool arguments, tool results, credentials, secrets, tokens, and raw payloads stay out