Timmy_Foundation/hermes-agent
16
0
Fork 0
Code Issues 40 Pull Requests 1 Actions 3 Packages Projects Releases Wiki Activity

[MEMORY] Enforce artifact-first retrieval before free generation on recall tasks #141

New Issue
Closed
opened 2026-04-06 21:58:20 +00:00 by Timmy · 2 comments
Timmy commented 2026-04-06 21:58:20 +00:00
Owner
Copy Link

Why

When the agent can retrieve truth from issues, files, logs, session search, or other artifacts, it should do that before improvising. This is the difference between memory as recall and memory as hallucination.

Goal

Enforce artifact-first retrieval for tasks that reference prior work, issues, files, reports, or known operational state.

Scope

  • detect recall-style prompts (previous work, issue references, file/project references)
  • route them through artifact retrieval before free-form answering when tools are available
  • make the policy testable
  • document the expected retrieval order

Acceptance Criteria

  • recall-style requests trigger artifact retrieval before free generation when tools are available
  • issue/file/project references are grounded through retrieval in tests
  • failure paths fall back honestly instead of fabricating context
  • docs explain the retrieval order: durable memory -> session state -> artifacts -> procedures -> generation
## Why When the agent can retrieve truth from issues, files, logs, session search, or other artifacts, it should do that before improvising. This is the difference between memory as recall and memory as hallucination. ## Goal Enforce artifact-first retrieval for tasks that reference prior work, issues, files, reports, or known operational state. ## Scope - detect recall-style prompts (previous work, issue references, file/project references) - route them through artifact retrieval before free-form answering when tools are available - make the policy testable - document the expected retrieval order ## Acceptance Criteria - [ ] recall-style requests trigger artifact retrieval before free generation when tools are available - [ ] issue/file/project references are grounded through retrieval in tests - [ ] failure paths fall back honestly instead of fabricating context - [ ] docs explain the retrieval order: durable memory -> session state -> artifacts -> procedures -> generation
Timmy self-assigned this 2026-04-06 21:58:20 +00:00
Timmy commented 2026-04-07 13:49:49 +00:00
Author
Owner
Copy Link

Timmy: Flagging for re-scope against Mempalace (#190, #566). Mempalace provides the spatial memory framework. This issue should be evaluated in that context before implementation.

Timmy: Flagging for re-scope against Mempalace (#190, #566). Mempalace provides the spatial memory framework. This issue should be evaluated in that context before implementation.
Timmy commented 2026-04-07 14:15:47 +00:00
Author
Owner
Copy Link

Closed. hermes-agent tracks upstream NousResearch only. Sovereign work belongs on Timmy_Foundation/timmy-config. Refile there if still needed.

Closed. hermes-agent tracks upstream NousResearch only. Sovereign work belongs on Timmy_Foundation/timmy-config. Refile there if still needed.
Timmy closed this issue 2026-04-07 14:15:48 +00:00
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
 assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Task assigned to KimiClaw for processing
 blocked
Blocked by external dependency or merge conflict
 claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 duplicate
Duplicate of another issue
 epic
Epic - large feature with multiple sub-tasks
 gaming
Gaming agent capabilities
 infra
Infrastructure, VPS, DNS, deployment
 kimi-done
KimiClaw has completed this task
 kimi-in-progress
KimiClaw is actively working on this
 mcp
MCP (Model Context Protocol) tools & servers
 morrowind
Morrowind Agent gameplay & MCP integration
 needs-review
PR or issue requires reviewer sign-off before merge/close
 p0-critical
p1-important
security
Security hardening, vulnerability fixes
 stale
No activity, pending triage or closure
 velocity-engine
Auto-generated by velocity engine
 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 groq hermes kimi manus perplexity sonnet
No Assignees Timmy
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/hermes-agent#141
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?