All posts

A Memory That Never Sleeps

Dr. Jerry A. Smith · September 11, 2026 · 8 min read

Building Minds — what a firm's AI memory should attend to, keep, and bring back

A Memory That Never Sleeps

Until August, the decision memory I had been building for investment firms kept every word of every document it had ever read. Nothing faded.

That design feels safe. It is not. The remedy is not deletion.

A memory that retains everything at equal weight has never decided what matters. The next person who searches decides for it. Most days that is enough. It fails in three ways, and each failure costs judgment the firm has already paid for.

Similar decisions blur. Two add-on acquisitions with the same structure and different outcomes answer the same query; nothing says which lesson applies. Popularity begins to look like truth. Material cited often rises in the ranking, and if summaries draw on what ranks highly, repetition passes for corroboration. Old warnings stay buried. Evidence that didn't matter when it arrived, but matters a great deal after the thesis changes, has no path back to the surface.

Simpler fixes exist, and they may be enough: better ranking, strong provenance, date filters. I do not yet know whether a more deliberate design beats a well-tuned single store. That is the honest starting point for what follows.

What the brain does at night

The brain faces the same problem on a larger scale. Much of its answer arrives during sleep.

It runs two learning systems. The hippocampus captures experience quickly, one episode at a time. The neocortex learns slowly, extracting what holds across many episodes. McClelland, McNaughton, and O'Reilly argued in 1995 that the split is necessary: a single system fast enough to learn from one experience would overwrite what it had learned before.

Most of what the fast system captures does not last. Frey and Morris found in 1997 that a weak change at a synapse became durable only when strong stimulation elsewhere on the same neurons triggered protein synthesis within a window of less than three hours. They proposed a tag that marks which changes are eligible to be kept. Selection also looks forward. In a 2011 study by Wilhelm and colleagues, sleep improved memory only for people who had been told they would be tested later.

At night, the hippocampus replays the day. In 1994, Wilson and McNaughton found that rat place cells that fired together during exploration fired together more often in the sleep that followed. Two years later, Skaggs and McNaughton showed that the firing order was preserved as well. In 2009, Girardeau and colleagues tested whether the replay matters: suppress those bursts after training, and rats learn a maze more slowly.

Sleep also takes things away. Tononi and Cirelli's synaptic homeostasis hypothesis holds that waking strengthens synapses across the cortex and sleep scales them back down, keeping the differences between them while restoring room to learn. In mice, de Vivo and colleagues found synaptic contacts about 18 percent smaller in animals that had slept than in animals that had been awake, with the largest synapses spared. Richards and Frankland argue that this kind of forgetting is a feature: it keeps outdated detail from interfering with flexible decisions.

None of this proves that software should work the same way. It offers design hypotheses, and each one translates into an operation.

Capture fast; integrate slowly. New evidence counts the moment it arrives. Changes to what the firm believes go through a slower step. Score attention, and let the score fade unless something renews it. Integrate by comparison: before proposing a change to a belief, pull the prior evidence that supports it and the prior evidence that conflicts with it. Scale priority down as well as up, or everything drifts to the top. Let what falls away leave the default view, not the record.

One departure from the brain is deliberate. Recalling a human memory can change it. Nader, Schafe, and LeDoux showed in 2000 that reactivated fear memories in rats needed new protein synthesis to re-stabilize. A firm's memory should never work that way. Using a memory can change how prominent it is. It must never change the evidence behind it.

A firm cannot simply forget

Here the analogy breaks, and the break matters. Firms carry audit, legal, and regulatory obligations. The document that justified a decision cannot vanish because nobody opened it for a year.

So the design separates two things a brain never has to separate. The record keeps everything, unaltered, with its provenance. Active memory is what search and reasoning consult by default. For a firm, forgetting means demotion from active memory — never destruction of the record.

Five things a single store blurs

Once the record and active memory are separate, five properties that usually hide inside one relevance score come apart.

Attention priority: what gets reviewed, integrated, or shown first. Evidence confidence: how strongly a claim is supported. Temporal validity: when a claim applies, and whether it has been superseded. Memory status: whether something is recent, consolidated, or archived. Retention protection: what must stay recoverable, and under what conditions.

Holding them apart yields four rules.

Use is not evidence. Retrieval and citation can raise priority; they never raise confidence. Authority counts from day one. Audited financials carry evidentiary weight the moment they arrive, before anyone has worked through what they imply. Staleness is a validity question, not doubt. A figure reported as of a date is no less supported a year later; it is only less current. Protection is not prominence. A decision record can be guaranteed never to be destroyed without being guaranteed the top of every search.

The first rule is the one I needed most. The system has an option, built but never switched on, that would let approvals, upheld challenges, and recent citations nudge a fact's confidence upward. This work argues for keeping the first two and dropping the citations.

Recommended by LinkedIn

[Lead with the Brain. Land on the Calendar.Lead with the Brain. Land on the Calendar. Eva D'lom, ACC

5 months ago](https://www.linkedin.com/pulse/lead-brain-land-calendar-eva-d-lom-ec3ae) [The new science of controlling lucid dreamsThe new science of controlling lucid dreams Scientific American

1 year ago](https://www.linkedin.com/pulse/new-science-controlling-lucid-dreams-scientific-american-rqgae) [What Your Brain Actually Does While You SleepWhat Your Brain Actually Does While You Sleep npnHub | Uniting Experts and Learners in Applied Neuroscience

5 months ago](https://www.linkedin.com/pulse/what-your-brain-actually-does-while-you-sleep-npnhubcommunity-fxlnf)

The warning that comes back

Suppose the following. The companies and numbers are invented; the structure is not.

A diligence memo reports that Company A's largest customer is 41 percent of revenue, on a contract that renews in 20 months. The committee passes on A. The recorded rationale is valuation. Nothing connects the concentration warning to anything the firm is working on, and nobody opens it. Three months later it leaves active memory, with a note in the record saying why.

Over the next year, the firm buys Companies B, C, and D. Each has one customer at 30 to 45 percent of revenue. Each looks good at its 12-month review. The system proposes a generalization: at these add-ons, concentration has not hurt 12-month results. A reviewer approves it. It is cited in four investment memos. Its visibility rises. Its confidence does not, because citation is use, not evidence.

At month 18 the firm adopts a new thesis: build a platform and sell it to a strategic buyer within two years. The same week, a banker's note says strategic buyers discount platforms where any customer tops 25 percent. The goal change triggers a search of the archive. Back come Company A's warning, the past decision, and a market update reporting that A lost its largest customer at renewal.

The system proposes a narrower generalization. Concentration did not hurt 12-month results in three deals, but it is untested past the first renewal, and under an exit thesis it is a valuation risk. A reviewer approves the revision and records the reason. The old version is closed, not erased.

Across the whole story, the evidence behind Company A's warning never changed. Only its visibility did.

Walking the scenario end to end exposed rules I would not have found in the abstract. A generalization must carry its scope, including the time horizon of the outcomes behind it. It needs a stored search for counterexamples that can be re-run later. And recovery cannot be optional, because nothing at month 0 could have known the warning would matter.

Four ways back

Forgetting is only safe if the way back is designed as carefully as the way out.

A goal changes: search the archive for what the new goal makes relevant. A belief is contradicted or thinly supported: widen the search before answering. A reviewer restores something, with the reason on record. A fixed share of each night's work goes to neglected material and possible counterexamples, without waiting for a trigger.

What's built, and what isn't

One narrow form of forgetting is built. Past a retention window, the exact text of an old document version fades to a summary, with the source still recoverable. Its first run faded 77 document versions and dropped 358,587 characters.

Everything else here is a proposal. The test I have designed compares each piece against the strongest single store I can build, with the same ranking signals, provenance, models, and budget. It seeds the failures that matter: late relevance, popular documents that turn out wrong, contradictions, and changed goals. Each piece has to earn its place. If the single store wins every comparison, that is a real result. It would mean a good ranking is enough, and this design shouldn't be built.

The cost I am watching most closely is reviewer time. Every proposal and every restore that reaches a person requires attention a firm may not have.

Five questions for any AI memory you trust with decisions

When a document is used often, does it become more credible, or only more visible?

Can the system tell you when a claim stopped applying, not only when it was written?

What leaves the default view, by what rule, and where is that recorded?

When your thesis changes, what brings back old evidence?

Which records can never be destroyed, and is that separate from how prominently they appear?

A memory that never sleeps never has to decide what mattered. The brain makes that call every night, in the dark. A firm's memory has to make it in the open, with a record of every choice.

When your firm's thesis last changed, what old evidence should have come back?

— Jerry

Start with one workflow.

Tell me what your team does today, where the work gets stuck, and what a useful result would look like. We will use a short call to identify a sensible next step.

Book a call