architecture

Architecture

A model is declared once as a TopologySpec and rendered twice — into the snnTorch module that trains and into the nir.NIRGraph that exports and validates — so the two cannot silently diverge. Every surface (CLI, WebSocket, dashboard) renders from the same payload shapes.

flowchart LR
    A["Datasets and event streams<br/>MNIST, Fashion, N-MNIST, DVS"] --> B["SpikeEncoder /<br/>EventSpikeBridge"]
    B --> C["TopologySpec<br/>single source of truth"]
    C --> D["snnTorch StageModule"]
    C --> E["nir.NIRGraph"]
    D --> F["Simulator / training<br/>one temporal loop"]
    E --> G["Independent NIR interpreter<br/>validation and drift"]
    F --> G
    E --> I["Deployment targets<br/>rewrite, quantize, backends"]
    F --> J["Energy accounting<br/>SOP / MAC / AC estimate"]
    C --> H["Model hub<br/>inspect, compat, import"]
    G --> K["Dashboard and CLI<br/>WebSocket / JSON"]
    H --> K
    I --> K
    J --> K

Loading

The same spine powers the recipes in COOKBOOK.md and the scripts in examples/.

The browser dashboard is extracted to its own repository, capsize-games/spikeforge-dashboard (ARCH-0001 Phase 2). client/ stays here for one release as a read-only mirror; the pinned dashboard bundle version is recorded in compatibility.json, and the server serves a pinned prebuilt bundle when SPIKEFORGE_DASHBOARD_DIST is set. The versioned WebSocket contract lives under protocol/ (see its README.md).

The deploy layer — deploy backends, quantization, energy accounting, and the sparse event runtime — is extracted to capsize-games/spikeforge-targets (ARCH-0001 Phase 3; distribution spikeforge-targets, import root spikeforge_targets). It depends on core (spikeforge~=0.3.5) but core never depends on it. The top-level spikeforge_targets/ package stays here as the packages/spikeforge-targets workspace distribution.

The model hub is likewise extracted to capsize-games/spikeforge-hub (ARCH-0001 Phase 4; distribution spikeforge-hub, import root spikeforge_hub), also depending on spikeforge~=0.3.5. Core itself lives at capsize-games/spikeforge; the spikeforge-server distribution (import root server) stays in that repository because its extraction trigger T4 did not fire.

Because the project was pre-1.0 and unpublished when the split landed, the extraction shipped without back-compat aliases: the old spikeforge.{targets,energy,event_runtime,hub} import paths were deleted rather than kept as shims.