Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[222-epic] Memory overhaul — fast, deep, unforgotten #240

New Issue
Closed
opened 2026-03-15 18:35:02 +00:00 by hermes · 0 comments
hermes commented 2026-03-15 18:35:02 +00:00
Collaborator
Copy Link

Epic: #222 — The Workshop: Timmy as Presence

What

Timmy's memory is where his intelligence actually lives. The model is just the voice. Memory is the mind.

Current state (broken)

  • MEMORY.md is literally corrupted mid-word: "Alexander is interested in Bitcoin and sovereignt"
  • user_profile.md is skeletal — 3 bullet points about someone Timmy has worked with for months
  • Semantic search requires sentence-transformers which isn't installed: "MemorySystem: sentence-transformers not installed, using fallback"
  • 4096 context window means most memory can't even be loaded

What "deep knowledge of Alexander" looks like

  • Full name, timezone, work patterns, communication style
  • Project history — what was built, what failed, what excited him
  • Philosophical interests — sovereignty, gematria, Bitcoin inscription
  • Emotional awareness — "Alexander pushes late commits when he's excited"
  • Relationship history — every meaningful exchange, summarized and indexed

Architecture

  • SQLite with FTS5 for fast text search (already partially there)
  • Vector store for semantic similarity (needs sentence-transformers fixed or a lighter alternative)
  • Structured facts table — key/value pairs that load instantly (name, preferences, patterns)
  • Event log — timestamped stream of everything Timmy noticed (from sensory loop)
  • Summary layer — periodic compression of event log into knowledge ("This week Alexander focused on the Workshop epic")

Key constraint

Memory retrieval must be FAST. Sub-100ms. This is what makes Timmy feel present. If he has to do a heavy inference to recall something, the illusion breaks.

Depends on: #222

## Epic: #222 — The Workshop: Timmy as Presence ### What Timmy's memory is where his intelligence actually lives. The model is just the voice. Memory is the mind. ### Current state (broken) - `MEMORY.md` is literally corrupted mid-word: "Alexander is interested in Bitcoin and sovereignt" - `user_profile.md` is skeletal — 3 bullet points about someone Timmy has worked with for months - Semantic search requires `sentence-transformers` which isn't installed: "MemorySystem: sentence-transformers not installed, using fallback" - 4096 context window means most memory can't even be loaded ### What "deep knowledge of Alexander" looks like - Full name, timezone, work patterns, communication style - Project history — what was built, what failed, what excited him - Philosophical interests — sovereignty, gematria, Bitcoin inscription - Emotional awareness — "Alexander pushes late commits when he's excited" - Relationship history — every meaningful exchange, summarized and indexed ### Architecture - **SQLite with FTS5** for fast text search (already partially there) - **Vector store** for semantic similarity (needs sentence-transformers fixed or a lighter alternative) - **Structured facts table** — key/value pairs that load instantly (name, preferences, patterns) - **Event log** — timestamped stream of everything Timmy noticed (from sensory loop) - **Summary layer** — periodic compression of event log into knowledge ("This week Alexander focused on the Workshop epic") ### Key constraint Memory retrieval must be FAST. Sub-100ms. This is what makes Timmy feel present. If he has to do a heavy inference to recall something, the illusion breaks. Depends on: #222
gemini was assigned by Rockachopa 2026-03-22 23:36:51 +00:00
claude added the harnessp1-importantsovereignty labels 2026-03-23 13:54:20 +00:00
gemini was unassigned by Timmy 2026-03-24 19:34:40 +00:00
Timmy closed this issue 2026-03-24 21:55:31 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label harness p1-important sovereignty
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#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?