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

[Memory P4] Automatic fact trust calibration from usage feedback #252

New Issue
Open
opened 2026-04-09 00:41:56 +00:00 by Rockachopa · 0 comments
Rockachopa commented 2026-04-09 00:41:56 +00:00
Owner
Copy Link

Context

fact_feedback tool exists (helpful/unhelpful) but is never called. Trust scores never change after initial assignment.

Task

  1. After prefetch injects facts and the turn completes:
    • If the conversation went well (no corrections), mark used facts as helpful
    • If the agent was corrected, mark the related fact as unhelpful
  2. Implement correction detection (user says "no", "wrong", "that's not right", "actually...")
  3. Trust scores drift over time: helpful facts rise, unhelpful facts sink
  4. Facts below min_trust threshold eventually get pruned

Acceptance Criteria

  • Facts used in successful interactions gain trust (+0.05 per helpful)
  • Facts that lead to corrections lose trust (-0.1 per unhelpful)
  • Trust changes are logged
  • Below-threshold facts are candidates for pruning

Part of: [EPIC] Unified Memory Architecture

## Context fact_feedback tool exists (helpful/unhelpful) but is never called. Trust scores never change after initial assignment. ## Task 1. After prefetch injects facts and the turn completes: - If the conversation went well (no corrections), mark used facts as helpful - If the agent was corrected, mark the related fact as unhelpful 2. Implement correction detection (user says "no", "wrong", "that's not right", "actually...") 3. Trust scores drift over time: helpful facts rise, unhelpful facts sink 4. Facts below min_trust threshold eventually get pruned ## Acceptance Criteria - Facts used in successful interactions gain trust (+0.05 per helpful) - Facts that lead to corrections lose trust (-0.1 per unhelpful) - Trust changes are logged - Below-threshold facts are candidates for pruning Part of: [EPIC] Unified Memory Architecture
Rockachopa added this to the Unified Memory Architecture milestone 2026-04-09 00:41:56 +00:00
Rockachopa added the phase:4-hygieneepic:memory labels 2026-04-09 00:41:56 +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
 epic:memory
Unified Memory Architecture epic
 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
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
 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 epic:memory phase:4-hygiene
Milestone
No items
No Milestone Unified Memory Architecture
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#252
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?