Neuro-Features and state machines - Neuro Developer Documentation

A Neuro-Feature is a contract-related digital feature that an application can retrieve together with its attributes and event history. A related state machine can make allowed lifecycle states and transitions explicit.

Relationship model

Approved creation template
        ↓
Creation contract
        ↓
Neuro-Feature identifier
        ├── attributes and description
        ├── current owner or holder data exposed by the API
        ├── current state
        └── notes and event history

The exact creation and transfer sequence must come from a verified template and supported Neuron build. The existence of read operations does not prove that a guessed combination of contract and token operations will mint or transfer a feature.

State-machine reasoning

For each stateful workflow, document:

Question	Application requirement
What is the current state?	Read it from the documented operation or event
Which transitions are allowed?	Follow the approved contract/state-machine definition
Who can trigger a transition?	Check identity, party, role, and privilege requirements
Is the transition synchronous?	Handle accepted, pending, final, and failed outcomes as documented
What evidence remains?	Retain the feature/contract identifier and retrieve its event history

Available documentation

The token guide covers inspection. No generic tutorial currently covers creation, state transitions, or ownership transfer; obtain those procedures from the target Neuron’s operator.

Reference