TheoSphere has crossed an important feasibility boundary. A private appliance can preserve a substantial memory, retrieve a bounded evidence set, brief a local model, validate citations, and show the owner a decision trace.
One qualification run produced a grounded local answer with validated sources. A later response drifted from the required citation format; the system rejected it and returned a deterministic cited fallback. Refusing an attractive but invalid answer is part of the product.
A compelling future is not evidence that the future has already shipped.
The status ledger
The public website now separates demonstrated capability from active development and product roadmap. That distinction will move with the build receipts, not with enthusiastic conversation.
The current Bob and model-control-room work is a source candidate and synthetic shadow. It does not yet mean customer-ready provider routing, tools, autonomous work, or a shipping appliance.
Why the boundary matters
A memory system will eventually hold material that matters deeply to its owner. Trust cannot be built from words like private, sovereign, or intelligent alone. It has to be earned through permissions, receipts, restore tests, safe failure, and visible limits.
The goal is ambitious. The reporting can still be exact.