Research notes · This week
From the Jul 18, 2026 daily brief
Oracle, in a 13-author technical report on July 14, builds agent memory as a database-native substrate: memory managed as a full lifecycle — extraction, consolidation, retrieval, pruning — self-reporting 93.8% on the long-term-memory benchmark LongMemEval while using about 10.7x fewer tokens than stuffing the entire history into the model (arXiv, Jul 14). A UCLA-affiliated team's July 15 method, MemCon, points out that in existing systems "when to read, when to write" is almost entirely hand-coded rules; they turn that decision itself into an online-learned policy, self-reporting success-rate gains of up to 15.2 percentage points. That figure is the ceiling across a grid of 6 benchmarks, 3 agent frameworks, and 3 model backbones rather than a typical average (arXiv, Jul 15). Both are team-self-reported with no third-party reproduction. For anyone building an agent platform, a useful decomposition: "where memory lives" and "who decides when to read and write it" are two independent decisions — the database giants just entered the first, and the second is only just starting to become tunable.
Just an email address, unsubscribe anytime. This is the only thing we ask of you.
The current mainstay of post-training (the stage after base training where a model is taug…
In the same AMD assessment, SemiAnalysis reports firsthand engineering observations: 2.5 e…
The Jacobian conjecture, posed in 1939, is a famous problem in algebraic geometry. It says…
Our July 21 Research Notes covered this empirical study (gains from optimizing an agent pi…