Skip to results
RE-callEvidence
English source

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.

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.

Result tables · Artifact map · Fine-tuning study

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.

Withdrawal register · Findings and corrections