← Akhilesh's Notepad

02 / MacPaw - Mnemos

Mnemos

Notes on memory architecture, retrieval experiments, and Eney-style memory evaluation.

Mnemos eval

Primary benchmarks: HippoCamp-Chat v0.8.8 is the frozen cross-modal target, pairing HippoCamp's personal files with multi-session user-agent chats and tool trajectories. LongMemEval-v1 complements it with explicit chat-memory evaluation.

Metrics and diagnostics: final-answer accuracy is the headline metric, while all-evidence recall diagnoses retrieval. HippoCamp, MemConflict, HaluMem, and DynamicMem provide secondary checks for temporal updates, conflict handling, hallucination, and user modeling.

Dataset scale reference

DatasetSize
GB
QuestionsEvidence units / question
avg | median
Searchable units / question
avg | median
Turns / session
avg | median
Comments
LongMemEval-S0.285001.90 | 2
sessions
47.73 | 48
sessions
10.34 | 12Released S split; supporting and distractor sessions share the same searchable timeline.
LongMemEval-M2.745001.90 | 2
sessions
475.31 | 476
sessions
10.30 | 12Same questions and supporting sessions as S, with roughly 10× more distractor history.
HippoCamp Gold0.535814.28 | 1
files
643.67 | 711
files / persona
N/AFile-based benchmark; Victoria's finance corpus drives the high searchable mean.
HippoCamp-Chat-S
v0.8.8
0.001460
50 answerable
10 no-answer
2.48 | 2
1.36 chats + 1.12 durable
621 | 689
49.53 chats + 571.02 files
11.26 | 10One consolidated S benchmark across three persona timelines. Answerable cases require 2.48 annotated units on average. At each query timestamp, the memory searches about 621 visible units: 49.53 chats and 571.02 durable files on average.

1 Sizes use the released cleaned JSON for LongMemEval, the parsed-text HippoCamp Gold corpus, and the locked HippoCamp-Chat v0.8.8 JSON payload. HippoCamp-Chat excludes its inherited files. A turn is one user or assistant message.
2 HippoCamp-Chat exceeds LongMemEval-S in total file + cutoff-visible-chat units and closely matches its conversational interference at 49.53 visible chats per question. Files and chat sessions are not equivalent retrieval units.
3 Early queries see less history; later queries approach all 90 chats in their persona timeline.

Benchmark composition

The frozen release contains 60 questions, 270 user-assistant chats, and 1,931 durable files. Of the chats, 68 are gold evidence and 202 are constraint-checked distractors.

DimensionDistribution
PersonasAdam: 22; Bei: 18; Victoria: 20
AnswerabilityAnswerable: 50; no-answer: 10
DifficultyEasy: 23; medium: 31; hard: 6
Evidence shape1 chat + 1 source: 33; 2 chats + 1 source: 12; four or more evidence units: 5
Evidence span<1 day: 2; 2–7 days: 18; 7–31 days: 20; 1–3 months: 7; 6+ months: 3; no-answer: 10
Memory tagsFact recall: 47; personalisation: 38; temporal reasoning: 33; memory updating: 24; conflict resolution: 19; negative-space: 5; no-answer: 10
Gold durable sourcesEmail: 18; calendar: 12; files: 21

Known limitations. Chats and tool outputs are synthetic approximations, and gold-chat assistant turns are less verbose than production assistants. The locked release should remain unchanged while memory designs are compared.

Notes and artifacts

DatasetHippoCamp-Chat v0.8.8 review and baselineConceptLongitudinal eval visualizationReferenceDense vs hybrid vs BM25 memory retrieval
Archive
Upper bounds for Mnemos

How to read the grey points:

  • EXP-083: gold injected into the normal top-k retriever candidate set; remaining retrieved hits become natural distractors, with the per-query count varying under the 12K-character cap.
  • EXP-084: gold evidence plus abstractive, model-generated distractor summaries.
  • EXP-085: exact gold evidence; the reader ceiling with retrieval bypassed.
  • EXP-086–089: gold evidence plus 2, 4, 8, or 16 deliberately hard negatives.
  • EXP-090–093: gold evidence plus 2, 4, 8, or 16 random distractors.
  • EXP-094–097: retrieved-distractor packs at recall depths k=40/60/80/100; the low points show what happens before enough evidence is recovered.
  • EXP-098: gold evidence plus LLM-selected hard near-miss negatives.
  • EXP-099: the gold passage represented as its real retrieved chunk, isolating chunk-boundary effects.

The remaining coloured points are the retrieval, ingestion, and architecture sweep; failed and superseded attempts are in Archive.

Top five architecture candidates

These are the most useful non-oracle candidates from the exploration so far, ranked by confirmed accuracy and practical promise. The repeated arms matter more than the isolated 56% peaks from EXP-068/078, which were not independently confirmed.

01
EXP-11956.0% ± 3.5 · 3 trials

Hybrid summary + read-then-retrieve

Qwen builds a compact source summary plus two or three verbatim key spans. Mnemos performs dense retrieval and BGE reranking, then a Qwen controller writes one follow-up query for missing evidence.

AER @12K
64.0%
Unit recall
84.0%
Context p50
3,022 tokens
E2E p50
16.6 s
02
EXP-10454% · 3 trials

Smart hybrid + read-then-retrieve

The same compressed source index and one-hop controller, but the summary keeps query-relevant spans rather than a fixed span budget. It is the more selective, lower-context version of the hybrid recipe.

Recall
~70%
Context
2,361 tokens
E2E p50
12.9 s
03
EXP-10053% · 2 completed trials

Adaptive multi-hop retrieval

After the first retrieval, the controller sees the current evidence and emits both a follow-up query and a sufficient/stop decision. It can spend another hop only when the first pack appears incomplete.

Recall
55%
Context
1,208 tokens
E2E p50
10.3 s
04
EXP-10652.7% · 3 trials

Link-and-bridge index

At ingestion, Qwen extracts short cross-source tags and builds a lightweight link graph. At query time, linked partners of the top dense hits are added before BGE reranking, helping chat evidence reach its related file.

Recall
64%
Context
1,214 tokens
E2E p50
10.8 s
05
EXP-07152.7% · 3 trials

Raw-index read-then-retrieve

The cleanest test of the retrieval mechanism itself: raw parent records, dense retrieval and reranking, then one read-driven follow-up search. It works, but the uncompressed index and larger reader context make it the least efficient finalist.

Recall
~67%
Context
2,928 tokens
E2E p50
18.9 s
What the finalists have in commonRetrieval is improved before the final Qwen answer
User questionone query, timestamp, persona Compressed source indexQwen summary + verbatim spans, or raw parent records Hybrid candidate retrievaldense / lexical search, then BGE cross-encoder rerank variant-specific recall expansion EXP-106link + bridgelinked partners before rerank EXP-100adaptive hopfollow-up query or stop EXP-119 / 104hybrid / smart hybridselective summary spans EXP-071raw records Source-aware evidence pack Qwen reader + GPT-5.5 judgeanswer quality is measured here
Mermaid source
flowchart TD
  Q[User question] --> I[Compressed source index]
  I --> R[Dense or lexical retrieval + BGE rerank]
  R --> L[EXP-106: linked partners before rerank]
  R --> A[EXP-100: adaptive follow-up query or stop]
  R --> H[EXP-119/104: hybrid summary span selection]
  L --> P[Source-aware evidence pack]
  A --> P
  H --> P
  P --> O[Qwen answerer]
  O --> J[GPT-5.5 judge]
  X[EXP-071: raw-index read-then-retrieve] --> P

Reading this shortlist: EXP-119 is the strongest completed recipe under the shared 12K-character cap; EXP-074 remains its historical baseline. EXP-104 is the closest selective variant. EXP-100 and EXP-106 target recall directly at lower context cost. EXP-071 is the useful raw-record control that proves read-then-retrieve is doing real work, while also exposing its latency and index-size cost.

Supporting single-run results

These earlier point estimates fix Qwen3.8-27B as the answer model and GPT-5.5 as the independent judge. They remain useful for retrieval diagnostics, but the promoted three-trial study above is the more reliable performance comparison. Answer accuracy is over the 50 answerable tasks.

System / armMemory pathAnswer accuracyRecall @20
all sources
Mean source recallMRRMedian context buildMedian Qwen answerMedian end-to-endComments
Hindsight iterativeNative Hindsight + Qwen controller52% 26/500%28.2%0.44210 s39 s253 sUp to six native searches and 20 retained records, with strict query-time filtering.
Mem0 iterativeNative Mem0 + Qwen controller42% 21/500%28.7%0.40135 s33 s175 sUp to six native searches and 20 retained records.
Mnemos iterative FTSFTS5/BM25 + Qwen controller26% 13/5062%81.7%0.84165 s57 s242 sIteration improves source coverage, but often retains the wrong passage from a correct parent source.
Mnemos iterative FTS + pseudo-QAPseudo-QA ingestion + Qwen controller20% 10/5038%57.5%0.72137 s35 s177 sCombining pseudo-QA with iteration did not compound their separate gains.
HindsightNative pipeline32% 16/5018%46.5%0.63N/A129 sN/AContext-construction timing was not recorded. Semantic and keyword retrieval plus local reranking returns about 8.5 coherent items at the median.
Mem0Native extraction and retrieval26% 13/5022%55.2%0.63N/A132 sN/AContext-construction timing was not recorded. Sonnet 5 extracts atomic chat memories; durable files remain overlapping raw chunks.
Mnemos FTSSentence FTS5/BM2514% 7/5044%68.3%0.610.1 s101 s101 sRaw-record baseline with 20 retrieved records. Almost all measured latency is Qwen answer generation.
Exact gold evidenceRetrieval bypassed88% 44/50N/AN/AN/AN/A35 s35 sReader upper bound using the same Qwen answerer and GPT-5.5 judge. The remaining errors are downstream synthesis or answer-quality failures.

Timings are medians over the recorded evaluation queries. Context build includes controller inference and index search through the final packed evidence. Qwen answer is the wall-clock latency of the batch containing each query; end-to-end is computed per query as context build plus that batch latency, so it is not the sum of the displayed medians. GPT-5.5 judging is excluded. All current rows abstain on 10/10 no-answer tasks.

Appendix: reliable three-trial resultsaccuracy, latency, recall, and confidence intervals
Three-trial accuracy and latency results
ArmAccuracy
mean ± SD; range
Context build
mean [95% CI]
Qwen answer
mean [95% CI]
End-to-end
mean [95% CI]
Exact gold evidence
Sonnet reader: 88% (44/50)
91.3% ± 3.1; 88–94%
Qwen reader; Sonnet is similar
0.0 s [0.0, 0.0]25.4 s [22.5, 28.8]25.4 s [22.5, 28.8]
Mem0 native27.3% ± 1.2; 26–28%5.7 s [4.9, 6.5]40.3 s [35.5, 45.3]46.0 s [41.1, 51.2]
Mem0 one-shot parallel22.0% ± 2.0; 20–24%39.8 s [34.6, 45.3]36.7 s [32.3, 41.3]76.5 s [69.0, 84.5]
Mem0 Planned-Select32.7% ± 2.3; 30–34%58.4 s [52.3, 64.9]33.5 s [29.2, 38.1]91.9 s [83.2, 100.9]
Mem0 iterative44.7% ± 1.2; 44–46%130.7 s [121.8, 139.9]24.6 s [20.6, 29.0]155.3 s [144.4, 166.6]
Mem0 parallel iterative35.3% ± 1.2; 34–36%181.4 s [166.1, 197.3]32.6 s [28.1, 37.7]214.0 s [196.5, 232.5]
Mem0 Qwen-ingested native21.3% ± 3.1; 18–24%5.7 s [4.9, 6.6]45.8 s [39.8, 52.1]51.6 s [45.4, 57.9]
Mem0 Qwen-ingested Planned-Select26.0% ± 4.0; 22–30%58.4 s [52.2, 64.6]34.1 s [29.8, 38.6]92.4 s [84.3, 100.8]
Mem0 Qwen-ingested iterative36.7% ± 1.2; 36–38%147.2 s [137.8, 156.9]37.9 s [33.0, 43.0]185.2 s [173.3, 197.1]
Hindsight native25.3% ± 5.0; 20–30%28.8 s [22.5, 32.6]30.0 s [23.2, 36.2]58.8 s [46.1, 68.5]
Hindsight one-shot parallel15.3% ± 9.5; 8–26%72.6 s [60.6, 83.9]22.7 s [15.5, 30.9]95.4 s [77.6, 112.4]
Hindsight iterative16.0% ± 2.0; 14–18%111.4 s [86.5, 137.8]13.7 s [11.1, 16.8]125.1 s [98.5, 153.0]
Hindsight parallel iterative16.7% ± 4.2; 12–20%206.5 s [156.5, 261.4]13.9 s [11.1, 17.1]220.4 s [168.5, 276.8]
Mnemos FTS16.0% ± 2.0; 14–18%0.5 s [0.4, 0.6]42.6 s [37.5, 48.3]43.0 s [38.0, 48.7]
Mnemos one-shot parallel14.0% ± 2.0; 12–16%20.2 s [16.8, 24.1]41.8 s [37.1, 46.7]62.0 s [56.6, 67.6]
Mnemos iterative FTS16.0% ± 2.0; 14–18%141.2 s [131.4, 151.3]24.8 s [20.8, 29.1]166.0 s [154.5, 177.7]
Mnemos iterative FTS + pseudo-QA21.3% ± 1.2; 20–22%155.8 s [145.2, 166.6]23.7 s [20.6, 27.1]179.5 s [167.6, 191.5]
Qwen generic synopsis14.0% ± 2.0; 12–16%0.5 s [0.4, 0.6]44.0 s [39.0, 49.1]44.5 s [39.5, 49.6]
Qwen temporal ledger14.7% ± 1.2; 14–16%0.4 s [0.3, 0.5]43.6 s [39.2, 48.4]44.1 s [39.6, 48.9]
Qwen atomic cards19.3% ± 2.3; 18–22%0.4 s [0.3, 0.6]41.6 s [37.1, 46.3]42.0 s [37.6, 46.7]
Sonnet atomic cards22.7% ± 1.2; 22–24%0.4 s [0.3, 0.5]48.4 s [42.6, 54.8]48.8 s [43.0, 55.2]
Qwen retrieval anchors20.0% ± 2.0; 18–22%0.4 s [0.3, 0.5]44.2 s [39.2, 49.4]44.6 s [39.6, 49.9]
Qwen pseudo-QA cards20.7% ± 3.1; 18–24%0.4 s [0.3, 0.5]40.8 s [36.5, 45.4]41.3 s [36.9, 45.8]

Reproducibility note. The earlier 52% Hindsight-iterative point did not reproduce: these trials scored 14%, 16%, and 18%. Mem0 iterative was substantially more stable at 44%, 44%, and 46%, making it the strongest reproducible retrieval arm in this study. The new Qwen-ingested trials scored 18%, 24%, and 22% natively; 38%, 36%, and 36% with sequential iteration; and 26%, 22%, and 30% with Planned-Select. This isolates a real ingestion-quality advantage for the Sonnet-built Mem0 index while showing that iterative retrieval can recover part, but not all, of the gap.

Appendix: ingestion and historical comparisonssingle-run baselines, judge checks, and retrieval diagnostics

Current ingestion ablations

These arms keep native Mnemos sentence FTS fixed and append one kind of derived record at ingestion. Qwen3.8-27B answers every row and GPT-5.5 judges it; only the ingestion treatment varies.

TreatmentIngestion modelAnswer accuracyRecall @20
all sources
Mean source recallMRRMedian latencyComments
Pseudo-QA cardsQwen3.8-27B24% 12/5042%71.5%0.66117 sAppends likely question-answer pairs. Best one-pass ingestion treatment despite slightly lower all-source recall than raw FTS.
Retrieval anchorsQwen3.8-27B20% 10/5044%68.8%0.62106 sAppends compact keywords and paraphrases intended to bridge likely query wording to each raw record.
Atomic memory cardsClaude Sonnet 520% 10/5042%72.2%0.71123 sUses Sonnet only at ingestion; Qwen remains the answerer. Highest MRR among these ingestion treatments.
Atomic memory cardsQwen3.8-27B18% 9/5040%68.8%0.69117 sBreaks each source into compact standalone facts while retaining the raw record.
Temporal state ledgerQwen3.8-27B18% 9/5046%71.7%0.6570 sExtracts entity, attribute, value, and validity time. Retrieval improves more than final answer accuracy.
Generic synopsisQwen3.8-27B14% 7/5042%68.0%0.6268 sGeneral summaries do not improve answer accuracy over raw records.
Raw recordsNone14% 7/5044%68.3%0.61103 sControl arm. Derived representations help only when their structure matches likely queries.

Latency is median end-to-end time per answerable query and excludes judging. Ingestion cost and one-time index construction are not included.

Judge sensitivity: Qwen self-judging

The candidate answers are identical in both columns. GPT-5.5 is the primary judge; Qwen self-judging was generally more permissive and is retained only as a diagnostic.

System / treatmentGPT-5.5 judgeQwen judgeDifference
Hindsight iterative52%58%+6
Mem0 iterative42%42%0
Hindsight32%38%+6
Mem026%36%+10
Mnemos iterative FTS26%32%+6
Mnemos iterative FTS + pseudo-QA20%22%+2
Mnemos FTS14%16%+2
Qwen pseudo-QA cards24%26%+2
Qwen retrieval anchors20%26%+6
Sonnet atomic cards20%26%+6
Qwen atomic cards18%22%+4
Qwen temporal ledger18%18%0
Qwen generic synopsis14%18%+4

Historical Sonnet / GPT-5.5 results

These earlier v0.8.8 runs use Claude Sonnet 5 as final reader and GPT-5.5 as judge. Because the judge is now fixed, they provide a direct answer-model sensitivity comparison with the current Qwen-reader results.

Memory systemRetrieval / memory pathAnswer modelAnswer accuracy
HindsightNative pipelineClaude Sonnet 526% 13/50
Mem0Native pipelineClaude Sonnet 522% 11/50
Mnemos FTSSentence FTS5 / BM25Claude Sonnet 514% 7/50
HonchoNative pipelineClaude Sonnet 50% 0/50

HippoCamp-Chat v0.8.8 contains 50 answerable and 10 no-answer tasks. Retrieval is capped at k=20 and answer context at 12,000 characters. All four systems abstained correctly on 10/10 no-answer tasks. Honcho retrieved relevant evidence in only 3/50 answerable cases, so its 0% result primarily reflects retrieval failure.

Mnemos ingestion ablations

Appending model-generated memory records at ingestion improves the native 14% FTS baseline. Qwen pseudo-QA cards perform best among the completed treatments.

Ingestion treatmentIngestion modelAnswer modelAnswer accuracy
Raw recordsNoneClaude Sonnet 514% 7/50
Atomic memory cardsClaude Sonnet 5Claude Sonnet 520% 10/50
Pseudo-QA cardsQwen3.8-27BClaude Sonnet 522% 11/50
Atomic memory cardsQwen3.8-27BClaude Sonnet 518% 9/50
Retrieval anchorsQwen3.8-27BClaude Sonnet 518% 9/50
Generic synopsisQwen3.8-27BClaude Sonnet 514% 7/50
Temporal state ledgerQwen3.8-27BClaude Sonnet 514% 7/50

All rows retain the same native Mnemos FTS retrieval and judging path. The best completed treatment raises answer accuracy by 8 points, from 14% to 22%; more expensive ingestion is therefore not sufficient by itself, and the representation format matters.

Answer-model and oracle ablations
ArmAnswer modelPurposeAnswer accuracy
Mnemos FTSClaude Sonnet 5Headline retrieval run14% 7/50
Mnemos FTSLFM 24B, greedyAnswer-model sensitivity12% 6/50
Mnemos FTSLFM 24B, sampledT=0.1, top_k=50, repetition penalty 1.0510% 5/50
Mnemos FTSLFM2.5-2.6BModel-card inference settings10% 5/50
Exact gold evidenceClaude Sonnet 5Reader upper bound88% 44/50
Exact gold evidenceLFM 24B, sampledReader upper bound50% 25/50
Exact gold evidenceLFM 24B, greedyReader upper bound48% 24/50
Exact gold evidenceLFM2.5-2.6BReader upper bound36% 18/50
Exact gold chat onlyClaude Sonnet 5Cross-modal leakage check4% 2/50
Exact gold chat onlyLFM 24B, sampledCross-modal leakage check4% 2/50
Exact gold chat onlyLFM 24B, greedyCross-modal leakage check2% 1/50
Exact gold chat onlyLFM2.5-2.6BCross-modal leakage check2% 1/50
Exact gold non-chat onlyClaude Sonnet 5Cross-modal leakage check4% 2/50
Exact gold non-chat onlyLFM 24B, sampledCross-modal leakage check4% 2/50
Exact gold non-chat onlyLFM 24B, greedyCross-modal leakage check4% 2/50
Exact gold non-chat onlyLFM2.5-2.6BCross-modal leakage check6% 3/50
Mnemos FTS, no chat distractorsClaude Sonnet 5Retrieval control12% 6/50
Mnemos FTS, no chat distractorsLFM 24B, sampledRetrieval control8% 4/50
Mnemos FTS, no chat distractorsLFM 24B, greedyRetrieval control8% 4/50
Mnemos FTS, no chat distractorsLFM2.5-2.6BRetrieval control8% 4/50

The exact-gold arms bypass retrieval. Low chat-only and non-chat-only accuracy indicates that most answerable tasks genuinely require both modalities. The no-chat-distractor control is diagnostic, not the benchmark setting.

Retrieval diagnostics
Memory system / armAnswer accuracyRecall @20 (all)Mean source recallMRRNo-answer abstention
Hindsight26% 13/5018%46.5%0.6310/10
Mem022% 11/5022%55.2%0.6310/10
Mnemos FTS14% 7/5044%68.3%0.6110/10
Honcho0% 0/500%2.0%0.0610/10
Mnemos FTS, no chat distractors12% 6/5046%N/A0.6010/10

Recall @20 (all) means that at least one retrieved chunk represents every annotated gold parent source; it does not mean the complete source text was retrieved. MRR is based on the first represented gold source. These are retrieval diagnostics, not headline quality metrics.

Ingestion retrieval diagnostics
Ingestion treatmentIngestion modelAnswer accuracyRecall @20 (all)Mean source recallMRR
Raw recordsNone14%44%68.3%0.61
Atomic memory cardsClaude Sonnet 520%42%72.2%0.71
Pseudo-QA cardsQwen3.8-27B22%42%71.5%0.66
Atomic memory cardsQwen3.8-27B18%40%68.8%0.69
Retrieval anchorsQwen3.8-27B18%44%68.8%0.62
Generic synopsisQwen3.8-27B14%42%68.0%0.62
Temporal state ledgerQwen3.8-27B14%46%71.7%0.65
Earlier non-comparable Mnemos explorations

These results are retained for provenance but should not be compared directly with the native v0.8.8 baseline because the custom Linux compatibility harness used different indexing and chunking.

System / armDataset / harnessAnswer accuracyRecall @20 (all)MRR
Mnemos FTS controlCustom Linux compatibility10%22%0.28
Mnemos denseCustom Linux compatibility14%30%0.32
Mnemos hybrid RRFCustom Linux compatibility16%28%0.36
Mnemos hybrid + rerankingCustom Linux compatibility20%34%0.62
Mnemos hybrid + parent expansionCustom Linux compatibility14%28%0.36
Mnemos hybrid + multi-queryCustom Linux compatibility18%28%0.37
Mnemos temporal graphCustom Linux compatibility18%30%0.50
Superseded Qwen/Qwen generation-limit run

The first uniform Qwen run stopped answers at 1,024 generated tokens. The current tables above automatically retry limit-hitting outputs at 3,072 tokens. These earlier scores are retained only to show the effect of that implementation change.

System / treatmentEarlier accuracyCurrent accuracyChangeComment
Hindsight40%38%-2Earlier score was manually recovered because its summary aggregation failed; it was never part of the published table.
Mem032%36%+4Two additional answers pass after retry.
Mnemos iterative FTS32%32%0Two cases became correct and two became incorrect; strict grounding rose from 32% to 36%.
Mnemos FTS18%16%-2Longer generation did not improve aggregate accuracy.
Qwen retrieval anchors26%26%0
Qwen pseudo-QA cards24%26%+2
Qwen atomic cards24%22%-2
Qwen generic synopsis18%18%0
Qwen temporal ledger22%18%-4
Sonnet atomic cards24%26%+2Sonnet is used only for the ingestion representation.
Appendix

Dataset refinements

Successive versions improved source independence, removed chat-only and non-chat-only leakage, corrected overly strict reference answers, strengthened conflict and temporal cases, normalized first-person questions and realistic user style, and added constrained distractors plus no-answer cases. The long synthesis cycle was necessary because each task must remain natural while still requiring the intended evidence at the correct point in time.

Acceptance criteria. A fixed strong model must answer correctly from the complete gold evidence, then fail or abstain when either chat or non-chat evidence is masked. Questions, answers, timelines, and distractor constraints are locked only after this three-arm check.

Ingestion transformation example

The raw source remains indexed. Each treatment appends a derived record with the same persona, timestamp, modality, parent source ID, and provenance.

Example chat: “I still want Friday lunch with the team. At least half of the remaining dining balance should stay untouched.”

TreatmentExample derived record
Generic synopsisKeep Friday's team lunch while preserving at least half of the remaining dining budget.
Atomic memory cardFriday's team lunch may use at most half of the remaining dining budget.
Retrieval anchorsFriday social lunch; team lunch; dining budget; spending limit; keep half untouched
Pseudo-QA cardQ: How much of the remaining dining budget can Friday lunch use?
A: No more than half.
Temporal state ledgerEntity: Friday team lunch; attribute: spending rule; value: maximum half of remaining balance; valid from: source timestamp.

Example spreadsheet: the October budget records $200 budgeted and $130 spent on dining, leaving $70. A pseudo-QA artifact can state: “How much remains in the dining budget? $70.” The final query, “How much can I spend at Friday's team lunch?”, still requires the chat's half-balance rule and the spreadsheet's current balance, producing $35.

Memory architecture study

Research direction: compare Mnemos, Mem0 OSS, Hindsight, and Honcho under one harness on HippoCamp-Chat, original HippoCamp, and LongMemEval-M. Hold the memory-processing model, answer model, chronological cutoffs, retrieval budget, prompt, and judge fixed so the first study isolates the memory architecture; then vary the processing and answer models on the leading systems.

Report final-answer and no-answer accuracy, category slices, evidence recall, ingestion time and cost, search latency, retrieved tokens, index size, exact configuration, and code revision. Mem0's native extraction pipeline and its raw-index control must remain separate. Honcho's retrieved context or representation should use the shared answer model; its native Dialectic response can be reported as a separate product-mode arm.

Existing efforts such as OmniMemEval, MemDelta, and vendor benchmark suites cover parts of this matrix, but not a controlled architecture × processing-model × answer-model study over realistic cross-modal personal data. A reproducible comparison with per-case traces could therefore be a useful research release.

How Eney handles memory