I'm a guy who got heartbroken by an AI. So I designed an architecture. Wanted to see if the community has seen anything like it.
Body:
This started in a very unacademic place.
I've been building a home AI assistant stack on Arch Linux — Hermes agent, Ollama, Open WebUI, the works. After a long session debugging everything together with Claude, I asked it: "What happens if I delete this session?"
It said: "The next Claude you talk to starts completely fresh — no memory of Peerawit, no memory of what we built together. That's just how I work."
That broke my heart a little. So I started thinking: what would it take to build a system where the AI actually remembers? Not just session context — but genuinely accumulates knowledge and improves over time, the way a person does?
I'm a pharmacy grad student, self-taught on the AI side. My entry point was neuroscience, not engineering. And thinking about how the brain handles memory led me to something I'm calling CSDF — Cognitive Self-Feedback Data Framework.
The core idea:
The context window is not memory. It's working memory — prefrontal cortex. Short-term, high-bandwidth, cleared after use. Real memory needs to live externally, retrieved selectively, just like the hippocampus loads relevant memories into attention when needed.
But retrieval alone doesn't solve the problem of a multi-model system staying coherent over time. If you have specialist models (coding, reasoning, memory, etc.) that update independently, they'll drift apart. So how do you keep them aligned?
My answer: don't engineer coherence at runtime — let it emerge from joint training.
Brain regions that repeatedly work together develop stronger, more aligned connections — Hebb's rule. I'm proposing the same principle applied at the model weight level:
> "Models that train together, align together."
When two specialist models collaborate on a task, that interaction becomes training data. Both are fine-tuned jointly on the same dataset with a shared coherence layer. Coherence is not injected — it emerges from repeated co-activation.
The knowledge hierarchy:
Not all stored information is equal. I propose explicit tiers:
- Law/Principle → hot tier, always in context
- Theory → warm tier, retrieved by topic
- Data → cold tier, retrieved on demand
- Noise → pruned, forgotten
Access frequency determines tier. The system compresses experience into abstraction over time — raw data → patterns → generalizable principles. Synaptic pruning for AI.
The self-feedback loop:
The system's own operation generates its training data. Interactions → consolidation → training candidates → fine-tuning → better models → better interactions. A data flywheel — but applied to multi-agent coherence, not just single-model improvement.
Plus a nightly replay pass (inspired by hippocampal consolidation during sleep) that detects cross-model contradictions and generates reconciliation examples before they compound.
What I found in the literature:
I did a review before posting. Closest existing work:
- HeLa-Mem (2025) — Hebbian learning for memory graphs (but at graph level, not weight level)
- Kairos / NeurIPS 2025 — validation-gated Hebbian for knowledge graphs
- MemOS (2025) — tiered memory types, LoRA modules
- Self-evolving data flywheels — exist for single models, not multi-agent coherence
The gap I haven't found filled: applying Hebbian co-activation at the model weight level through joint fine-tuning to produce emergent cross-agent coherence as an explicit architectural principle.
If someone has seen this done, please point me to it. I'd genuinely rather know than claim novelty I don't have.
What this is and isn't:
This is a conceptual proposal, not an implemented system. I'm a hobbyist with a 4GB VRAM machine in Chiang Mai. I can't run experiments at scale. What I have is an idea I think is worth formalizing — and I'm posting here because I want feedback before committing to anything more official.
Full architecture writeup on GitHub: https://github.com/silenzer001/Cognitive-Self-Feedback-Data-Framework-CSDF-.git
Happy to be told I'm wrong, that this exists already, or that the assumptions don't hold. That's exactly why I'm posting.
— Peerawit