Skip to content
OpenTrain AIFor AI Companies

HFEPX · Eval paper review

MMLA: How Memory Lets the Past Shape the Future

Junyi Zou, Avrova Donz

Published

Jun 27, 2026

Citations

0

Trust level

Low

Usefulness score

0/100 (Low)

Extraction confidence

35% (Low)

Derived from extracted protocol signals and abstract evidence.

Rater population

Not reported

Signals refreshed

Aug 12, 2026

Should you rely on this paper?

This paper is adjacent to HFEPX scope and is best used for background context, not as a primary protocol reference.

Use this as background context only. Do not make protocol decisions from this page alone.

Best use

Background context only

Use if you need

A secondary eval reference to pair with stronger protocol papers.

What to verify

Validate the evaluation procedure and quality controls in the full paper before operational use.

Main weakness

This paper looks adjacent to evaluation work, but not like a strong protocol reference.

Human feedback signal
Not explicit
Not explicit in abstract metadata
Evaluation signal
Detected
Eval setup described
Usefulness for eval research
0/100
Adjacent candidate

Treat as adjacent context, not a core eval-method reference.

Abstract

Proposal. Long context can replay history, but it does not decide which completed observations deserve authority. MMLA formalizes a bounded resident memory between transient context and slow weight updates. A completed local segment is eventized; for each event, a target-conditioned constructor proposes semantic content and a trusted assembler produces a complete versioned row; deployment either commits that row atomically or returns NULL. Realized futures may price actions during training, while deployment remains causal and future-blind. Validated components. Controlled studies establish narrower ingredients. Lifecycle execution is exact on 300/300 held-out records for each of three seeds. Calibrated selection with full-archive fallback improves over a weak budget-matched dense baseline by 5.5--16.6 F1 and over BM25 by 4.0--6.2 F1 on held-out multi-hop QA; the original Llama budget execution is retained as failed, while the corrected Qwen packer satisfies the stated per-record caps. Typed anchor--filler transport reaches 240/240 held-out exactness per seed while three same-checkpoint controls obtain 0/240 whole-record successes. Current blocker. The integration loop is not complete. Dense-row, structured-span, and checkpoint-native readers trained from V28, the frozen 352.3M-parameter model-only checkpoint produced by a 50.0M-token native-scaffold pilot, all fail semantic qualification across three seeds. Candidate exactness is 0--45/23,040, query exactness is 10--1,536/9,216, and record-macro Brier remains near the 1,025-class uniform reference. Structural mapping passes, but none of the nine jobs qualifies. Predictive overwrite is therefore closed by gate.

What we could verify

These are the protocol signals we could actually recover from the available paper metadata. Use them to decide whether this paper is worth deeper reading.

Human Feedback Types

missing

None explicit

No explicit feedback protocol extracted.

"Long context can replay history, but it does not decide which completed observations deserve authority."

Evaluation Modes

partial

Automatic Metrics

Includes extracted eval setup.

"Long context can replay history, but it does not decide which completed observations deserve authority."

Quality Controls

missing

Not reported

No explicit QC controls found.

"Long context can replay history, but it does not decide which completed observations deserve authority."

Benchmarks / Datasets

missing

Not extracted

No benchmark anchors detected.

"Long context can replay history, but it does not decide which completed observations deserve authority."

Reported Metrics

partial

F1, Brier score

Useful for evaluation criteria comparison.

"Long context can replay history, but it does not decide which completed observations deserve authority."

Benchmarks and datasets

No benchmark or dataset names were extracted from the available abstract.

Reported metrics

f1brier score
Human feedback details
Uses human feedback
No
Feedback types
None
Rater population
Not reported
Expertise required
General
Evaluation details
Evaluation modes
Automatic Metrics
Agentic eval
None
Quality controls
Not reported
Evidence quality
Low
Use this page as
Background context only

Research brief

Metadata summary

Long context can replay history, but it does not decide which completed observations deserve authority.

Based on abstract + metadata only. Check the source paper before making high-confidence protocol decisions.

Key takeaways

  • Long context can replay history, but it does not decide which completed observations deserve authority.
  • MMLA formalizes a bounded resident memory between transient context and slow weight updates.
  • A completed local segment is eventized; for each event, a target-conditioned constructor proposes semantic content and a trusted assembler produces a complete versioned row; deployment either commits that row atomically or returns NULL.

Researcher actions

  • Compare this paper against nearby papers in the same arXiv category before using it for protocol decisions.
  • Validate inferred eval signals (Automatic metrics) against the full paper.
  • Use related-paper links to find stronger protocol-specific references.

Caveats

  • Generated from abstract + metadata only; no PDF parsing.
  • Signals below are heuristic and may miss details reported outside the abstract.

Recommended queries

Contribution summary

  • Calibrated selection with full-archive fallback improves over a weak budget-matched dense baseline by 5.5--16.6 F1 and over BM25 by 4.0--6.2 F1 on held-out multi-hop QA; the original Llama budget execution is retained as failed, while the…

Why it matters for eval

  • Abstract shows limited direct human-feedback or evaluation-protocol detail; use as adjacent methodological context.

Researcher checklist

  • Human feedback protocol is explicit

    No explicit human feedback protocol detected.

  • Evaluation mode is explicit

    Detected: Automatic Metrics

  • Quality control reporting appears

    No calibration/adjudication/IAA control explicitly detected.

  • Benchmark or dataset anchors are present

    No benchmark/dataset anchor extracted from abstract.

  • Metric reporting is present

    Detected: f1, brier score