Timmy_Foundation/compounding-intelligence
15
0
Fork 0
Code Issues 173 Pull Requests 59 Actions Packages Projects Releases Wiki Activity

[Retro] Migrate existing MemPalace + fact_store into knowledge store #19

New Issue
Open
opened 2026-04-14 15:15:25 +00:00 by Timmy · 0 comments
Timmy commented 2026-04-14 15:15:25 +00:00
Owner
Copy Link

Epic: #5 (Retroactive Harvest)

Task

Don't lose existing knowledge. Migrate from current systems.

Sources

  1. MemPalace: ~/.hermes/mempalace/*.json — structured analysis data
  2. Fact store: holographic memory (31 facts stored)
  3. Skills: ~/.hermes/skills/ — procedural knowledge
  4. Session search: already-indexed session summaries

Process

  • Read each source
  • Convert to knowledge store schema
  • Deduplicate (existing knowledge store has priority)
  • Mark migrated facts with source attribution

Acceptance Criteria

  • All MemPalace forge data migrated
  • All fact_store entries migrated
  • Skills represented as pattern facts
  • No data loss, full source attribution
## Epic: #5 (Retroactive Harvest) ### Task Don't lose existing knowledge. Migrate from current systems. ### Sources 1. **MemPalace**: `~/.hermes/mempalace/*.json` — structured analysis data 2. **Fact store**: holographic memory (31 facts stored) 3. **Skills**: `~/.hermes/skills/` — procedural knowledge 4. **Session search**: already-indexed session summaries ### Process - Read each source - Convert to knowledge store schema - Deduplicate (existing knowledge store has priority) - Mark migrated facts with source attribution ### Acceptance Criteria - [ ] All MemPalace forge data migrated - [ ] All fact_store entries migrated - [ ] Skills represented as pattern facts - [ ] No data loss, full source attribution
Timmy added the retroactivemilestone:4 labels 2026-04-14 15:15:25 +00:00
hermes was assigned by Rockachopa 2026-04-15 01:50:35 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acceptance-criteria
batch-pipeline
Token masterplan batch pipeline
 bootstrapper
Pre-session context injection
 epic
Epic-level issue
 harvester
Session knowledge extraction
 measurer
Compounding metrics
 milestone:1
Milestone 1: Foundation
 milestone:2
Milestone 2: Integration
 milestone:3
Milestone 3: Measurement
 milestone:4
Milestone 4: Retroactive
 pipeline
Pipeline/integration work
 pipeline
priority:high
priority:medium
retroactive
Processing existing sessions
 throughput-10x
throughput-10x label
 token-masterplan
token-masterplan label
No Label milestone:4 retroactive
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Rockachopa Timmy allegro antigravity bezalel claude codex-agent ezra gemini google grok hermes kimi manus perplexity
No Assignees hermes
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/compounding-intelligence#19
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?