Documentation

Architecture

How NeuroBlocks, stacks, the runtime, and receipts fit together as one pipeline from biology-inspired modules to verifiable execution.

Layers

Think of SynapseVM as four layers. Each has a clear job; none silently pretends to do another’s job.

  Data / provenance          NeuroBlock library
  (datasets, circuits)  ──▶  (versioned modules)
                                    │
                                    ▼
                             NeuroStack graph
                          (typed composition)
                                    │
                                    ▼
                              SynapseVM tick
                         (deterministic runtime)
                                    │
                         critical action?
                                    │
                                    ▼
                              NeuroReceipt
                         (replayable evidence)

Control plane vs evidence plane

The control plane is the tick path: sensors → neural modules → actuators. It must stay offline-capable and fast.

The evidence plane runs after a critical action: packaging a receipt, replaying it, and (optionally) consulting external indexes or anchors. Evidence never authorizes the reflex itself.

Where code lives

NeuroLab (apps/neurolab-web) — Discover, Compose, Simulate, Verify UI.
SynapseVM core (crates/) — fixed-point SNN runtime and receipt semantics.
Compiler / blocks — packaging versioned NeuroBlock artifacts.
Optional partners — registry, subgraph, consensus anchors, confidential validators; always post-action.