Compiled 2026-09-06 from the three research digs (Mem Think, Mem Compare Int, Mem Compare Ext). Same ideas as the short ping, spelled out so anyone can follow.

Source dump: ‣


Big picture

Context compiler (not a "memory drawer")

What it means: Most products treat "memory" like a filing cabinet: stuff facts in, pull some back later. What you've been designing is closer to a compiler: raw history is the source code; a short "what matters right now" page is the build output that goes into the prompt; rules about how that page is built are the build config.

Why it matters: Filing cabinets optimize for storage and search. Compilers optimize for a stable, checkable output. For a long-running agent, the expensive part is the prompt — so the win is "what the model sees is deliberate and auditable," not "we stored more stuff."

Kitchen analogy: The diary of everything that happened is the pantry. The short note on the fridge is what you're cooking with today. You don't throw out the pantry when you rewrite the fridge note.


Cascading Context Cache (CCC) / Cascading Context Sheet (CCS)

What it means: House-wide facts should be written once in the shared place and cascade down to every bot. A single bot's private notes can override when needed — but they shouldn't quietly copy a house rule, because then the copy blocks the cascade and the house version can never update for that bot.

Why it matters: The dig found CCC is already leaking: house rules live in multiple places, and some bots' private profiles contain "House rule" lines that shadow the shared ones. Enforcement (a real sheet / mechanism), not just a slogan, is the fix.


Focus / mouth (the filter layer)

What it means: The "mind" can know a lot. The mouth is a last-second check before anything is said or sent — always / never / danger / caveat rules that should not fade just because the chat got busy.

Why it matters: Dig found this is 100% design, 0% code today. Standing rules currently sit in the same pile as clip notes and an address, so they can get pushed off the page like any other fact.


From Mem Think

"Why is this line in my prompt?" (make this Phase 1 #1)

What it means: For every line the model sees, you should be able to answer: which rule pulled it in, what it overrode, and why it's still there.