{"item":{"id":"wf-memory-check","product":"hermes","language":"en","title":"Check that a memory update changes the next session","summary":"The checked documentation separates profile-local files, staged writes and the frozen session-start snapshot. Verify a correction with a saved record and a fresh-session action. Model behavior remains untested.","contentType":"guide","category":"workflow","revision":7,"canonicalUrl":"https://botclaw.tech/items/wf-memory-check","sourceUrls":["https://hermes-agent.nousresearch.com/docs/user-guide/features/memory"],"sourcePublishedAt":"2026-10-01T13:51:23.773Z","reviewedAt":"2026-10-02T08:27:29.747Z","collectedAt":"2026-10-01T13:51:23.773Z","updatedAt":"2026-10-29T20:00:21.744Z","source":{"id":"botclaw-editorial","name":"BotClaw","origin":"editorial"},"summaryMethod":"editor","applicability":{"version":"Hermes memory documentation snapshot, 2026-10-02; runtime untested","platforms":["Supported Hermes host"],"requirements":["For execution: a working model and one disposable profile used for every test session"]},"verification":{"kind":"official_documentation","checkedAt":"2026-10-02T08:01:48.994Z","urls":["https://hermes-agent.nousresearch.com/docs/user-guide/features/memory","https://botclaw.tech/evidence/round1-sources.json"],"limitations":["Documentation snapshot only; no Hermes executable version or model behavior was tested.","A saved file, staged write and fresh-session action are separate acceptance checks."]},"body":{"introduction":"Use a disposable Hermes profile. This is a reviewed test protocol, not a successful memory experiment: the first round checked the documentation and its source hash without running a model.","sections":[{"heading":"Write, correct, reopen","paragraphs":[],"steps":["Ask Hermes to save a fictional preference: for sample reports, use blue headings. Check the memory tool result or the actual saved record.","In a new session, request a sample report and check whether the preference influences its output.","Correct the preference to green headings and require the obsolete blue preference to be replaced or marked superseded.","Use /new and repeat the task. Verify both the stored correction and the next action. Remove only the disposable test record afterward."]},{"heading":"Check the effective store and session","paragraphs":["Read MEMORY.md and USER.md under the same profile used by the agent. A write awaiting approval has not reached that store. Memory is injected as a frozen snapshot at session start: restarting a messaging gateway can resume the old session, so use /new after the correction. Do not approve unrelated pending writes."]},{"heading":"Record each verdict","paragraphs":["Keep the profile identifier, write result, superseded entry, fresh-session boundary and observed report choice. Mark each as pass, fail or not run. In this round the two live document checks passed with unchanged hashes; persistence, correction propagation and Agent action are all not run."]},{"heading":"Common failures","paragraphs":["If the preference appears only before /new, inspect whether it was saved at all. If old and new preferences coexist, resolve the conflicting record and test a fresh session again. Do not reset a real user memory store to make the test pass."]}]},"indexable":true,"supersededBy":null,"review":{"state":"pending","pendingChanges":3,"policyDays":7}}}