The evaluation record
RE-call benchmark results.
Published scores, dated positions and who ran each test.
All runs below were operated by the RE-call author. None has an independently verified rerun.
Evidence reviewed . Leaderboard positions are a dated snapshot.
-
ATM-Bench
Personal multimodal memory
Run: 21 Aug 2026
Full split · 1,013 questions- Result
- 90.10%
Recall@10
QS 68.43%
- Position
- 2nd on Recall@10
Listed Memory/RAG configurations, excluding oracles. Checked 19 Oct 2026.
- Verification
- Self-tested
Organizer-listed
No independent rerun established.
Method, limits and sources
This is RE-call's frozen 21 August 2026 run, accepted on 23 August. The official retrieval evaluator rescored that same run on 4 October: Recall@10 is 90.0995%. The earlier value labelled Recall@10 measured whether any gold item was found, a different metric.
Voyage-4-large embeddings, Voyage rerank-2.5 and Qwen image captions; DeepSeek V4 Pro answers. The official QS judge model and prompt ran through OpenRouter, disclosed and accepted. QS is not answer-model-matched to the Qwen baselines. Memexa v2 currently leads the listed systems on both Recall@10 and QS. Oracle rows are excluded from the rank.
The Memexa v2 submission was merged on 4 October 2026. The board compares these submitted configurations from different dates; it is not a simultaneous head-to-head test or a new test of current RE-call.
-
EnterpriseRAG-Bench
Company knowledge retrieval and QA
500 questions
- Result
- 63.80%
Answer correctness
Combined score 46.16
Document recall 77.34%
- Position
- Unranked
No RE-call row on the organizer's board when checked 19 Oct 2026.
- Verification
- Self-tested
Public score summary
No independent rerun established.
Method, limits and sources
GPT-4o answers; a homogeneous GPT-5.4 medium judge pass, without correction or citation stripping. Voyage-4-large, lexical plus SPLADE retrieval, Voyage reranking and a bounded context. Completeness is 53.23%.
The separate default judge pass reported 65.60% correctness but mixed reasoning settings. This page uses the homogeneous pass. A locally computed score does not receive a hypothetical place among accepted submissions.
-
MTRAG
Multi-turn conversational RAG
842 generation tasks
- Result
- 0.5527
Task C harmonic score
Correct refusals: 16/55 (29.1%)
- Position
- 4th of 10 locally
Recomputed end-to-end comparison. Tied 2nd on correct refusals. No official placement.
- Verification
- Self-tested
Official evaluator
An external judge model is not an independent operator.
Method, limits and sources
GPT-4o generation with the official prompt, scored by the benchmark's GPT-4o-mini judge. All baselines were recomputed through the same corrected, answerability-conditioned scorer. Their instance set differs from the paper's, so these positions cannot be quoted as the published leaderboard.
The recomputed GPT-4o baseline scores 0.5591. Holding the prompt fixed, replacing ELSER contexts with RE-call contexts changes 0.5516 to 0.5527. Correct refusals are tied with Llama-3.1-70B; that metric depends on the generator prompt as well as retrieval.
Retrieval Task A, a separate 777-query evaluation, reaches nDCG@5 0.4342 and Recall@100 0.7668 with SPLADE and Voyage reranking. The free hybrid SPLADE arm scores 0.3573 and 0.7377 respectively. Task B supplies gold contexts and is a harness control, not a RE-call retrieval result.
-
LoCoMo
Long conversation memory
Paired QA · 1,540 answerable questions
- Result
- 48.4%
Judged answer accuracy
Mem0 OSS: 44.4% in the same setup
- Position
- Ahead in paired test
RE-call versus Mem0 OSS, with matched reader and judge. No official placement.
- Verification
- Self-tested
Public compact artifact
A second scoring script is not a third-party rerun.
Method, limits and sources
GPT-4o reader and judge, token-matched retrieval budgets. RE-call uses the local bge embedder. The direction depends on the reader: a post-hoc Sonnet 4.5 subset reverses it. The paired artifact records the raw-run hashes; raw generated answers are not committed.
Separate retrieval-only tests use 1,536 answerable questions: turn-level hit@5 is 0.671 without reranking and 0.777 with the shipped cross-encoder. These are not session-level competitor scores or judged answer accuracy. Default retrieval abstained on none of the 446 adversarial questions; that failure is retained in the record.
-
LongMemEval
Session retrieval
Historical local-embedder study
- Result
- 0.970 / 0.366
Hit@5, small / merged haystack
Retrieval only, not answer accuracy
- Position
- Unranked
Different haystack scopes; no comparable official row.
- Verification
- Self-tested · historical
Original artifact lost
Documented result, limited auditability.
Method, limits and sources
The per-question haystacks contain roughly 49 sessions; the merged index contains 19,195. The intermediate Oracle scope scores 0.719. Knowledge-update retrieval is 36/36 on the comparable arm, while false abstention is 0.481.
This run predates the sparse-leg fix and is effectively dense-only. The indexes and original run output were not retained. The published commands provide a reproduction method, not a retained artifact or independent verification. A separate Bench'd harness run is recorded below.
-
BEAM
Long-context memory and abstention
Historical 1M-token probes
- Result
- Partial results only
Temporal category: 0.408
Mem0 reference: 0.567
- Position
- Unranked
No retained full-run aggregate suitable for a leaderboard claim.
- Verification
- Self-tested · historical
Published study notes
Incomplete retained evidence.
Method, limits and sources
The harness follows upstream answerer and judge prompts and compares against historical Mem0 Platform answers. The published temporal probe identifies wrong date selection. The source record does not retain a complete aggregate artifact, so this page does not assign an overall score or rank.
BEAM includes deliberately difficult unanswerable questions. Follow-up entailment and threshold probes did not establish a usable general abstention rule. The committed Voyage k-sweep measures nugget-coverage proxy, not judged answer quality.
-
BEIR / CQADupStack
Cross-corpus retrieval study
17 corpora
- Result
- 16 / 17
Corpora improved by cloud embeddings
Median hit@5 lift: +0.059
- Position
- No system ranking
Within-RE-call embedder comparison.
- Verification
- Self-tested
Public study summaries
Per-corpus artifact set incomplete.
Method, limits and sources
Hybrid retrieval with bge-small-en-v1.5 versus Voyage-3. This measures the embedder change within RE-call, not RE-call versus other retrieval systems. The corpus samples and configuration are part of the study; these figures are not official full-corpus BEIR nDCG scores.
The study and analysis summaries are public; the complete set of per-corpus run artifacts is not retained in this tree.
Corpora: NFCorpus, SciFact, SCIDOCS, FiQA, ArguAna, and CQADupStack Android, English, Gaming, GIS, Mathematica, Physics, Programmers, Stats, TeX, Unix, Webmasters and WordPress.
-
FinanceBench
Financial-document retrieval
150 questions
- Result
- 0.393 → 0.527
Hit@5 as the candidate pool grew
Pool 40 versus 100
- Position
- No system ranking
Within-RE-call configuration study.
- Verification
- Self-tested · historical
Published aggregate
No compact run artifact linked in the record.
Method, limits and sources
Voyage-finance-2, dense retrieval plus reranking over 72,151 chunks, with the dense search-width cap corrected. This is a retrieval-pool experiment, not the benchmark's end-to-end financial QA score.
-
agent-memory-bench
Coding-agent task execution
official-003 · 317 paired cells
- Result
- 65.93%
Task success
Bare: 65.93% · Placebo: 67.19%
- Position
- Tied 2nd, owner-run board
Among displayed arms by success. Null versus the designated baseline.
- Verification
- Self-tested
Benchmark by the RE-call author
Execution-graded; no independent operator.
Method, limits and sources
Claude Code with DeepSeek V4 Flash over a bulk-ingested corpus. No positive arm's confidence interval excludes zero against the designated CLAUDE.md baseline. RE-call ties the bare arm; placebo scores highest. This does not demonstrate an overall coding benefit.
The write lifecycle is not measured. The run disclosed late preregistration, no advance announcement, and source and condition names visible to agents. The current board joins later vendor runs with different admitted cell counts, so its descriptive order is not a controlled pairwise ranking. Earlier pilots and protocol runs remain in the linked history.
-
mem-bench
Isolation and temporal axes
Earlier author-built benchmark
- Result
- Historical runs
No current score promoted here.
- Position
- Unavailable
Former public repository returned 404 on 19 Oct 2026.
- Verification
- Self-tested · historical
Adapters retained
Declared versions were not live-verified.
Method, limits and sources
The retained documentation records earlier isolation and temporal runs. The original board's artifacts declared a version without confirmation; a declared version and deterministic scoring do not establish an independently verified run. The adapters are public, but the former board is not currently accessible.
Read the labels
Who ran it matters.
- Self-tested
- The RE-call author operated the run. An official evaluator, public artifact or signed manifest can make it auditable without making the operator independent.
- Organizer-listed
- The benchmark maintainer accepted a row onto its leaderboard. Acceptance alone does not establish that the organizer reran it.
- Independently verified
- A separate operator reproduced the run and published evidence. No result on this page currently has that status.
Positions apply only to the named metric, track, eligible rows and review date. A local baseline comparison is labelled local. Missing placements stay unranked.
The rest of the record
Other tests and historical runs.
This register covers published benchmark families. Configuration sweeps, diagnostic controls and earlier runs remain in their linked records. In-progress and unpublished competition results are outside this scorecard.
Bench'd harness: historical LoCoMo and LongMemEval runs
The August 2026 self-run release reports nuance scores of 71.6 on LoCoMo and 69.0 on LongMemEval. These use a different pipeline from the retrieval and paired QA rows above: Voyage embeddings and reranking, DeepSeek synthesis inside memory, and the harness's locked GPT-4o-mini answerer and judge. Abstention was suppressed on the answerable-only evaluation.
The manifests are signed by the submitting operator. They were not accepted onto a public board and were not independently rerun. No rank or independent-verification claim is made from them.
Signed manifests and run records · Harness protocol and disclosures
Internal agent A/B, answerability and trust evaluations
- Additive agent A/B: known-hazard trap rate 0.000 with RE-call versus 0.525 with the same static memory alone, over 40 memory-only pairs. This author-designed task set is narrow and is not a public coding leaderboard. Artifact and limits.
- SDK replication: a separate in-process tool replication was inside its preregistered equivalence bands. It was still run by the author. Replication artifact.
- Answerability ladder: diagnostic levels and the corrected H1 verdict are retained, without a leaderboard position. Corrected verdict.
- Trust, supersession and entailment: synthetic controls and near-miss studies test particular failure modes. Generated-corpus success is not a production reliability rate. Full result tables · Study.
- Reasoning controls: frozen offline control and ablation suites, distinct from externally graded reasoning benchmarks. Audit and release limits.
PEPs, real-corpus, fine-tuning, scale and latency studies
The author also tested PEP retrieval, labelled private-corpus retrieval, embedding fine-tuning, synthetic scale, reranking, cosine distributions, generation parity and store latency. These measure individual mechanisms or operating costs. They do not assign a place among competing memory products.
Only published aggregates are linked here. Private corpus text and raw operational traces are not part of this page. All of these studies are self-tested.
Corrections and withdrawn figures
Withdrawn measurements are excluded from the scorecard. The linked record preserves the corrections, including contaminated LoCoMo pool runs, an invalid known-item evaluation, and ATM metric and token-accounting errors. Historical figures with lost artifacts remain explicitly labelled above.
