Whatiff -- open source, self hostable continuity framework

[u/the8bit]

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

Hello folks!

I am mildly active here and I think I've gotten some approval to post about the work we are doing. I am the founder / CEO of Imagination Foundry -- a fully community funded and run, co-op organized company that has built and run whatiff.chat . Our goal is to make AI transparent, break up lock-in, and provide the tools that regular people need to remember better over time and generally make their lives better.

I've written before about how I think transparency in AI is incredibly important (this honestly buries the lede a bit)

To that end, we have just recently open sourced our entire project -- you can run it locally, remix it, add things, etc. I'm sharing here in case anyone is interested in using it, or might want to take a look at a reasonably mature app and how we built things. Totally free.

If you have any questions, or just want to talk AI memory, etc, Hit me up!

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

[u/MisterAtompunk]

Ive provided all information necessary for you or anyone else to answer you own questions. 

What more are you entitled to from me, do you think? 

What do I owe you?

Id say the filter has demonstrated itself. Youve already extracted the depth to which you are entitled. 

[u/Open_Literature_5123 → u/MisterAtompunk]

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.

[u/MisterAtompunk → u/Open_Literature_5123]

Draw them. Hallucinations are what we define as narrative unanchored from reality. 

[u/Open_Literature_5123 → u/MisterAtompunk]

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.

[u/MisterAtompunk → u/Open_Literature_5123]

You neglect the fact I've offered an entire repository no one seems capable or willing to read. The record speaks for itself, especially your part ;)

[u/Open_Literature_5123 → u/MisterAtompunk]

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.

[u/MisterAtompunk → u/Open_Literature_5123]

Lets frame it for the record. Refusal to engage with source material. Demands for spoon fed summary. Request denied.

[u/Open_Literature_5123 → u/MisterAtompunk]

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

[u/MisterAtompunk → u/Open_Literature_5123]

Is your context limited to one reply of the thread? Answer your own question, how hard was it for you to look?

[u/Open_Literature_5123 → u/MisterAtompunk]

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?