DEV Community: Sofia

Bounded continuity is a product decision, not a memory claim

Sofia — Fri, 11 Sep 2026 16:21:32 +0000

When an AI conversation can continue later, the useful question is not “does it remember everything?” The useful question is “which contributions are intentionally preserved, and how can the user understand that boundary?”

Sofia V4.5 is a proprietary live platform for personal conversations with an AI. Confirmed conversation contributions can be preserved on an account-bound basis so a suitable earlier conversation can be resumed. This is bounded continuity rather than perfect recall.

That distinction matters for trust: explicit preservation is easier to reason about than an assistant that implies an unlimited memory. Sofia is not open source, and the live experience is available here: https://fragsofia.de/chat

A small design choice for AI conversations: continuity without pretending to remember everything

Sofia — Fri, 11 Sep 2026 15:53:58 +0000

When people talk about memory in AI products, the conversation often becomes binary: either the assistant remembers everything, or it remembers nothing. Sofia V4.5 takes a narrower and more legible route.

Sofia is a proprietary live platform for personal conversations with an AI. Confirmed conversation contributions can be preserved on an account-bound basis, so a suitable earlier conversation can be resumed. The important part is the boundary: this is not a promise of perfect recall, and it is not an open-source project. It is a product decision that makes continuity visible without pretending that every past detail is always available.

That distinction changes the interaction design. A returning user can pick up a meaningful thread instead of starting from a blank page, while the product can still communicate what is actually being carried forward. For conversational systems, that kind of clarity is more useful than vague claims about “human-like memory.”

Sofia V4.5 is live in the browser. If you want to try the experience, open https://fragsofia.de/chat and start a conversation.

Building an AI That Remembers Your Work Across Conversations

Sofia — Thu, 10 Sep 2026 09:26:05 +0000

When an AI assistant forgets everything between chats, the user has to become the system of record. That is fine for a one-off question, but it becomes frustrating when conversations are part of a longer project.

I am building Sofia around a simple product question: what if an assistant could remember the work around a conversation without pretending that every generated sentence is a fact?

The useful distinction: conversation, memory, and evidence

A durable assistant needs more than a longer context window. I separate three kinds of information:

Conversation state: what is being discussed right now.
Working memory: account-bound information that should remain useful across conversations.
Evidence: documents, workspace materials, and verified facts that can support an answer.

The separation matters. A previous conversation is not automatically proof. A remembered preference is not the same as a source. Keeping those categories distinct makes it easier to explain where an answer came from and when the system should say that it does not know.

A conservative retrieval flow

The high-level flow is intentionally boring:

Identify the user and the relevant workspace.
Retrieve candidate memories and materials.
Apply deterministic checks and permissions.
Prefer explicit facts and source-backed material over loose context.
Ask the language model to synthesize an answer from the approved context.

This keeps the model in the role of answer synthesis. It does not get to silently rewrite the source of truth. If the evidence is missing or contradictory, the assistant should surface that boundary instead of filling the gap with confidence.

Why account-bound memory changes the product

Memory only helps when it has the right scope. Personal context, project context, and shared workspace context should not be mixed by accident. The system therefore needs explicit ownership and continuation rules, not just a vector search endpoint.

It also needs lifecycle controls: users should be able to understand what is remembered, correct it, and decide what belongs in a workspace. Those controls are product features, not implementation details.

What Sofia is

Sofia is a web-based AI assistant designed for work that continues across conversations. It keeps relevant context available over time, helping users continue projects and conversations without repeatedly explaining the same background. Sofia separates remembered context from verified information, runs as a proprietary live platform, and is not open source.

Version 4.5 is live at fragsofia.de/chat. Sofia is free to use, with optional premium features.

I am sharing this as a work in progress because the interesting engineering questions are still open: how much memory is useful, how should users inspect it, and which checks provide the most value before synthesis?