docs: record the separate data directory (ADR-0011)
Add ADR-0011: the community edition defaults to ~/.waggle-community, a temporary name that follows the product-name decision (Q8), and copies nothing from the commercial ~/.waggle. It supersedes point 4 of ADR-0009 and closes the pending "separate data directory" decision. Update the install guide, troubleshooting, capabilities, memory, architecture, the Windows build notes, THREAT_MODEL, README, .env.example and the changelog. Log UF-068 (Open): marketplace skills and plugins ignore a custom data directory.
This commit is contained in:
@@ -39,11 +39,14 @@ lists what changed for users compared with that product. The reasons are recorde
|
||||
### Changed
|
||||
|
||||
- **Memory runs on local mem0** behind a memory contract (ADR-0002, ADR-0007). Memories are kept
|
||||
in `~/.waggle/memory/`, embedded by a model that runs on your computer, and searched with
|
||||
in `~/.waggle-community/memory/`, embedded by a model that runs on your computer, and searched with
|
||||
mem0's combined vector and keyword search. Nothing goes to a cloud memory service. Memories
|
||||
from the old `.mind` files are not carried over. See [docs/memory.md](docs/memory.md).
|
||||
- **Waggle's own data** (automations, notifications, cost tracking, your profile card and task
|
||||
list) moved to a separate `waggle.db`, apart from memory.
|
||||
- **The data directory is `~/.waggle-community`** (ADR-0011), so the community edition never
|
||||
opens the databases of the commercial Waggle in `~/.waggle`. Nothing is copied from
|
||||
`~/.waggle`; set `WAGGLE_DATA_DIR` to use another directory. The name is temporary.
|
||||
- **Analytics are opt-in** (ADR-0006). Waggle asks once; nothing is sent until you choose
|
||||
**Allow**, and Settings → General → Privacy & Telemetry turns it off again. When allowed,
|
||||
Waggle sends one event at the end of setup with the template, persona and model you chose.
|
||||
|
||||
Reference in New Issue
Block a user