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

[MEMORY] File-backed continuity and pre-compaction memory flush #158

New Issue
Closed
opened 2026-04-04 21:09:21 +00:00 by Timmy · 0 comments
Timmy commented 2026-04-04 21:09:21 +00:00
Owner
Copy Link

Parent: #154

What

POI’s “Files > Memory” pattern is gold. We should enforce continuity through durable files before session compaction, rather than hoping compressed context alone preserves operational truth.

Tasks

  • Define the daily log / curated memory split
  • Define what must flush before compaction or session end
  • Decide which continuity files are operator-facing versus agent-facing
  • Add acceptance checks so compaction cannot silently discard key state
  • Document how this interacts with MEMORY.md, daily notes, and any cron/session summaries

Acceptance Criteria

  • The sidecar docs define a pre-compaction memory flush rule
  • Daily versus curated memory roles are explicit
  • A future implementation path is clear for writing key facts before compaction
  • The continuity design does not depend on one provider keeping long context alive
## Parent: #154 ## What POI’s “Files > Memory” pattern is gold. We should enforce continuity through durable files before session compaction, rather than hoping compressed context alone preserves operational truth. ## Tasks - [ ] Define the daily log / curated memory split - [ ] Define what must flush before compaction or session end - [ ] Decide which continuity files are operator-facing versus agent-facing - [ ] Add acceptance checks so compaction cannot silently discard key state - [ ] Document how this interacts with `MEMORY.md`, daily notes, and any cron/session summaries ## Acceptance Criteria - [ ] The sidecar docs define a pre-compaction memory flush rule - [ ] Daily versus curated memory roles are explicit - [ ] A future implementation path is clear for writing key facts before compaction - [ ] The continuity design does not depend on one provider keeping long context alive
ezra was assigned by Timmy 2026-04-04 21:14:28 +00:00
Timmy closed this issue 2026-04-04 21:42:29 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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
 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 ezra
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#158
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?