Timmy_Foundation/timmy-config
16
0
Fork 0
Code Issues 93 Pull Requests 6 Actions Packages Projects Releases Wiki Activity

docs: add MEMORY_ARCHITECTURE.md — retrieval order, storage layout, data flow #375

Open
perplexity wants to merge 1 commits from perplexity/mempalace-architecture-doc into main
pull from: perplexity/mempalace-architecture-doc
merge into: Timmy_Foundation:main
Conversation 0 Commits 1 Files Changed 1 +141
perplexity commented 2026-04-07 20:17:33 +00:00
Member
Copy Link

Summary

Adds the missing docs/MEMORY_ARCHITECTURE.md — the canonical reference for how Timmy's memory palace works.

Part of epic #367. Fulfills the documentation acceptance criterion from #369 ("Documented retrieval order in docs/MEMORY_ARCHITECTURE.md").

What's Documented

  • Retrieval Order (L0–L5) — the layered lookup chain from identity through palace rooms, scratchpad, artifacts, procedures, to free generation
  • Storage Layout — file structure for ~/.mempalace/ and ~/.hermes/scratchpad/
  • Component Map — links each module (mempalace.py, retrieval_enforcer.py, scratchpad.py, wakeup.py) to its issue and PR
  • Data Flow Diagram — ASCII visualization of recall detection → retrieval → response
  • Anti-Patterns — what NOT to do (generate from vibes, auto-promote, store raw output)
  • Status Table — current implementation state of each component

Relation to Other PRs

This doc is designed to be the companion to #374 (MemPalace integration). Once #374 merges, the code and the docs land together.

## Summary Adds the missing `docs/MEMORY_ARCHITECTURE.md` — the canonical reference for how Timmy's memory palace works. Part of epic #367. Fulfills the documentation acceptance criterion from #369 ("Documented retrieval order in `docs/MEMORY_ARCHITECTURE.md`"). ## What's Documented - **Retrieval Order (L0–L5)** — the layered lookup chain from identity through palace rooms, scratchpad, artifacts, procedures, to free generation - **Storage Layout** — file structure for `~/.mempalace/` and `~/.hermes/scratchpad/` - **Component Map** — links each module (`mempalace.py`, `retrieval_enforcer.py`, `scratchpad.py`, `wakeup.py`) to its issue and PR - **Data Flow Diagram** — ASCII visualization of recall detection → retrieval → response - **Anti-Patterns** — what NOT to do (generate from vibes, auto-promote, store raw output) - **Status Table** — current implementation state of each component ## Relation to Other PRs This doc is designed to be the companion to #374 (MemPalace integration). Once #374 merges, the code and the docs land together.
perplexity added 1 commit 2026-04-07 20:17:34 +00:00
docs: add MEMORY_ARCHITECTURE.md — retrieval order, storage layout, data flow 2e2a646ba8
This pull request doesn't have enough required approvals yet. 0 of 1 official approvals granted.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin perplexity/mempalace-architecture-doc:perplexity/mempalace-architecture-doc
git checkout perplexity/mempalace-architecture-doc
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Dispatched to Kimi via OpenClaw
 assigned-sonnet
claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 enhancement
epic
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 lazzyPit
Lazarus Pit automated recovery system
 research
sonnet-ready
velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity sonnet
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#375
Delete Branch "perplexity/mempalace-architecture-doc"

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?