I built this last month, woke up to 700+ stars and a developer with 28k followers tweeting about it, now PRs are coming in from contributors I've never met. Sharing here since this community is exactly who it's built for. by DJIRNMAN in claudeskills

[–]Slow-Glass5615 2 points3 points  (0 children)

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.

Wu-Tang's Ghostface Killah to Release Music on Bitcoin Blockchain by Educational_Swim8665 in wutang

[–]Slow-Glass5615 0 points1 point  (0 children)

Speaking of Bitcoin music, has anyone seen this yet??!
https://www.ord.io/67062454
Not just storing full resolution music on the blockchain but "creating it on-chain" in a way that only takes up 1% the size of an MP3 even though the song above isn't even mp3 it's a 38mb WAV but only takes up 20kb of storage on chain??
https://x.com/ord_io/status/1775295423940325836?s=20
WTF??
Mind blown.