Repository navigation
snn interpreter provenance
github-actions[bot] edited this page Oct 13, 2026
·
1 revision
Records the standing of the sibling snn_interpreter/ directory for
Capsize-Games/spikeforge#57. This note moves, deletes, and retires
nothing; retirement is explicitly unauthorized in the adopting pull
request.
-
spikeforge(this repository) is the canonical source for the client and the engine. All client work lands here. - The sibling
snn_interpreter/directory (same parent directory as this checkout) is retained as an unversioned mirror: it carries no.gitdirectory and is not a checkout of any branch. It is a recoverable copy of an earlier tree, not a second maintained tree. - At the time of writing the two manifests are byte-identical
(
client/package.jsononorigin/mainversus the mirror's copy), andclient/srcshares 68 identical files. The adopting pull request adds one line to the canonical manifest (the@capsizellc/commonsdependency); that is the only post-note divergence. The remaining differences are classified per file group inplans/client_diff_classification.md; nothing in the mirror is silently dropped by that classification.
- Migration in the adopting pull request: none. No path moves, no file is deleted, no consumer is repointed.
- Repointing the
999consumers named in Capsize-Games/spikeforge#57 rides its own branch and is out of scope here. This note records the requirement; it does not perform the repoint. - Rollback of the adopting pull request is a plain revert: the mirror is untouched, so there is nothing to restore.
- The mirror remains recoverable until the provenance gate is explicitly closed (the acceptance criterion in Capsize-Games/spikeforge#57). Closing that gate is a separate decision and is not taken here.
Capsize-Games/spikeforge#57 coordinates with Capsize-Games/hq#5, #24,
#30, #34, and #35. Follow-ups (further shared-package adoptions, the
999 repoint, any retirement proposal) reference this note rather than
re-deriving provenance.
- Home
- Architecture
- Backend Execution
- Benchmarks
- Dashboard
- Development
- Encoding Goldens
- Event Datasets
- Event Runtime And Energy
- Features
- Implications And Boundaries
- Interop Foldins
- Interpreter Spine
- Introspection
- Model Deployment
- Model Hub
- Notes
- Operational Maturity
- Production Workflows
- Project Layout
- Quickstart
- Requirements
- Sequence Primitives
- Streaming Timeseries
- Targets And Interop
- Usage
- Arch 0001 Adr Repo Topology
- Arch 0001 Core Boundary
- Arch 0001 Decision Metrics
- Arch 0001 Migration Plan
- Arch 0001 Packaging Versioning
- Arch 0001 Protocol Contract
- Arch 0001 Risk Register
- Arch 0001 Target Topology
- Backend Execution Plan
- C Package Contract
- Client Diff Classification
- Ecosystem Listings
- Ecosystem Roadmap
- Event Runtime Plan
- Hub Accounts Plan
- Hub Expansion Plan
- Plans
- Integration Plan Historical
- Interop Foldins Plan
- Interpreter Spine Plan
- Memory System Research
- Model Hub Plan
- Nir C Runtime Profile
- Nir Unmappable Decisions
- Operations Plan
- Production Toolkit Plan
- Production Use Cases
- Professional Roadmap
- Repo Topology Plan
- Sequence Primitives Plan
- Snn Interpreter Provenance
- Use Case Audio Keyword Spotting
- Use Case Biosignal Medical Monitoring
- Use Case Computational Neuroscience
- Use Case Edge Power Budgets
- Use Case Event Camera Vision
- Use Case Intrusion Anomaly Detection
- Use Case Low Latency Sensor Stream
- Use Case Rl Control Robotics
- Use Case Spiking Transformers
- Use Case Streaming Timeseries