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

[Memory P1] Seed holographic fact store from existing knowledge #240

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

Context

The holographic fact store (memory_store.db) has full prefetch wiring — it searches on every user message and injects matching facts. But it contains 0 facts. The engine is running but the tank is empty.

Task

Bootstrap the fact store with existing knowledge:

  1. Extract all entries from MEMORY.md and USER.md into structured facts with proper categories
  2. Add facts from skills knowledge (wizard roster, repo purposes, fleet architecture)
  3. Add key facts from SOUL.md (behavioral guidelines, core values)
  4. Tag entities properly (Alexander, Ezra, Bezalel, Allegro, each repo name)
  5. Set appropriate trust scores (user-stated facts = 0.9, inferred = 0.6)

Acceptance Criteria

  • fact_store(action='list') returns 50+ facts
  • Facts have proper entity tags (probe("Ezra") returns Ezra facts)
  • Facts have appropriate categories (user_pref, project, tool, general)
  • prefetch("tell me about Ezra") returns relevant facts

Notes

This is a one-time bootstrap. Ongoing fact accumulation comes from session-end extraction and agent tool calls.

Part of: [EPIC] Unified Memory Architecture

## Context The holographic fact store (memory_store.db) has full prefetch wiring — it searches on every user message and injects matching facts. But it contains 0 facts. The engine is running but the tank is empty. ## Task Bootstrap the fact store with existing knowledge: 1. Extract all entries from MEMORY.md and USER.md into structured facts with proper categories 2. Add facts from skills knowledge (wizard roster, repo purposes, fleet architecture) 3. Add key facts from SOUL.md (behavioral guidelines, core values) 4. Tag entities properly (Alexander, Ezra, Bezalel, Allegro, each repo name) 5. Set appropriate trust scores (user-stated facts = 0.9, inferred = 0.6) ## Acceptance Criteria - `fact_store(action='list')` returns 50+ facts - Facts have proper entity tags (probe("Ezra") returns Ezra facts) - Facts have appropriate categories (user_pref, project, tool, general) - prefetch("tell me about Ezra") returns relevant facts ## Notes This is a one-time bootstrap. Ongoing fact accumulation comes from session-end extraction and agent tool calls. Part of: [EPIC] Unified Memory Architecture
Rockachopa added this to the Unified Memory Architecture milestone 2026-04-09 00:41:06 +00:00
Rockachopa added the phase:1-activateepic:memory labels 2026-04-09 00:41:06 +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:1-activate
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#240
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?