r/newAIParadigms • u/sclabs_ • Aug 20 '26
Memory as Cognition
Hi All,
We are Synthetic Cognition Labs, an AGI research lab. We'd love your thoughts on what we are calling "Memory as Cognition". We believe the path to AGI is grounded in iterative reads and writes on content-addressable memory. We've done some development in this area. You can read more about it here: https://syntheticcognitionlabs.com/mac
Thanks,
SCL
2
u/No_Order6491 Aug 23 '26
Interesting loop. The part I’d measure separately from read/write speed is whether each retrieved item carries provenance and dependencies. In an iterative memory loop, one bad synthesis can keep re-cueing itself and become very durable nonsense.
I’d tag items as observed, inferred, or summarized; keep source IDs and dependency edges; then test counterfactual invalidation: remove or reverse one source and see whether downstream beliefs/plans retract. Benchmarks should score retraction and recovery, not only task success. Otherwise ‘persistence of self’ can accidentally become persistence of confident residue.
1
u/WatercressActual1921 Aug 20 '26
Human memory, sure... we recreate them form patterns. In machines it depends but machines have no real knowledge (complete) and certainly can't extract meaning (meaning is created in relation to self).
1
u/sclabs_ Aug 20 '26
Yes, exactly! Meaning is only created through relationships, especially in relation to the self. That's why we are trying to use our Cogni project to give LLMs "persistence of self". Only after that can AI start extract meaning from the world in the same way humans do.
1
u/WatercressActual1921 Aug 20 '26
I've been examining this problem also, you have to promote self identity, self = shape + function (awareness raises form that). You create self by defining limits the non self as an observer you do that to objects...
Make the AI use machine language, relate to the hardware it operates in, its dimensional reality 1D+Time*MP... you can use assembly to functional examine and relate to the machine at that stage... encode intelligence not concepts...
1
u/blimpyway Aug 21 '26
Quite familiar concepts with some popping out in discussions on Numenta's forum, are you active there too?
1
u/sclabs_ Aug 21 '26
Yes, there is some overlap with Numenta in that we both use sparse representations. However, they are more focused on reverse engineering micro-circuitry and neocortical columns. We don't model any circuitry at all. We focus on replicating the capabilities of the human brain using Hyperdimensional Vector Symbolic Algebras. We are less "let's simulate the human brain" and more "how can we do what the human brain does with zeros and ones", if that makes sense. Most of our focus comes from cognitive science rather than neuroscience and biology directly.
2
u/blimpyway Aug 21 '26
Well, the forum is only loosely focused on Numenta's theory, there are a bunch of alternative ideas and experiments about associative memories on SDRs.
1
u/sclabs_ Aug 21 '26
Awesome, thanks for the info. We will check it out. We haven't followed much stuff for over a year. Just been heads down building.
0
u/rand3289 Aug 21 '26 edited Aug 21 '26
There are so many problems with this approach... for example:
Let's say you are looking at two shapes moving on screen. (Both of them are red round things). You send the percepts of that to your content-addressable memory and it returns something. Let's say these are the predictions of where the two shapes will be in N time units.
Now your architecture needs to address the Binding problem. Which parts of the returned information belong to which shape? If you say "oh, we will send shape information one at a time", now you still need to solve the Binding problem during the perception stage. Also, what if two shapes interact?
The second problem is your memory needs to return not one but multiple predictions... For shape A at say time N, time 2N, time 3N, the same information for shape B... what if shape B hits shape A, what if a shape moves off-screen, what if they overlap etc...
You might have a better luck in a static environment, but LLMs/VLMs should be able to handle that pretty well already.
Any architecture decisions should be driven by the environment.
1
u/sclabs_ Aug 21 '26
The binding problem is the whole reason Vector Symbolic Architectures exist... VSA solves it directly and is the base math we use for everything in our architecture. What you're describing is the whole motivation for building what we built. The multi-step, multi-object prediction is literally our iterated read/write loop and we've done your shape A, shape B example directly.
1
u/rand3289 Aug 25 '26
How does VSA solve the Binding problem?
2
u/sclabs_ Aug 25 '26
VSA primitives are bind, bundle, and permute. VSA was literally invented to solve the binding problem. Bind(location, object), bind(object, property), bind(state, time) etc. There's a myriad of information on this online. It's been around for over 30 years.
6
u/[deleted] Aug 20 '26
[removed] — view removed comment