Vol. I · No. 1Edition: MorningEst. 2026AboutSearchRSS

The Sand Paper

Finding grains of sand with grains of sand.
A Journal of Intelligence Transfer
Models & Hardware

MemT 1.0 Keeps What You Teach It Inside the Model, @sudoingX Finds

He saved its memory to a 42 MB file, restarted, and it still followed his Rust house rules.

A model that writes what you tell it into its own memory state, then keeps it across restarts.

MemT 1.0, from the @MemOS_dev team, writes what you tell it into a memory state inside the model for later answers, @sudoingX explains, while the current message still goes in the context window.

He ran it in bf16 on his 128 GB Strix Halo. In the first session he gave it his Rust house rules and one lesson: one error enum called BeastError, no unwrap and the ? operator everywhere, and a missing config must never crash but fall back to defaults with a warning.

He saved its memory to a 42 MB file, killed the process and started a new one from that file. With the same weights, that memory and zero messages in context, he asked for a config loader. It used BeastError on every error path, ? everywhere with no unwrap, and defaults plus a warning for a missing file.

StepWhat happened
Session 1Taught the Rust rules and one lesson
SaveMemory written to a 42 MB file; process killed
Session 2New process, 0 messages in context
ResultConfig loader followed every rule
From @sudoingX’s post.

A bigger 288B version is built on DeepSeek V4 Flash, and the weights are open for both, he says. He posted links to the nano and flash weights and to the code and paper.

Sources

  1. @sudoingX on X · Oct 22, 5:02 AM PT
  2. @sudoingX on X · Oct 22, 5:02 AM PT
Back to front pageMore in Models & Hardware