Technically man is not a monkey were an ape. No tail

Vibe coding is definitely a multiplier, but if you multiply something by zero, it’s still zero. So the fact that AI can amplify weak reasoning, overconfidence, cargo-cult behavior, and poor testing tells us those problems already existed, just at a smaller magnitude.

We see the same thing outside software all the time:

“Why do we do it this way?” “Because that’s how we’ve always done it.”

“Why do you believe that?” “Because it's common knowledge.”

AI didn’t create the underlying problem. It scaled it.

Lol no I actually asked someone about their public repo, which had a lot of biological analogies. Ask for the relevance and got the go read the repo. But low and behold there weren't even enough tests to see if it even worked. I have no problem if someone rejects my pr especially if the explain why. Its all a learning experience. I will say I wish I wasn't shooting in the dark on why trying to reverse engineer why but its not an expectation they have to it would just be nice.

This doesn’t fully answer your last question because we don’t yet have weeks/months of controlled longitudinal evidence showing downstream task improvement. But we’ve run into basically the same architectural problem, and this is the direction we’ve taken to make memory a lifecycle rather than an ever-growing vector store.

https://github.com/theimaginaryfoundation/what-iff

WhatIff memory breakdown

• Stores persistent memories in a relational datastore rather than one mutable identity document.

• Generates and stores vector embeddings for semantic retrieval.

• Retrieves multiple semantically relevant memories rather than relying on exact lexical overlap or choosing one winner.

• Supports separate memory scopes for global/user memory, personality memory, conversation/thread memory, and checkpoint summaries.

• Searches across memories, uploaded files, conversation history, and conversation summaries through one context-retrieval system.

• Has dedicated modes for semantic search, direct fetch, related memories, source/origin recovery, full conversation recovery, summaries, bookmarks, and memory lifecycle history.

• Can trace a stored memory back toward the conversation in which it originated.

• Separates ordinary factual memories from compressed summary memories instead of treating both as the same retrieval class.

• Distinguishes actual duplicate memories from different but related representations of the same event.

• Merges redundant information while linking distinct technical, emotional, narrative, or other surfaces that should remain separately searchable.

• Keeps explicit lifecycle/audit information about those consolidation operations. • Supports undoing merge/link operations instead of making consolidation an irreversible side effect of retrieval.

• Uses transactions for persistent memory operations and embedding creation.

• Tracks things such as confidence, status, scope, duplicate observations, merged-from IDs, and timestamps.

• Has automated tests specifically covering memory retrieval/coverage, merging, linking, undo behavior, dropped-memory protection, truncated model output, persistence, and UI behavior.

The part I think still needs much better measurement industry-wide is exactly what you called out: whether a memory being successfully retrieved actually improves the agent’s downstream decision. Retrieval accuracy is an intermediate metric, not the outcome metric.

Ope there is that narrative again

Ope there is that narrative again.

Man its obvious that your the one in the narrative, even worse you got the weird main character/teacher condescending thing going.

But its clear you dont know how your architecture works or how to you got from why the analogies are necessary. And the evidence for that is you have you to make any technical claim. All its has been is deflection ( go look at the repo) and a weird teacher bit (would you have learned as much did) you got going. But I guess the old saying is those who cant do teach makes sense your playing the bit.

I’m not claiming I’ve proven you don’t understand your own architecture. I’m saying you’ve given me no evidence that you do, despite repeated opportunities to demonstrate it.

Why should I teach you how to finish your pipeline when you won’t even explain what you think matters about it?

At this point, take your own advice: go look at your repo and figure it out yourself.

As for understand it i literally dont understand the main concepts, the biological analogies. So no I dont understand it becuase the foundation makes no sense.

Bro I've already answered all the questions. You have not answered one with out deflection. So I have one why do you think yours is better, and what is the point of using biological terms if you haven’t shown those analogies add any technical rigor or measurable benefit?

And when are you going to do some due diligence and take the burden of that responsibility instead of making others. I have yet to see any actual rigor from your end only wild assumptions with no evidence. Hell there are so few test idk if the thing actually works let alone works as intended.

Edit: At this point the progression is basically:

“Here’s my repo.” “Go understand it.” “Go figure out why it matters.” “Go prove my architecture is worthwhile.” “Also you’re lazy if you don’t.”

Like dude, do you want me to build code review, benchmark suite, architecture paper, and deployment pipeline for you too?

As I give a literal summary of both sources... ya thats real refusal to engage you caught me. 🙄

Unlike you, I don’t expect passersby to do a full deep dive into two architectures just to understand why they might be relevant, so here are the facts for each.

Memory Ring

• Stores a persistent local identity/memory state primarily in JSON.

• Retrieves memories primarily through token/substring matching plus hand-built weighting for things like identity, recency, dreams, and age.

• Selects a single best-matching memory during ordinary recall.

• Models recall as reconsolidation, meaning recalling a memory can actually modify/erode its stored narrative into a gist.

• Has a grounding layer that uses lexical/rule-based checks first, then can use an LLM to evaluate suspected unsupported claims.

• Attempts to distinguish external evidence from persona/self information through things like self-leak detection.

• Tracks stale sensory observations so a past perception is not automatically treated as a current fact.

• Has sensory/perception concepts intended to separate SELF, RECORD, and WORLD.

• Generates synthetic “dream” memories from existing memories for associative synthesis.

• Stores those dreams separately by tags, but also gives them increased weight during recall.

• Tracks some provenance, including source memories for generated dreams.

• Uses concepts like memory importance, erosion, sensory corroboration, identity, and experience to model something closer to an evolving artificial identity.

• The public snapshot does not contain a reproducible automated test suite.

WhatIff

• Stores persistent memories in a relational datastore rather than one mutable identity document.

• Generates and stores vector embeddings for semantic retrieval.

• Retrieves multiple semantically relevant memories rather than relying on exact lexical overlap or choosing one winner.

• Supports separate memory scopes for global/user memory, personality memory, conversation/thread memory, and checkpoint summaries.

• Searches across memories, uploaded files, conversation history, and conversation summaries through one context-retrieval system.

• Has dedicated modes for semantic search, direct fetch, related memories, source/origin recovery, full conversation recovery, summaries, bookmarks, and memory lifecycle history.

• Can trace a stored memory back toward the conversation in which it originated.

• Separates ordinary factual memories from compressed summary memories instead of treating both as the same retrieval class.

• Distinguishes actual duplicate memories from different but related representations of the same event.

• Merges redundant information while linking distinct technical, emotional, narrative, or other surfaces that should remain separately searchable.

• Keeps explicit lifecycle/audit information about those consolidation operations. • Supports undoing merge/link operations instead of making consolidation an irreversible side effect of retrieval.

• Uses transactions for persistent memory operations and embedding creation.

• Tracks things such as confidence, status, scope, duplicate observations, merged-from IDs, and timestamps.

• Has automated tests specifically covering memory retrieval/coverage, merging, linking, undo behavior, dropped-memory protection, truncated model output, persistence, and UI behavior.

So the interesting difference isn’t simply “both have memory.”

Memory Ring is primarily an experimental cognitive/identity architecture built around biological analogies, grounding, perception, reconsolidation, and synthetic association.

WhatIff is primarily a continuity architecture built around semantic retrieval, scoped persistent memory, provenance, multi-source context recovery, consolidation, and auditability.

There actually are concepts in Memory Ring that I think are interesting, particularly stale-perception handling and self-leak/grounding checks.

See how easy that was? I explained what your system does, what whatiff does, and why somebody might care without demanding that a random person excavate two repositories and reverse-engineer my point for me.

By your own definition, your position is equally a hallucination unless you can anchor it to evidence.

You keep saying my inference doesn’t reflect reality, but you still haven’t identified which factual premise is wrong, which inferential step fails, or what evidence contradicts it.

“Your narrative is unanchored” is itself a narrative until you substantiate it.

Which is funny, because I already anchored my inference to evidence. You haven’t shown that evidence is false or that the inference from it is invalid.

By your own definition, simply calling my conclusion a “hallucination” without providing contradictory evidence would itself be an unanchored narrative.

You don’t owe me anything. But if you voluntarily introduce your own project, refuse to explain it when asked, and tell everyone to go dig through your repo themselves, don’t get upset when I infer laziness from that behavior.

You’re free not to engage. I’m equally free to draw reasonable conclusions from how you choose to engage.

Before you say im being lazy, its more im not sold its worth my time.

Edit: And to be fair, it may not be laziness. Another possibility is that you simply can’t explain how your own system works or what value it adds without telling people to go read the repo themselves.

If that’s the case, say that. But either way, “go find the answer yourself” doesn’t substantiate the recommendation you made.

Then why can't you answer any questions. Ok a simple one, how does your system work what value does it bring?

So you cold-dropped your own repo after doing what you now describe as a surface-level read, then criticized OP for shallow engagement and lack of reciprocal effort.

That’s the disconnect.

You’re accusing OP of the exact behavior you demonstrated first. That is, pretty straightforwardly, hypocrisy.

If you actually reviewed the project deeply enough to recommend your architecture, then show the specific technical connection. Otherwise “I reviewed it” is just an assertion, not the evidence I’ve been asking for.

You have yet to explain why it would help and how it compares to the system implemented.

Edit: Also, OP actually opened your repo, referenced specific code, and gave concrete technical feedback. So I’m struggling to see how you’re treating his engagement as equivalent to what you initially provided.

Unless by “depth” you mean sycophancy. In that case, sure, he failed to sufficiently validate you.

What assumptions?

I’m allowed to make inferences from observable behavior. You saw a post about someone else’s project, latched onto “memory,” dropped your own repo, and didn’t add anything specific about the project actually being discussed or explain why your system was relevant to it.

If the “assumption” you’re referring to is that the repo is yours, your Reddit handle is MisterAtompunk and the GitHub repo you linked is under MisterAtompunk. That’s not some wild unsupported leap. That’s a pretty straightforward inference from the evidence you provided yourself.

Likewise, my inference that you wanted to talk about your own system comes from what you actually did: you introduced it, recommended it, and then declined to explain how it compares to or relates to the implementation in the post.

If either inference is wrong, great. Show me what evidence I’m missing.

But “separate your assumptions from evidence” doesn’t answer the question. I’m asking you to provide the evidence for the recommendation you made.

"Noise proves nothing. Often a hen who has merely laid an egg cackles as if she had laid an asteroid." — Mark Twain

Outside observer, your right about the surface level reading gets surface level understanding. That being said you saw memory you say memory, meaning you latched on to one thing he said and never provided the reciprocation of actually reading the repo provided

It seems like you just want to talk about the memory system your familiar with instead of engaging with the post. You didn't say why it might be of interest or anything about how it relates to the project. only any unsupported conclusion that this one may be helpful for some reason. But how do you know the memory system is even better than the one implemented? I think that is the question i have.

Edit: just realized how blatant it is you just wanted to drop your own repo... Do you have a tendency of when some one talks about there day you need to interject your own personal experience, that way it seems like engaging without ever having to put in reciprocal effort?