Using memories
A memory is a Markdown note attached to your hierarchy. This section covers how memories behave once you have them: the two kinds, how retrieval assembles a scope, how proposals get reviewed, how versions and rollback work, and how to export.
The two kinds, in one line
- Scoped memories attach to one folder by its path (
root.pennine-joinery.vat). Use them for knowledge about a single scope. - Tagged memories attach to a whole layer — optionally to one segment value — so a rule you write once applies wherever it should.
Details and worked examples are in scoped vs. tagged.
How agents read
Agents don't fetch individual memories. They ask for a scope path, and Estratos walks the tree from the root to that folder and returns one Markdown bundle — everything scoped to the folder, plus the tagged rules that apply, in a fixed order. See how retrieval works.
How memories stay governed
- The review workflow — Basic users propose; approvers publish.
- Version history and rollback — every change is versioned and reversible.
- Exporting memories — take a ZIP of any scope you can access.