Skip to content
zensation

Research

πŸ”¬

Research overview

Three tracks, architecture and agenda

πŸ“

Methodology

Operational standards and validation

πŸ“„

Publications

Preprints, software, identifiers

βš–οΈ

Research ethics

Fundamental rights and compliance

🧰

Resources

Code, data, citation, open science

Collaboration & applications

πŸ›οΈ

Public sector & funding

Collaborations in the public sector

🧭

Adopt AI

Neutral roadmap & interactive simulation

πŸ›‘οΈ

Protecting public spaces

Track B β€” rights-preserving early warning

βš™οΈ

Technology

ZenBrain β€” our open core

PublicationsAboutOpen SourceBlog
Contact
zensation

Research

πŸ”¬Research overviewπŸ“MethodologyπŸ“„Publicationsβš–οΈResearch ethics🧰Resources

Collaboration & applications

πŸ›οΈPublic sector & funding🧭Adopt AIπŸ›‘οΈProtecting public spacesβš™οΈTechnology
PublicationsAboutOpen SourceBlogContact
Blog
Engineering

Seven Layers: A Memory Model Takes Shape

Alexander Bering
Alexander Bering
January 28, 2025 Β· 3 min read

From a stack of references to a model

The 2024 sketch had the right instincts and no edges. Over the following months it hardened into something we could actually reason about: seven memory layers, each with a defined role, and a handful of principles governing how information moves between them.

The seven layers, in plain terms:

  • Working memory β€” the active focus of the current task.
  • Short-term memory β€” the context of the current session.
  • Episodic memory β€” concrete experiences, with their time and surroundings.
  • Long-term memory β€” the durable, distilled knowledge.
  • Procedural memory β€” learned routines and how-to.
  • Core memory β€” a small set of pinned, always-present facts.
  • A predictive layer β€” the part that anticipates and revises, which we left deliberately underspecified at this stage.

The number seven is not sacred. It is the smallest set that gave each documented function its own home without forcing two unlike things to share one.

Consolidation, not retrieval, at the centre

The design decision we are most committed to is also the least obvious: the interesting work happens between writes and reads, not during them.

Most systems do everything at write time or query time. We pushed the important transformations into a separate, scheduled process β€” a consolidation pass, in the spirit of sleep consolidation, that replays recent experience, strengthens what is used, lets the incidental fade, and promotes episodic detail into semantic knowledge. Retrieval then operates over a store that has already been organised, rather than over raw sediment.

This is a methodical choice as much as a biological analogy. It means the system's behaviour over weeks is governed by a process we can inspect and tune, not by an accident of what happened to be written down.

Confidence as a first-class output

The second principle: a memory system should know how sure it is. Recall is not binary. A well-timed review makes a memory more retrievable; time without review makes it less so; some facts are corroborated from several directions and some rest on a single mention.

So from early on we treated confidence as something to be propagated and reported β€” a calibrated estimate attached to what the system returns, rather than a single best guess presented with uniform certainty. A system that can say "I am fairly sure, on weak evidence" is more useful than one that presents every answer with the same certainty, and it makes its own limits legible.

Still an open question

In January 2025 this was a model and an early implementation, not a result. The principles were defensible on paper; whether they would outperform a plain vector store under real load was unproven. But the model now had edges sharp enough to test β€” which is the only state from which a research question can move forward.

The model became running code, layer by layer: The 7-Layer Architecture, The Art of Forgetting, and Sleep Consolidation.

Share on XShare on LinkedIn

Related Articles

From AI Overview to a Real Demo: Turning a Blueprint into a ZenAi Instance β€” Autonomously

Most AI pilots don't fail on the technology β€” they fail at the jump from idea to a tangible, context-true application. Here's how a quick assessment turns autonomously into a lightweight, sector-accurate ZenAi instance β€” and why honesty (clearly labelled demo data) is the most important building block.

The Stress Test: Why We Ran Ten Security Sprints Before the First Customer

Between 'it runs on my machine' and 'a company entrusts it with its data' lies a gap many AI projects underestimate. How we bridged it with ten back-to-back hardening sprints.

91 % of the accuracy at 1 % of the tokens β€” the Pareto position for AI memory

On LongMemEval-500, ZenBrain reaches 91.3 % of a long-context oracle's accuracy at 1/106α΅—Κ° the per-query token budget. The oracle wins by 4.5 percentage points, burns 106Γ— more tokens, and has no memory architecture at all.

Β© 2026 Alexander Bering / ZenSation Enterprise Solutions

HomeResearchMethodologyResearch ethicsPublic sectorPublicationsResourcesAdopt AIOpen SourceTechnologySystem explorerAboutBlogRSSChangelogPrivacy PolicyLegal NoticeAccessibility
GitHubLinkedInarXivZenodoORCIDScholarSemantic ScholarHuggingFacenpmDiscord