Three places to keep knowledge
Hermes has persistent memory for compact facts and preferences, project context files for instructions, and session search for retrieving past conversations. A durable project folder can hold the detailed evidence those small orientation layers point toward. These serve different purposes; placing a document in one does not automatically make it available everywhere.
Our recommended arrangement is to keep the project location and a few lasting conventions in memory, operating instructions in the project context, and decisions, sources and outputs in ordinary files. For a research project, memory might identify the project folder while a decision record explains why a source was accepted. That keeps the evidence inspectable when a summary becomes stale.
Design a recovery check
Choose one fact that matters next week: the accepted output location, the owner of a decision, or the latest approved brief. Ask a fresh session to find it and cite its record. A successful answer should explain where the fact came from and distinguish accepted decisions from proposals. If it cannot, improve the record or its discoverability before adding more material.
Keep dates and supersession notes with changing decisions. A saved statement that a service was healthy yesterday should lead to a fresh check today; it should not become permanent proof of health. Avoid storing raw logs or credentials in an orientation note.
Scope and limits
The current documentation describes profile-specific memory and a snapshot loaded at session start. Verify the active profile when comparing sessions. This guide explains an information-management pattern; it does not establish that your installation has written, loaded or recovered a particular memory successfully.
Primary sources
Spotted something wrong or out of date? Tell us on X at @HermesWatcher (opens in a new tab) and we will fix it.
New Hermes Agent updates every day on X. Follow @HermesWatcher