Memory

Not Rest Inc. · Capabilities · Files you can open, not state you must trust

Ask most AI products what they remember about you and you get a shrug wrapped in a settings page. Memory, done honestly, has a different shape: it's written down, in files you can open, read, correct, and take with you. Not hidden vectors in someone's database — documents. If you can't read your memory, it isn't yours.

How our own systems remember

The not.rest session harness — open at github.com/notrestai/notrest — makes working sessions continuous through an estate of plain files: a foundation document that holds what's always true, an append-only ledger that records every piece of work as it lands, machine-written records of every delegated agent, and handoff files a successor session resumes from. Two bookends make it continuous: intake loads the foundation at session start; session-end updates it before stopping. A session can die at any moment and nothing of substance is lost — because the memory was never in the session. It was in the files.

Two properties do the heavy lifting

Append-only: ledgers are added to, never rewritten — the record can be trusted precisely because it can't be quietly edited. Readable: every memory artifact is plain text a human can open — which means memory can be audited, corrected, and owned in the only sense that matters.

Even this website practices the discipline at its smallest scale: a visit's journal is per-visit, anonymous, and short-retention — declared publicly in the site's own contracts at /agents/index.json, where you can read what is kept and for how long, instead of taking our word for it.

Memory is the capability everything else compounds on: agents need it to be accountable, skills need it to improve, sessions need it to continue. So we build it the way anything load-bearing should be built — where you can see it.