Neuralware Index (registry reconciliation) · neuralware-index
Owner directive (2026-06-12), canonical for the model. "Neuralware is a plug-an-play Cogni with due source and qasi-kernel resources. So it is of extreme importance the concepts,: tools, skils, whatever... are well set and ready for the Cognitive Loop when some Looper or Datan chose a Neuralware." [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:184-185]
Content
A neuralware is a plug-and-play cogni (capability + due source + quasi-kernel resources) a looper or datan equips into the cognitive-loop; under the 2026-06-12 directive every capability is available to every Datan (available_to: all-datans) [src: wiki/voidweb/neuralwares.json:1]. This card reconciles the two machine registries.
Both registries currently enumerate the same 37 ids. The canon JSON declares count: 37 [src: wiki/voidweb/neuralwares.json:1]. The code registry originally held 28 entries; RUN-013 item #11 appended the 9 doc-only ones under the comment "Canon reconciliation (RUN-013 #11) — 9 neuralwares declared in wiki/voidweb/neuralwares.json (37 total) but previously doc-only" [src: HOS-Webdoc/web/src/lib/sapiens3/neuralware-registry.ts:51-53]. The composition is 37 = 20 original + 3 web-capability + 5 browser-platform + 9 ontology/tooling [src: wiki/reference/neuralware-catalog.md:5].
The 28 pre-RUN-013 registry ids [src: HOS-Webdoc/web/src/lib/sapiens3/neuralware-registry.ts:5-49]
| Group | Ids |
|---|---|
| dooit (4) | nw-code-writer · nw-file-ops · nw-build-runner · nw-git-ops |
| ditto (4) | nw-api-verify · nw-schema-validate · nw-data-augment · nw-endpoint-expose |
| Orchestration / construct (3) | nw-squad-assembly · nw-loop-coordinator · nw-priority-router |
| assistant (2) | nw-context-reader · nw-response-gen |
| companion (2) | nw-pref-learner · nw-context-persist |
| advisor (3) | nw-frontier-scanner · nw-strategy-gen · nw-benchmark-compare |
| Universal (2) | nw-loop-runner · nw-spark-emitter |
| Web-capability, 2026-06-12 (3) | nw-modern-web-guidance · nw-iwa · nw-devtools-149 |
| Browser-platform, 2026-06-12 (5) | nw-chrome-extensions · nw-chrome-release-channels · nw-origin-trials · nw-chrome-chromium · nw-bfcache-notrestoredreasons |
The 9 RUN-013 canon-reconciliation additions (delta 28 → 37) [src: HOS-Webdoc/web/src/lib/sapiens3/neuralware-registry.ts:54-62]
nw-blackboard · nw-coder (Visual Studio light) · nw-hieroglyph · nw-neural-engine (Lighthouse / n8n) · nw-palantir-ontology (write-back) · nw-servers (Server Fleet / dyson substrate) · nw-studio (ComfyUI) · nw-version-control (Git) · nw-visual-studio
These nine match the owner's academy list of swappable gear — "N8N, ComfyUI,VisualStudio,Gitea,Servers,APIS,TOOLS, WHATEVER" [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:612] — and are the backbone of gear-sets.
Variants
| # | Definition (verbatim) | Source | Ruling | Status |
|---|---|---|---|---|
| A | "Machine-readable registry: voidweb/neuralwares.json — 37 neuralwares (20 original + 3 web-capability + 5 browser-platform + 9 ontology/tooling additions). Code: sapiens3/neuralware-registry.ts (the original code registry; the ontology/tooling additions — Palantir-Ontology, Visual Studio, Git, Servers, Hieroglyph, Neural-Engine, Studio, Coder, Blackboard — are registered in the VoidWeb registry)." | [src: wiki/reference/neuralware-catalog.md:5] | pending — see Open question (states the 9 are not in the code registry) | variant |
| B | "// Canon reconciliation (RUN-013 #11) — 9 neuralwares declared in wiki/voidweb/neuralwares.json (37 total) but previously doc-only." — followed by the 9 entries in the code registry itself | [src: HOS-Webdoc/web/src/lib/sapiens3/neuralware-registry.ts:51-62] | pending — see Open question (the code now carries all 37) | variant |
| C | "The 37 neuralware-registry entries (RUN-013) are exposed as tools without mutating the registry." | [src: wiki/engines/above-adk-runtime.md:94] | pending — consistent with B, contradicts A's "original code registry" wording | variant |
Open question
To the owner: no D-ledger or C-entry rules on the neuralware count/placement.
- Confirm 37 as the canonical neuralware count going forward (28 = the pre-RUN-013 code registry; 37 = canon JSON and the post-RUN-013 code registry), and that the code registry legitimately carries the 9 ontology/tooling entries.
- If confirmed,
wiki/reference/neuralware-catalog.md:5should be corrected — it still says the 9 additions live only in the VoidWeb registry, which no longer matchesneuralware-registry.ts:54-62. - Confirm the
nw-*namespace remains registry-internal: this library models the index and gear-sets, not one card per neuralware.
Composition
- uses: neuralware (the concept) · cognitive-loop (where equipped neuralwares inject) · sapiens3 (the engine whose registry this is)
- used-by: gear-sets (loadouts draw from this index) · sop-001-loop-execution (academy swaps pick from here) · squad-eggtech / squad-schematic / squad-instance (all equipment)
See also
- neural-engine —
nw-neural-engineis its neuralware form - sop-002-conflict-resolution — the procedure that keeps this card draft until ruled