A Skill File Can Carry Distilled Memory, Collapsing Two Sets of Retrieval Machinery Into One
Memory-Skill Isomorphism (arXiv 2609.16669, submitted 15 Sep 2026) argues that memory stores and skill stores duplicate the same routing, retrieval, reflection, and update machinery, and that a Skill is already a natural carrier for distilled memory under progressive disclosure: resident description holds hot cues at a governed 1,024-character budget, an on-demand file holds a colder index and curation policy, and reference/*.md files hold detailed memories. Writes fork, history appended and current state rewritten and revalidated. In a deployed system the sharpest finding was governance, 4 write entries existed but only 1 of 4 reached the settlement ledger, and one L1 lesson added 1,313 first-turn tokens against a 1,462-token baseline; the authors are explicit that the task-level improvement is a post-selection existence signal, not a confirmatory rate.
↳ Follow the thread