Memorist — an auditable, local-first memory engine for Open WebUI
Long-running LLM work loses continuity: decisions, corrections, and constraints evaporate between sessions. Most fixes summarize old chats into a hidden prompt — invisible, unauditable, easy to poison.
Memorist takes a different position: raw messages are evidence, not memory. Every message is preserved unchanged in a local ledger. Deterministic sentence segmentation produces units with exact character offsets, so every memory claim traces back to the exact words that produced it. A memory is a versioned, evidence-linked claim that must earn recall through gate, routing, trust, and consolidation stages. Open WebUI stays the parent chat product; Memorist owns capture, processing, retrieval, and privacy workflows beside it.
Repo: https://github.com/doctordocto159753/open-webui-memorist-edition
Where it stands: the core event-sourced engine and processing flow work and are tested. The semantic routing layer is designed but not fully wired into the candidate pipeline yet, and the UI/UX needs real frontend work — I've prioritized correctness of the engine over polish.
Who I'm looking for: a frontend/UX contributor (Svelte, Open WebUI integration), and anyone interested in benchmarking whether structured memory actually improves long-conversation quality — that's the core research question. I'm a product manager by background (literature → theater → humanities theory → fintech PM), and this project is where those domains meet engineering. I'll own product design, specs, and testing coordination; I need engineers who want ownership of their layer.
Starter issues are labeled in the repo. Comment here or open a discussion if interested.

A text incapable of explaining me: I started with literature {a science fiction lover}, I studied art and theater, then a little bit of humanities theory, then I became a product manager, then I got involved in networking concepts; and during this time, I prototype my ideas with artificial intelligence. In these projects, I tried to connect different domains that were from humanities and arts, engineering and product management, and my experiences.

Memorist — an auditable, local-first memory engine for Open WebUI
Long-running LLM work loses continuity: decisions, corrections, and constraints evaporate between sessions. Most fixes summarize old chats into a hidden prompt — invisible, unauditable, easy to poison.
Memorist takes a different position: raw messages are evidence, not memory. Every message is preserved unchanged in a local ledger. Deterministic sentence segmentation produces units with exact character offsets, so every memory claim traces back to the exact words that produced it. A memory is a versioned, evidence-linked claim that must earn recall through gate, routing, trust, and consolidation stages. Open WebUI stays the parent chat product; Memorist owns capture, processing, retrieval, and privacy workflows beside it.
Repo: https://github.com/doctordocto159753/open-webui-memorist-edition
Where it stands: the core event-sourced engine and processing flow work and are tested. The semantic routing layer is designed but not fully wired into the candidate pipeline yet, and the UI/UX needs real frontend work — I've prioritized correctness of the engine over polish.
Who I'm looking for: a frontend/UX contributor (Svelte, Open WebUI integration), and anyone interested in benchmarking whether structured memory actually improves long-conversation quality — that's the core research question. I'm a product manager by background (literature → theater → humanities theory → fintech PM), and this project is where those domains meet engineering. I'll own product design, specs, and testing coordination; I need engineers who want ownership of their layer.
Starter issues are labeled in the repo. Comment here or open a discussion if interested.

A text incapable of explaining me: I started with literature {a science fiction lover}, I studied art and theater, then a little bit of humanities theory, then I became a product manager, then I got involved in networking concepts; and during this time, I prototype my ideas with artificial intelligence. In these projects, I tried to connect different domains that were from humanities and arts, engineering and product management, and my experiences.

Memorist

An auditable, local-first memory engine for Open WebUI

An auditable, local-first memory engine for Open WebUI