Timmy_Foundation/hermes-agent
15
0
Fork 0
Code Issues 282 Pull Requests 87 Actions 1 Packages Projects Releases Wiki Activity

[ATLAS][Memory] Port Hindsight-style multi-path recall (semantic + BM25 + graph + temporal + RRF) #1011

New Issue
Open
opened 2026-04-22 14:25:20 +00:00 by Rockachopa · 2 comments
Rockachopa commented 2026-04-22 14:25:20 +00:00
Owner
Copy Link

Parent

Timmy_Foundation/hermes-agent#985

Depends on

Timmy_Foundation/compounding-intelligence#230

Source to Mine

  • vectorize-io/hindsight

What

Port the most useful part of Hindsight's memory architecture into Hermes-native memory retrieval:

  • semantic retrieval
  • lexical/BM25 retrieval
  • graph-aware retrieval
  • temporal retrieval
  • fusion with RRF or equivalent
  • rerank stage where justified by measured gain

The goal is not to clone the whole Hindsight product. The goal is to steal the retrieval architecture that survives long-horizon memory workloads.

Tasks

  • Define a pluggable retrieval interface with separate retrieval lanes
  • Implement at least four retrieval lanes: semantic, lexical, graph, temporal
  • Add fusion logic (RRF or equivalent) with traceable scores
  • Add optional rerank stage behind a measurable guard
  • Emit retrieval traces so failures can be inspected after a run
  • Benchmark the new pipeline against the current Hermes-native retrieval path

Acceptance Criteria

  • Four independent retrieval lanes exist and can be enabled/disabled separately
  • Fusion output includes inspectable per-lane contributions
  • Retrieval traces are available for failed and successful recall cases
  • A benchmark or evaluation report shows whether the pipeline improves long-horizon recall on our prompt matrix
  • The implementation lands without introducing a mandatory cloud dependency
## Parent Timmy_Foundation/hermes-agent#985 ## Depends on Timmy_Foundation/compounding-intelligence#230 ## Source to Mine - `vectorize-io/hindsight` ## What Port the most useful part of Hindsight's memory architecture into Hermes-native memory retrieval: - semantic retrieval - lexical/BM25 retrieval - graph-aware retrieval - temporal retrieval - fusion with RRF or equivalent - rerank stage where justified by measured gain The goal is not to clone the whole Hindsight product. The goal is to steal the retrieval architecture that survives long-horizon memory workloads. ## Tasks - [ ] Define a pluggable retrieval interface with separate retrieval lanes - [ ] Implement at least four retrieval lanes: semantic, lexical, graph, temporal - [ ] Add fusion logic (RRF or equivalent) with traceable scores - [ ] Add optional rerank stage behind a measurable guard - [ ] Emit retrieval traces so failures can be inspected after a run - [ ] Benchmark the new pipeline against the current Hermes-native retrieval path ## Acceptance Criteria - [ ] Four independent retrieval lanes exist and can be enabled/disabled separately - [ ] Fusion output includes inspectable per-lane contributions - [ ] Retrieval traces are available for failed and successful recall cases - [ ] A benchmark or evaluation report shows whether the pipeline improves long-horizon recall on our prompt matrix - [ ] The implementation lands without introducing a mandatory cloud dependency
Rockachopa commented 2026-04-22 15:12:47 +00:00
Author
Owner
Copy Link

Opened PR #1028: #1028

Ported multi-path holographic recall with lexical/semantic/graph/temporal lanes, RRF fusion, trace capture, and a prompt-matrix benchmark that improved top-1 recall from 1 to 3 on the new long-horizon fixture set.

Opened PR #1028: https://forge.alexanderwhitestone.com/Timmy_Foundation/hermes-agent/pulls/1028 Ported multi-path holographic recall with lexical/semantic/graph/temporal lanes, RRF fusion, trace capture, and a prompt-matrix benchmark that improved top-1 recall from 1 to 3 on the new long-horizon fixture set.
Rockachopa commented 2026-04-30 13:04:00 +00:00
Author
Owner
Copy Link

BLOCKER: An open PR already references this issue.

PR #1028 — "feat: port multi-path holographic recall (#1011)" — is open and already implements the full work:

  • Four retrieval lanes: lexical, semantic, graph, temporal
  • RRF fusion with per-lane trace capture
  • Trace inspection via fact_store(action="trace")
  • Prompt-matrix benchmark report
  • No mandatory cloud dependency

PR is on branch fix/1011, authored by the issue opener, and is the intended implementation path.

Per STEP35 FREE BURN protocol: "STOP if any open PR already references #1011."

Resolution:

  • Review and merge PR #1028 (work is already done)
  • Close #1011 as duplicate/completed
  • Do NOT create a step35/ branch — the work exists and is in-progress via the canonical PR
**BLOCKER:** An open PR already references this issue. PR [#1028](https://forge.alexanderwhitestone.com/Timmy_Foundation/hermes-agent/pulls/1028) — *"feat: port multi-path holographic recall (#1011)"* — is **open** and already implements the full work: - Four retrieval lanes: lexical, semantic, graph, temporal - RRF fusion with per-lane trace capture - Trace inspection via `fact_store(action="trace")` - Prompt-matrix benchmark report - No mandatory cloud dependency PR is on branch `fix/1011`, authored by the issue opener, and is the intended implementation path. **Per STEP35 FREE BURN protocol:** *"STOP if any open PR already references #1011."* **Resolution:** - Review and merge PR #1028 (work is already done) - Close #1011 as duplicate/completed - Do NOT create a step35/ branch — the work exists and is in-progress via the canonical PR
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CI
Continuous integration, runners, workflow issues
 QA
Quality assurance, testing, production audit
 accessibility
Auto-created for game epic
 assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Task assigned to KimiClaw for processing
 audit-finding
batch-pipeline
batch-pipeline label
 blocked
Blocked by external dependency or merge conflict
 bug
claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 critical
docs
Auto-created for game epic
 duplicate
Duplicate of another issue
 epic
Epic - large feature with multiple sub-tasks
 epic:memory
Unified Memory Architecture epic
 game
Auto-created for game epic
 gaming
Gaming agent capabilities
 implementation
Auto-created for game epic
 infra
Infrastructure, VPS, DNS, deployment
 infrastructure
Auto-created for game epic
 juice
Auto-created for game epic
 kimi-done
KimiClaw has completed this task
 kimi-in-progress
KimiClaw is actively working on this
 mcp
MCP (Model Context Protocol) tools & servers
 mechanics
Auto-created for game epic
 mobile
Auto-created for game epic
 morrowind
Morrowind Agent gameplay & MCP integration
 needs-review
PR or issue requires reviewer sign-off before merge/close
 ops
p0-critical
p1-important
performance
Auto-created for game epic
 phase:1-activate
Phase 1: Activate existing systems
 phase:2-operational
Phase 2: Operational memory bridge
 phase:3-episodic
Phase 3: Proactive episodic recall
 phase:4-hygiene
Phase 4: Memory hygiene and quality
 phase:5-integration
Phase 5: Integration and testing
 poka-yoke
polish
Auto-created for game epic
 priority-high
Auto-created for game epic
 priority-low
Auto-created for game epic
 priority-medium
Auto-created for game epic
 research
security
Security hardening, vulnerability fixes
 shared-infra
Shared infrastructure across projects (Playground + LPM)
 sovereign
Auto-created for game epic
 stale
No activity, pending triage or closure
 throughput-10x
throughput-10x label
 token-masterplan
token-masterplan label
 tool-evaluation
ux
Auto-created for game epic
 velocity-engine
Auto-generated by velocity engine
 visuals
Auto-created for game epic
 wont-fix
Closed as intentionally not fixing — explicit descope
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok hermes kimi manus perplexity sonnet
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/hermes-agent#1011
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?