Architecture

No model runs over your memories.

Nothing you send is rewritten, and the engine is cheap, fast and deterministic. A model is never run over your stored memories. Tablet uses no model at all; Scroll and Book add one around the engine for stronger results, but it only ever sees your query, never what you stored.

  • Deterministic engine. The engine returns the same memories for the same query, every time - which is why our benchmark variance comes only from the reader model.
  • Cheap at scale. No generation cost to store or retrieve, so your bill tracks storage - not model usage - as memory grows.

Your words, untouched

One common design runs a language model at write time to extract and rewrite "facts" from the text. That design trades three things: generation cost on every write, added latency, and storage of a model's paraphrase rather than the original words. WOS makes the opposite trade - it does not rewrite what was said, and lets your LLM do the interpreting at read time with the original text in hand.

What WOS is not: not infrastructure you have to run, and not a framework you have to assemble. It is a hosted API you call. No model is ever run over your stored data. Scroll and Book do use a language model for stronger results, but it only ever sees your query, never your stored memories - and it never trains on your data or collects it.