Estratos

Your first memories

With a hierarchy in place, you're ready to fill it in. A memory is a Markdown note attached to your hierarchy. You can write memories two ways — in the app, or by letting an agent store them mid-conversation over MCP — and they land in the same place either way.

Two kinds of memory

Every memory is one of two kinds. Choosing between them is the main decision you make on each write:

  • Scoped — attached to one folder, by its path. Use it for knowledge that belongs to a single scope. "Pennine Joinery is on the VAT flat-rate scheme" lives at root.pennine-joinery.vat.
  • Tagged — attached to a whole layer, optionally to one segment value. Use it for a rule that should apply in many places at once. "How the firm formats working papers" attaches to the services layer and applies across every service.

A quick test: if the note is about one specific thing, make it scoped. If it's a standard, policy, or convention that should apply wherever a condition holds, make it tagged. The scoped vs. tagged guide goes deeper with more examples.

Writing a memory in the app

Open Memories › Scoped in the sidebar. Browse the folder tree, pick the folder you want, and add a memory: give it a title and write the body in Markdown. For tagged memories, use Memories › Tagged, pick the layer (and optionally a value to target), and write it there.

You never invent a storage key — Estratos derives a stable key from your title and the scope. Titles are short, specific noun phrases (for example, "VAT registration threshold for new clients").

Letting an agent capture a memory

Once you've connected an agent, you can just tell it to remember something:

"Remember that this client is on the VAT flat-rate scheme, under their VAT service scope."

The agent calls the remember tool with the path and the note. It generates the title itself from the content, and the server derives the key and resolves the path. Tagged works the same way through remember_tagged. See the MCP reference for the full tool contracts.

What happens when you (or your agent) write

Where a memory goes depends on your role:

  • If you're an Owner or Admin, your write publishes immediately.
  • If you're a Basic user, your write becomes a proposal. It's usable by you and your agent right away, but stays invisible to everyone else until an approver signs off. This is the review workflow, and it works identically whether you typed the memory or your agent wrote it.

Reading it back

To confirm a memory landed, ask an agent to retrieve the scope:

"Pull up everything we know about the Pennine Joinery VAT engagement."

The agent calls retrieve with the path and gets one Markdown bundle: the scoped memories at that folder plus the tagged rules that apply, in a fixed order. In the app, the scope's memories are listed on the folder itself.

Next steps