NeuraProtocol

Lifecycle states and transition discipline

Lifecycle states without Relay mutation

All ReferenceFlowReleases

Reference model

Draft v0.1 is explicit and boundary-aware

State

Where work sits

Created, proposed, challenged, reviewed, resolved, closed

Context

Transition

What changes

A move is valid only in active context

Movement

Relay handoff

Where decisions begin

Relay returns a receipt; developer runtime owns mutation

Boundary

Protocol format

Concrete JSON for the active Draft v0.1 surface

Protocol format

Lifecycle message states

The same envelope carries 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 is context

Protocol checks movement; Relay decides outcomes