How to Build Marcus's Algebraic Mind: Algebro-Deterministic Substrate over Galois Fields

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2605.21379v3 Announce Type: replace-cross Abstract: In The Algebraic Mind (2001), Marcus held that any adequate cognitive architecture needs operations over variables, recursively structured representations, and an individual/kind distinction, and that multilayer perceptrons support none of them; he left a register-and-treelet implementation as a conjecture. Twenty-five years later a memory architecture built for unrelated reasons (speed, power and cost on commodity silicon) meets that specification operation for operation, through one mechanism rather than three. PyVaCoAl/VaCoAl is a hyperdimensional computing architecture built end-to-end on one primitive: XOR-and-shift over GF(2), realised by primitive-polynomial linear-feedback shift registers (LFSRs). It gives reversible binding Bind(R,F) = R xor shift(F), non-commutative bundling that distinguishes "dog bites man" from "man bites dog", and address-space individual/kind separation, at fixed dimension. Capability: exact reversible binding at O(L) cost supplies each pillar as an architectural primitive, not a product of training, with inspectability no lossy substrate offers. Necessity: weaken the primitive to an approximate inverse, as circular convolution does, and all three pillars degrade together -- what cannot be exactly decomposed was never composed, only mixed. Position: this is not the mind, the brain is not an LFSR, and we do not beat large language models; the substrate supplies the auditable symbolic layer they structurally lack. We develop the correspondence pillar by pillar, recast the treelet as …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2605.21379
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.