Productisation Track (Epic #1029)
Hybrid Memory already has strong memory depth. This track exists to make that depth easy to see, trust, and demo.
Goal
Make hybrid-memory feel like a first-class product: immediately understandable, inspectable, and demoable without weakening the underlying trust model.
Important: Epic #1029 is a coordinating issue, not one giant implementation branch. Product work lands through focused child issues. The epic and every phase 1-3 child issue below are now closed as completed.
Current phase view
| Phase | Goal | Status | Child issues |
|---|---|---|---|
| Phase 1 — Foundation | Viewer, top-of-repo legibility, session visibility | Shipped | #1023 ✅, #1024 ✅, #1025 ✅ |
| Phase 2 — Polish | Messaging, demos, and simple public surface | Shipped | #1027 ✅, #1028 ✅ |
| Phase 3 — Maturation | Explicit retrieval strategy and layered terminology | Shipped | #1026 ✅ |
What is already shipped
Product entry points
- Memory Viewer / Mission Control via the local dashboard and viewer routes documented in
extensions/memory-hybrid/README.md(Issue #1023, closed) - README / onboarding refresh with the capture → store → recall → inspect → control mental model, trust/privacy links, and persona-based start paths (Issue #1024, closed)
- Simple public API / export surface documented at
PUBLIC-API-SURFACE.md(/health,/search,/timeline,/stats,/export) (Issue #1027, closed)
Trust and operator surface already available
- Local-first storage and inspection paths
- Verification, provenance, and deletion controls
- Quick start, operations, backup/restore, and trust/privacy documentation
- Session distillation and narrative docs that explain how memory is captured and reused over time
Phase delivery details
#1025 — Session timeline / observability (closed)
Delivered for the product story:
- one coherent session timeline
- capture vs injection visibility
- skipped/suppressed write explanations
- a human-readable “why this was recalled” surface
Status: unified observability service + tool surface is in place (services/session-observability.ts). CLI exposes openclaw hybrid-mem audit session with summary/timeline/json formats. Remaining polish is primarily UI visualization depth.
#1028 — Messaging, visuals, and demo story (closed)
Delivered for the presentation layer:
- tagline and elevator pitch (repository README)
- hero screenshots / proof points (
docs/assets/) - 60-second and 5-minute demo scripts (
docs/DEMO-PACKAGE.md) - terminology cleanup for first-time readers
#1026 — Filter → rank → hydrate retrieval (closed)
Delivered for the explicit retrieval model:
- named constrained-search mode in code and docs (
constrained-recall; seedocs/retrieval-modes.md) - structured filters before semantic ranking
- clearer explanation of why results matched and how they were ranked
Status: constrained-recall mode is documented and exposed as a user-facing retrieval mode; filter → rank → hydrate explanation is returned in tool output.
Execution order (completed)
- #1025 shipped — users can inspect capture, recall, injection, and skips without log-diving.
- #1028 shipped — the now-visible product has a sharper story, screenshots, and demo flows.
- #1026 shipped — retrieval is now a named, teachable product capability (
constrained-recall) instead of only an internal implementation detail.
Guardrails for every phase
- Local-first remains the hero path — no hosted-memory dependency required for the baseline experience.
- Keep the rich tool API — the product surface should complement it, not replace it.
- Do not weaken verification, provenance, or decay just to make the UI or docs simpler.
- Prefer layered explanations — simple first, deep internals one click away.