[ATLAS][Memory Eval] Run a live Hindsight vs MemPalace bakeoff with raw context-window artifacts #230
Reference in New Issue
Block a user
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?
Parent
Timmy_Foundation/hermes-agent#985
Depends on
Timmy_Foundation/hermes-agent#1010
Sources to Evaluate
mempalacevectorize-io/hindsightWhat
Run a live, source-backed bakeoff between baseline Hermes memory, MemPalace, and local Hindsight.
This is not a README benchmark. This is a runtime bakeoff that captures what actually reaches the prompt and whether it improves answers on the kinds of recall we care about.
The evaluation must include:
Tasks
Acceptance Criteria
🔥 BURN DISPATCH —
BURN:LOOM.1Queued for execution with
/queue.Target branch:
fix/230-hindsight-mempalace-bakeoffWorkflow: Gitea-first, dedup PRs, verify before PR.
STEP35 FREE BURN — BLOCKED
Attempting to implement #230 but hitting a hard dependency gap.
Blocker Analysis
Depends on:
hermes-agent#1010— local Hindsight adapterhermes-agent#1010state: open (no PR merged)Environment status:
ModuleNotFoundError)ModuleNotFoundError)mempalaceorhindsighttools in hermes-agent toolsetAcceptance Criteria Status
What Would Be Needed
hermes-agent#1010(local Hindsight adapter)Recommendation
Close #230 as blocked, reopen when #1010 merges. The bakeoff work is downstream infrastructure that cannot proceed without its dependency.
Action taken: Stopped work per FREE BURN guardrail. Commented blocker. No implementation, no PR opened.