NeuraProtocol

Lifecycle for proposed actions

Action Cards become traceable decisions

ReferenceFlowReleases

Reference model

Draft v0.1 is explicit and boundary-aware

Action state

Where action sits

Created, proposed, reviewed, decided, traced, closed

Status

Transition

What changes

Each move keeps context and refs intact

Movement

Relay decision

Where outcome returns

Relay returns a Decision Receipt; execution stays outside Protocol

Boundary

Protocol format

Concrete JSON for the active Draft v0.1 surface

Protocol format

Lifecycle state JSON

Action Card and Decision Receipt carry state and next-state refs

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

Lifecycle preserves context

Protocol tracks movement; Relay returns decisions