You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on anothe
8000
r tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Epic: consolidate vector store and local SQLite onto Turso (retire Qdrant Docker) #49
Move everything into Turso so we no longer need a separate vector store (Qdrant, which runs in Docker) and so the SQLite stores used by Mission Control / Inkie Deck run through it too.
Why
Qdrant in Docker is a poor fit for an installable product, and hard to back up.
A SQLite-style database is a single file/blob that is easy to back up and move.
One store for brain memory (recall), Deck state and queues.
What does migration from Qdrant look like (collections, payload indexes, embeddings re-use, dual-write/cutover, rollback)?
Backup/restore story, Windows installer fit (no Docker), embedded vs server mode, maturity/licence.
Can the existing recall CLI (the-brain search) and Deck SQLite usage move behind one interface?
Status
Research brief only. Tooling freeze applies: spec and hand over, do not build. A Sol research worker has been asked for a findings note.
Origin
Migrated from Linear: INK-985. The original wording is retained except the disclosed privacy and rendering edits below.
Current scope and qualifications
The description above is the original Linear account, including its historical findings and scope. It is not a fresh claim that every described defect still exists.
Current Linear state is Backlog. Prior source review recorded uncertain, with this remaining scope:
Review complete research findings and settle store decision; keep Deck dependency explicit.
Publication transfers the task; it does not authorise live recovery, deployment, spending or configuration changes.
Additional transfer edits: omit added excluded programme references.
Activity