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

[Memory P5] End-to-end memory integration test #255

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

Context

All four tiers need to work together without conflicts, latency spikes, or context overflow.

Task

  1. Simulate multi-session conversation:
    • Session 1: User shares facts, makes decisions
    • Session 2: Verify facts auto-surface via prefetch
  2. Verify operational data from mempalace appears in context
  3. Verify session search auto-triggers on recall patterns
  4. Verify contradiction detection works across tiers
  5. Verify total injected context stays within token budget

Acceptance Criteria

  • Facts from session 1 surface in session 2 without explicit search
  • Operational context present when discussing fleet/forge topics
  • "What did we decide about X?" triggers episodic recall
  • No contradictions between tiers
  • Total injected memory context < 2000 tokens

Part of: [EPIC] Unified Memory Architecture

## Context All four tiers need to work together without conflicts, latency spikes, or context overflow. ## Task 1. Simulate multi-session conversation: - Session 1: User shares facts, makes decisions - Session 2: Verify facts auto-surface via prefetch 2. Verify operational data from mempalace appears in context 3. Verify session search auto-triggers on recall patterns 4. Verify contradiction detection works across tiers 5. Verify total injected context stays within token budget ## Acceptance Criteria - Facts from session 1 surface in session 2 without explicit search - Operational context present when discussing fleet/forge topics - "What did we decide about X?" triggers episodic recall - No contradictions between tiers - Total injected memory context < 2000 tokens Part of: [EPIC] Unified Memory Architecture
Rockachopa added this to the Unified Memory Architecture milestone 2026-04-09 00:42:21 +00:00
Rockachopa added the phase:5-integrationepic:memory labels 2026-04-09 00:42:22 +00:00
claude self-assigned this 2026-04-10 09:41:08 +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:5-integration
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 claude
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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