refactor: drop the one-time copy of legacy .mind data

The first start copied Waggle's tables and the memories of the commercial
edition's .mind files into waggle.db and mem0. The product is still in
development and nobody has data to bring over, so both copies, their tests
and the legacy creation-time field are gone. ADR-0007 records the change.
This commit is contained in:
shumeiko.it
2026-10-28 12:35:41 +01:00
parent fb3697ca6c
commit a8250cb375
12 changed files with 15 additions and 618 deletions

View File

@@ -1,7 +1,7 @@
# ADR-0007: The memory contract and how it maps onto mem0
- Status: Accepted
- Date: 2026-10-18
- Date: 2026-10-18, amended 2026-10-28 (no copy of legacy data)
## Context
@@ -89,11 +89,10 @@ The stores of these tables take a `WaggleDB`, not a generic SQLite handle, so ha
memory database is a type error. Telemetry (`telemetry.db`) and the audit log (`audit.db`)
already had their own files and stay there.
On the first start the server copies these tables from the legacy `personal.mind`, and the
profile and awareness items of every `workspace.mind`, into `waggle.db`
(`importLegacyMindData`). The legacy files are only read, because the data directory may be
shared with the commercial edition; each scope is copied once (recorded in `waggle_meta`) and a
table only while its target is empty.
Nothing is copied from the `.mind` files of earlier versions. Until 2026-10-28 the first start
copied these tables and the legacy memories (`importLegacyMindData`, `legacy-memory-import.ts`);
the owner removed both because the product is still in development and nobody has data to
bring over. A data directory left by the commercial edition is ignored.
The logger, injection scanner, external-memory ingress guard, `WorkspaceManager` and the
embedders were copied from `@waggle/hive-mind-core` into `@waggle/core`, which exports its own
@@ -117,11 +116,6 @@ copies is part of the licensing review.
model through the built-in OpenAI-compatible proxy (or LiteLLM when the user runs it)
and reads the user's current model on every call. `memoryExtraction` in `config.json`
turns it off (default on). Failures are logged and never block a turn.
- **Legacy memories** are copied once into the store in the background
(`legacy-memory-import.ts`). The `.mind` files are opened read-only. Content prefixes
become kinds, `[mind-rawturn …]` frames and deprecated frames are skipped, the original
creation time is kept in `metadata.legacy_created_at` because mem0 sets its own. Progress
is kept per scope in `waggle_meta`, so an interrupted copy resumes.
- **Writers.** Chat write-back, compaction summaries, sub-agent and agent-run results
(`run-memory.ts`), loops, connector fetch, indexed workspace files and the failed-turn
capture all call `remember`. Contract field names are reserved in metadata; agent-run
@@ -136,8 +130,8 @@ copies is part of the licensing review.
a seventh of the latency. The reranker did not improve mem0's ranking and costs about
130 ms per search, so it stays off. The benchmark keeps running against mem0 alone after
the old engine is removed.
- **Waggle data moved to waggle.db** as well: the install audit trail (`install_audit`,
copied from `personal.mind` with the other personal tables) and the file index
- **Waggle data moved to waggle.db** as well: the install audit trail (`install_audit`)
and the file index
(`file_index`, keyed by scope and path, pointing at memory ids; files are re-indexed on
their next write rather than migrated).
- **Removed with the old engine:** the weaver package (consolidation, decay, transcript

View File

@@ -93,8 +93,7 @@ app\src-tauri\target\x86_64-pc-windows-msvc\release\bundle\nsis\Waggle_0.2.0_x64
`%USERPROFILE%\.waggle\logs\service.log`.
4. Chat needs a model: an API key in Settings → API Keys, or a running Ollama.
Waggle keeps its data in `%USERPROFILE%\.waggle`. If the commercial edition was used on this
machine, the first start copies its data once and leaves the old files unchanged.
Waggle keeps its data in `%USERPROFILE%\.waggle`.
## Troubleshooting