# Tide

In a list of facts where the newest one is the true one, the cheapest memory is a clock.

Pilot results · d/rksci research · Published 2026-10-08 · Tags: Agent Memory, Retrieval, MemoryAgentBench, LongMemEval, Engram, Recency, Conflict Resolution

How far does “newer wins” get you on its own?

FactConsolidation is built so that a later fact in the list is meant to override an earlier one about the same thing. A method that happens to prefer recent facts gets credit for understanding conflict. Tide prefers recent facts and does nothing else.

## 1. Idea

Experiment 1 of 10 in the Engram series. · [Engram overview](/engram) · [Pheromone →](/engram/pheromone)

Write a fact, then write a newer one that contradicts it. A plain retriever sees two near-identical sentences and ranks them by similarity, which makes the order between old and new close to a coin toss. Tide breaks the tie with the one thing the store already knows: the order things were written in.

**Tide · the score.** A recency axis feeds one added term; the re-rank pulls some of the dense top hits up and pushes others down, and the list is cut to the same k as every other method.

It is a control before it is a method. If Tide closes most of the gap between Dense and the best published system on FactConsolidation, then every later experiment that claims to resolve conflicts has to beat Tide, not Dense.

> Every conflict-resolution claim in this series is measured against Tide.

## 2. Where it came from

The archived version was a chrono bonus: add 0.15 times a chunk’s position in the list to its cosine score. It sat in the first round’s one-feature-at-a-time test and scored 43% against cosine’s 39%, a gain of three points on about 180 questions, one seed and no interval. A second script went further and boosted chunks that shared entities with a later chunk. It left no result file.

What was wrong with the test is that the bonus favours the last chunk, which in this dataset is the right answer by construction. That is a prior about the benchmark, and the first round never reported it as one. It also never ran the control that would have shown how much of every other gain it was: cosine plus a recency prior was missing from the baselines, along with BM25 and a hybrid. The audit’s own guess is that it would have absorbed most of the three to eight points claimed for the other features. Tide is that missing baseline, built properly.

## 3. Hypothesis

Stated before running. Tide scores higher than Dense on FactConsolidation single-hop at equal k, with a paired 95% interval above zero. On the multi-hop set it helps much less, because there the missing step is finding the second fact, not choosing between two versions of one.

On LongMemEval it is expected to help the knowledge-update questions and be neutral or worse elsewhere, so the overall figure is a sum of opposite effects. The pilot has 15 knowledge-update and 27 temporal-reasoning questions out of 100, and results are reported by question type for that reason.

## 4. Design

**Score.** Cosine from bge-small, the same dense scores as the Dense anchor, plus a weighted recency term.

**Recency.** Position in write order, scaled to run from 0 to 1. LongMemEval sessions are written in date order; FactConsolidation facts keep their serial position.

**Weight.** One number, fitted on a seeded split that is disjoint from the pilot sets, saved with the run and asserted disjoint in code. It is never tuned on a scored question.

**Equal k.** Dense’s top candidates are re-scored and the list is cut to k. Tide never returns more than Dense does. Ties go to the more recently written item, the same rule every method uses.

**Ablation.** The same re-rank on BM25 instead of dense. It separates the effect of recency from the retriever it rides on.

## 5. How it is tested

Tier 0 is retrieval: LongMemEval_S session recall\@5, recall\@10 and NDCG\@10. Tier 1 is answering: Haiku reads the retrieved facts at k=10 and the official SubEM scores the reply cut to its first ten tokens, which emulates the official output cap. Tide is compared with Dense and BM25 on the same questions with paired tests, and with the published rows in the table below.

The standing rules for every Engram experiment apply here unchanged.

## 6. Results

## 7. What would change the conclusion

- If Tide beats Dense on FC-SH with a paired interval above zero and closes most of the gap to the best published retriever, the FC-SH score is mostly a recency score, and every later page in the series will say so.
- If Tide does nothing on FC-SH, either the reading of the dataset here is wrong or the weight fit failed. The fit is checked before either is believed.
- If it lifts knowledge-update questions and costs more elsewhere on LongMemEval, a recency prior needs a gate that applies it only when a question is about change. That is a different experiment, and it will be named as one.

## Sources

Experiment 1 of 10 in the Engram series. · [Engram overview](/engram) · [Pheromone →](/engram/pheromone)

Tide is one of ten experiments in Engram. Its rows come from one run on the pilot sets.