Skip to content

[P3][Memory-Retrieval] Show source and age of recalled evidence #104

Open

Description

@bloodf

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/*.md updated in the same change; bun run check:docs passes

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

  1. added
    roadmapManaged Beans capability roadmap
    phase:P4Roadmap phase P4; not a blanket dependency
    area:memoryBeans memory workstream
    on Oct 7, 2026
  2. changed the title [-][P4][Memory-Retrieval] Show source and age of recalled evidence[/-] [+][P3][Memory-Retrieval] Show source and age of recalled evidence[/+] on Oct 7, 2026
  3. added
    phase:P3Roadmap phase P3; not a blanket dependency
    blockedBlocked: first unmet prerequisite named in the latest comment
    and removed
    phase:P4Roadmap phase P4; not a blanket dependency
    on Oct 7, 2026
  4. bloodf commented on Oct 13, 2026

    @bloodf
    OwnerAuthor

    Task contract — 2026-10-13

  5. added
    priority:normalUrgency: normal; schedule after high-priority work. Independent of roadmap phase.
    platform:androidScope: Android; implementation and acceptance require target-specific evidence.
    platform:cli-serverScope: CLI/Server; implementation and acceptance require target-specific evidence.
    platform:iosScope: iOS; implementation and acceptance require target-specific evidence.
    platform:linuxScope: Linux; implementation and acceptance require target-specific evidence.
    platform:macosTarget scope: macOS. Does not imply implementation or acceptance; require target-specific evidence.
    platform:windowsScope: Windows; implementation and acceptance require target-specific evidence.
    on Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:memoryBeans memory workstreamblockedBlocked: first unmet prerequisite named in the latest commentphase:P3Roadmap phase P3; not a blanket dependencyplatform:androidScope: Android; implementation and acceptance require target-specific evidence.platform:cli-serverScope: CLI/Server; implementation and acceptance require target-specific evidence.platform:iosScope: iOS; implementation and acceptance require target-specific evidence.platform:linuxScope: Linux; implementation and acceptance require target-specific evidence.platform:macosTarget scope: macOS. Does not imply implementation or acceptance; require target-specific evidence.platform:windowsScope: Windows; implementation and acceptance require target-specific evidence.priority:normalUrgency: normal; schedule after high-priority work. Independent of roadmap phase.roadmapManaged Beans capability roadmaptype:implementationRoadmap implementation

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions