Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-07-16 · high
Conflate the two, per Weng's new catalog, and changing your memory policy means rewriting the memory itself.
Why now: Weng posted the framework on July 4, and it's still the single most portable idea to come out of a catalog that covers far more ground.
Lilian Weng's new catalog on context engineering splits agent memory into two layers: the mechanism that manages it and the content stored inside. That split decides whether a team can change what an agent forgets, summarizes, or keeps, without tearing down the whole memory system to do it.
Weng calls this bi-level structure, what she labels Meta Context Engineering, the most portable idea in a catalog that covers a lot more ground, per the post. Most teams don't build it that way. They wire the memory policy straight into the data structure holding the memory, so mechanism and content end up as one piece of code from day one.
The catalog doesn't say how many production agent systems already have this coupling. It just says the fix has to happen before there's data sitting in the memory to migrate.
Skipping this split doesn't save time, it just moves the rewrite from before you have data to after, when it costs more. Watch for teams that call that rewrite a refactor.
Each link below shares sources, entities, or timing with this story.
Shared entity: Most / Shared topic / Earlier coverage / Tension
Both cover Most; overlapping topics (engineering, mechanism); earlier Most coverage from 2026-06-14.
Shared entity: Separate / Shared topic / Earlier coverage / Tension
Both cover Separate; overlapping topics (agent, data); earlier Separate coverage from 2026-02-26.
Shared entity: Weng / Same source
Both cover Weng; cite the same source (Weng's catalog).
Shared entity: Most / Shared topic / Earlier coverage
Both cover Most; overlapping topics (agent, context, engineering); earlier Most coverage from 2026-06-26.
Both cover Most; overlapping topics (agent, data, their); earlier Most coverage from 2026-06-12.
Both cover Most; overlapping topics (agent, memory); earlier Most coverage from 2026-07-12.
Both cover Most; overlapping topics (agent, data); earlier Most coverage from 2026-06-26.
Shared entity: Separate / Shared topic / Earlier coverage
Both cover Separate; overlapping topics (agent, memory); earlier Separate coverage from 2026-06-24.