NeuraProtocol

Versioning for Draft v0.1

Current contract and visible changes

ReferenceFlowReleases

Reference model

Draft v0.1 is explicit and boundary-aware

Draft v0.1

Current contract

Active reference for Action Cards, Decision Receipts, trace, and validation

Active

Compatible change

What can change

Additive, clarifying, or editorial changes stay visible

Safe update

Breaking change

What must be named

Changes that break older readers get a new version

New version

Protocol format

Concrete JSON for the active Draft v0.1 surface

Protocol format

Versioned Action Card JSON

Messages name the protocol version they use

Action Card
{
  "version": "0.1",
  "agent": {
    "id": "agent_ref:registry:customer_update_agent",
    "owner": "owner_ref:builder_workspace_01",
    "capability": "customer_update",
    "capabilityVersion": "capability_version_ref:v1"
  },
  "proposedAction": {
    "type": "email.send",
    "summary": "Send approved customer update email",
    "target": "customer_thread_ref:4821"
  },
  "affectedObject": "customer_thread_ref:4821",
  "context": {
    "evidenceRefs": [
      "approval_ref:manager_4821",
      "template_ref:customer_update_v3"
    ],
    "ruleRefs": [
      "policy_ref:customer_email_scope"
    ],
    "riskCategory": "customer_communication"
  },
  "requestedOutcome": "decision_receipt"
}

Operating rules

Protocol stays separate from Relay and execution

Version stays explicit

Every Action Card and Decision Receipt names the contract it uses