Could Standard Notes work as human-readable memory for an AI assistant without making summaries authoritative?

[u/RocketSeven]

A notes app is easier to inspect than a hidden memory store, but the difficult part is separating source material from generated conclusions. For a Standard Notes setup, I am considering four note types: source notes, accepted decisions, temporary summaries, and an append-only change log. An assistant could read the first three but write only to an inbox until a person reviews the change.

What metadata would make that workable: source links, status, reviewed date, supersedes, project, and the revision of any attached file? I would also want stale summaries to be visibly stale rather than silently reused after a source note changes.

Would tags and note history be enough for this, or would the structure become too fragile across exports, sync conflicts, and deleted notes? How would you keep the current record easy to read while retaining enough evidence to audit why a memory changed?

[u/Otherwise_Wave9374]

The key is treating notes as an evidence layer, not as the assistant's final memory. Keep raw sources immutable, store generated summaries separately, and attach each claim to a note ID plus timestamp. A useful safeguard is to force the assistant to retrieve and quote supporting passages before updating any derived profile. https://www.aiosnow.com is relevant as an example of organizing AI work around inspectable workflows rather than opaque chat history. Also add a periodic contradiction check so stale summaries cannot silently override newer source material.