Skip to content

[P3][Epic] Memory retrieval: evidence on top of the existing foundation #16

Open
1 of 2 issues completed

Description

@bloodf

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

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:

Activity

  1. added
    roadmapManaged Beans capability roadmap
    phase:P4Roadmap phase P4; not a blanket dependency
    on Oct 7, 2026
  2. changed the title [-][P4][Epic] Memory retrieval: evidence on top of the existing foundation[/-] [+][P3][Epic] Memory retrieval: evidence on top of the existing foundation[/+] 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
    area:memoryBeans memory workstream
    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:sharedShared implementation scope; target-platform support and acceptance require separate evidence.
    platform:windowsScope: Windows; implementation and acceptance require target-specific evidence.
    and removed
    blockedBlocked: first unmet prerequisite named in the latest comment
    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 workstreamphase: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:sharedShared implementation scope; target-platform support and acceptance require separate 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:epicRoadmap epic

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions