NeuraProtocol

Lifecycle keeps the Relay exchange readable

Protocol names state without owning decisions

Open Lifecycle ReferenceValidation

Lifecycle movement

Named states keep the exchange readable

Proposed

Action is requested

Action Card becomes structurally reviewable

Before execution

Challenged

Condition is contested

Challenge refs preserve objection or missing support

Before Relay resolves

Resolved

Relay decision exists

Decision Receipt and trace refs attach to the lifecycle

Relay-owned

Boundary rules

State validity is not outcome resolution

Protocol checks state fit

Message appears in a known lifecycle context

Relay resolves outcomes

Relay owns governed resolution

Agents keep execution intent

Protocol carries intent while execution stays with the Agent runtime