soft3/neuron/neuron specification.md

Neuron is the protocol subject with its own profile-defined identity and optional durable program execution. One named robot attaches several neurons for its keys, networks and devices. One neuron can execute multiple progs and tasks. Their data IDs and lifecycles add no second signing subject. Identity-only/watch-only use requires no running VM. The specification adopts the approved convergence decision.

MUST/MUST NOT define requirements for a profile claiming this contract. Accepted architecture does not make every runtime, proof backend, remote executor or agent feature implemented. Each profile declares the actual schemas, authority, resources, storage, evidence and failure behavior it supports. Observed results belong in audit.

Contract Defines
Foundations Cyb meanings, ownership, locality and immediate execution
Identity Native/foreign subjects, bindings, key and device changes
Model Neuron/prog/invocation records and distinct orderings
Data Canonical values, exact suites, IDs and bounded decoding
Runtime v1 Implemented multi-prog/task transitions and resource accounting
Lifecycle Program management, task cancellation and host placement
Execution Runtime/checkpoint/act/observation contracts
Authority Current host-bound grants and independent publication verification
Local authority Existing H(pubkey) and exact NSIG1 profile
Worker dispatch Existing worker selection, generations and guarded handoff
History Shared graph/BBG persistence, receipts, closure and retention
Communication Typed delivery, read/write/trade, durable cursors
Action envelope Signed native external action/receipt boundary
Evidence Observation, execution proof and network finality distinctions
Evolution Upgrade, relocation, backup and explicit forks
Migration Preserved old origins, resumable import and fencing
API, CLI Ports, operators and headless composition
Navigation Subject/prog/view/particle references without side effects
Query projection Immutable execution relations owned here, read by inf
Integration Crate DAG, owners, product and domain profiles
Agent, evaluation Full-agent requirements and measurable comparative gates
Conformance Behavioral, authority and persistence-failure checks
Legacy local runtime Retained original wire/reader compatibility

Cybergraph owns history, BBG supplies durability, and cyb Log renders it. Foculus owns signal ordering/finality; neuron runtime commits are a separate application projection over the same storage. Ward authorizes and vault manages secrets. Rune/nox execute; workers place computation. Soma owns cognition, goals and learning; progs are its execution mechanism, not a new identity hierarchy.

The old birth-based subject exists only as a legacy origin in migration records and immutable old codecs. Neither an activation particle nor a prog/checkpoint hash is a NeuronId. Existing keys, addresses, signatures, claims and historical record bytes survive convergence; unsupported continuation/evidence profiles remain inspectable and suspended rather than silently fabricated or rerun.

Folder

Graph