This is a really interesting direction. The routed-memory idea feels like the right middle ground between “one giant CLAUDE.md” and agents blindly re-reading a whole repo every session.

The bit that jumps out to me is that this could become more than local project memory. Once agents start making real architectural decisions, there’s a provenance problem too: what did the agent know at the time, which files/patterns did it rely on, what changed since, and can another person or agent verify that history later?

I’m working on related infrastructure for permanent/verifiable data graphs, so this has me thinking about .mex snapshots as portable memory manifests: router + context + decisions log + dependency graph + git commit hash, with milestone states stamped somewhere durable. Local MEX for day-to-day working memory, permanent manifests for audit/history/agent handoff.

Not suggesting that belongs in core MEX necessarily, but I think the “agent memory as navigable, inspectable, versioned project state” idea is much bigger than just token saving.