AI makes mistakes! Undisk makes recovery instant: every write is versioned, every file is reversible.
See it heal →
This pattern lets teams keep consistent operational memory even when different clients participate in the same workflow.

Design principles

  • Use stable path conventions for shared state.
  • Separate ephemeral scratch outputs from canonical memory files.
  • Apply read/write scopes per client class.

Practical workflow

  1. Define canonical memory files under a shared namespace.
  2. Route client writes through explicit policy boundaries.
  3. Review diffs before promoting scratch state into canonical memory.

Example tool sequence

write_file(path="memory/notes/today.md", content="...")
list_versions(path="memory/notes/today.md")
get_diff(path="memory/notes/today.md", from_version="ver_prev", to_version="ver_new")
Coming soon: cross-client brain templates for engineering workflows.