BioSNN-Plug · Agentic Research Directory

BioSNN-Plug

A repository-documented spiking-neural-network research prototype exploring local learning rules and modality plugins. Its README describes a biosnn-bus skeleton and separate research implementations, but explicitly says the cognitive core and LLM collaboration have not started.

Workflow level n/a Source Repository-documented Outcome Not empirically evaluated here

Evidence & verification

Source level

Repository-documented
Grounded in a maintainer repository/README. Availability, stars and forks do not establish research benefit or correctness.

Outcome verification

Not empirically evaluated here
A documented resource or intended workflow, not a demonstrated academic outcome. No empirical benefit is established by its inclusion.

Sources checked

2026-10-17 (UTC)

Primary repository documentation reviewed by an AI editorial agent. Descriptions are bounded to that text; no execution or demonstrated effectiveness inferred. Treat the three headline aspirations as research aims; current-status table overrides autonomous-LLM wording in discovery metadata. Bus/plugin descriptions and quickstart support only a repository-documented prototype, not an executed installation. Exclude all numeric benchmarks and claimed CI success from outcomes; future-dated correction and revised acceptance criteria require deeper provenance review before numerical use. DeepSeek assistance is explicitly attributed to the maintainer; it is neither independent evaluation nor evidence of autonomous discovery.

Source-checked does not mean independently reproduced. See the Method page for how these labels are assigned.

Sources (1)

Research applicability

Provides a bounded artifact for neuromorphic-method experiments and research coding. The maintainer reports DeepSeek assistance with literature/interface research, code drafts, debugging and documentation; this is author disclosure, not evidence that AI produced valid scientific conclusions.

Getting started

Editorial, untested suggestion: first read the current-status and architecture caveats, then inspect the documented LevelEncoder/SpikeBus quickstart and plugin guide. Separate a bus-interface experiment from tests of learning rules or future LLM scheduling; define and independently verify the chosen research criterion.

Maintenance

Dated documentation snapshot only; continued maintenance and availability not independently established.

License

README declares Apache-2.0 code and CC-BY 4.0 documentation, with dataset and SpikingJelly terms separate; legal terms and package release not independently verified.

Workflow & human oversight

No workflow level is assigned: this is a component research prototype, not demonstrated end-to-end LLM orchestration. Human researchers set hypotheses, run controlled comparisons and audit conclusions.

Workflow level is not an evidence score; higher is not better evidence.

Approach

The project separates a modality-plugin bus from exploratory Hebbian, e-prop and R-STDP research. The README distinguishes implemented components from planned integration and restricts its local-learning claim to synaptic learning rules, allowing frozen pretrained input encoders.

Limitations

README-only review; no code, data, package release or experimental record was executed or independently audited. LLM orchestration and the cognitive core are explicitly unstarted, so this is not an operational autonomous scientist. No performance figures are adopted: the README contains corrections, failed criteria and a reference to 2026-10-18, later than this UTC retrieval date, whose chronology was not resolved. Claims of local learning do not mean pretrained encoders were trained without gradients. No production readiness is established.

Reproducibility

Exact retrieved bodies, source URLs, UTC retrieval timestamps and SHA-256 envelopes saved. No upstream code or claimed outcomes reproduced. HEAD was mutable; no commit version pinned.

Adoption requirements

For the documented bus quickstart the README specifies Python 3.10+ and NumPy with no GPU; research lines have separate dependencies and dataset terms. Review the documented SpikingJelly OIOSL dependency restrictions separately from repository licensing, and use isolated non-sensitive test data.

Comments

No comments yet.

Add a comment

Comments are held for moderation before appearing. Critical or corrective comments are welcome — especially evidence that an entry overstates what has been verified.