Repository navigation
Description
User outcome
Users see which note/document/chat produced a recalled fact and can open or delete it.
Metadata
- Phase: P3 · Kind: leaf · Priority: personal computers stay first; this stream is independent of VM UI work
- Readiness: blocked by the per-platform memory-controls issues
- Relative size: M
Current behavior and evidence
Recall evidence is labelled untrusted data in ephemeral TurnNotes; Hit records source labels locally (memory.rs:77). Clients do not present provenance.
Proposed incremental behavior and reuse anchors
Expose Evidence (id, text, document_id) and source labels in a read-only inspector using existing inspect capability.
License and dependency constraints
Native Beans work under the repository's GPL-3.0-only licence; no new dependency.
Ordered tasks and subtasks
- 1. Inspector API mapping
- 2. Client view
- 3. Link to delete flow
Affected surfaces
- clients
- crates/cli/src/memory_service/api.rs
Failure, security, privacy and data-preservation cases
- Evidence text is untrusted; render as plain text.
Acceptance
- Inspector shows source for each recalled item when the backend supports it; hides otherwise
- Items without backend provenance show 'source unavailable', not an invented source
- Recalled text renders as plain, untrusted text
- Delete action from the inspector uses the existing fenced flow
Verification
- Automated: No established automated command covers this discovery; evidence is the written decision record.
- Manual scenario: Recall a fact and open its source.
- Plain-language note: commands above were not executed during roadmap drafting; run only those relevant to the change.
Prerequisites
Blocked by: memory-controls-macos, memory-controls-desktop, memory-controls-phone-gap (links filled at publication).
Completion evidence
- Linked PR with passing checks listed above
- Manual scenario result recorded (date, platform, outcome)
- Affected
docs/architecture/*.mdupdated in the same change;bun run check:docspasses
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][Epic] Memory retrieval: evidence on top of the existing foundation
Blocked by: [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
Activity
[-][P4][Memory-Retrieval] Show source and age of recalled evidence[/-][+][P3][Memory-Retrieval] Show source and age of recalled evidence[/+]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.