Repository navigation
Description
User outcome
A paraphrased question finds the right older note or document with its source, without exposing another bot's data, and removal really stops retrieval.
Metadata
- Phase: P3 · Kind: epic · Roadmap candidate 3 · Readiness: blocked by memory-retrieval-baseline and the per-platform memory-controls issues for UI items
Current behavior and evidence
The memory foundation exists: account-encrypted memory_config, own-bot namespaces, MemoryBackend with Hindsight, OpenViking, pgvector and Lance adapters, an embeddings module, per-turn automatic recall (5 s, 32 KiB, 20 results, 8000 characters), memory_service_retain/recall/reflect tools, a durable delivery queue and fenced deletion (https://github.com/bloodf/beans/blob/1a42fbf731609b71c0e81b3ce2f5c3e086926f92/docs/architecture/memory-services.md). Local Markdown memory (MEMORY.md, topic notes, dated logs, recall) is unchanged. Client status: memory-ui.md states the isolated request/draft adapters exist and 'the sheet module and native account/per-bot controls are not attached yet' on desktop; the phone has its own Memory pages (phone-app.md); do not claim full UI shipped. This epic adds measurement, ingestion and controls; it does not propose a second memory foundation or mandatory TinyHumans/CortexDB/Honcho accounts.
Children
- memory-retrieval-baseline
- memory-tinycortex-evaluation
- memory-controls-macos
- memory-controls-desktop
- memory-controls-phone-gap
- memory-document-ingestion
- memory-provenance-view
- memory-delete-rebuild-proof
- memory-scopes-sharing
- memory-scopes-implementation
Integration acceptance
- Paraphrased query retrieves an older approved fact with its source.
- Another bot's private note is never returned.
- After deletion and reindex the removed material is not returned; deleting a derived index never destroys notes.
Prerequisites
Blocked by: none.
Completion evidence
- All children closed with evidence; integration scenario recorded.
Current delivery phase
P3 — Profiles memory and artifacts. This difficulty-first assignment supersedes earlier phase/priority wording. Explicit dependencies remain required; same-phase work follows dependency order. Stable keys (including p0-* keys) remain unchanged.
Managed roadmap links
Parent: [P3] Profiles memory and artifacts
Blocked by: None.
Children:
- [P3][Memory-Retrieval] Measure current retrieval quality on synthetic fixtures
- [P3][Memory-Retrieval] Evaluate TinyCortex indexes against the baseline
- [P3][Memory-Retrieval] Opt-in ingestion of approved documents into memory
- [P3][Memory-Retrieval] Show source and age of recalled evidence
- [P3][Memory-Retrieval] Prove delete and derived-index rebuild behavior
- [P3][Memory-Retrieval] Explicit shared memory between bots
- [P3][Memory-Retrieval] Attach memory-service controls in the macOS app
- [P3][Memory-Retrieval] Attach memory-service controls in the Windows/Linux desktop app
- [P3][Memory-Retrieval] Assess phone memory pages against the shared fixture and close gaps
- [P3][Memory-Retrieval] Implement explicitly shared memory scopes
- [P3][Memory] Discover explicit group memory and compaction settings gaps
Activity
[-][P4][Epic] Memory retrieval: evidence on top of the existing foundation[/-][+][P3][Epic] Memory retrieval: evidence on top of the existing foundation[/+]bloodf commentedon Oct 13, 2026
Task contract — 2026-10-13
-R bloodf/beans, merge by the publishing authority, post-merge check. Source PASS is not installed-app or live-service acceptance.