chore(memory): archive low-value session summaries
This commit is contained in:
@@ -15,6 +15,20 @@
|
||||
- Prefer local-first search routing and remember Brave free-plan rate limits.
|
||||
- Keep backup/transcription infrastructure notes in long-term memory when they affect future operations.
|
||||
|
||||
## Consolidation pass
|
||||
- Archived obvious low-value auto-generated session-summary files out of top-level `memory/` into `memory/archive/session-summaries/` instead of deleting them.
|
||||
- Archived files:
|
||||
- `2026-03-02-2127.md`
|
||||
- `2026-03-03-2223.md`
|
||||
- `2026-03-03-session-greeting.md`
|
||||
- `2026-03-04-0825.md`
|
||||
- `2026-03-04-greeting.md`
|
||||
- `2026-03-04-test-confirmation.md`
|
||||
- `2026-03-05-heartbeat-ok.md`
|
||||
- `2026-03-05-codex-error-type-error-error-t.md`
|
||||
- Rationale: these were mostly reset/greeting/test/heartbeat artifacts with little long-term value, but still worth retaining in case old session evidence is needed later.
|
||||
|
||||
## Follow-up intent
|
||||
- Be more disciplined about using the daily note as the default inbox and promoting only durable truths into `MEMORY.md`.
|
||||
- Avoid adding new one-off memory files unless the topic is truly long-lived.
|
||||
- Consider a later second-pass reclassification for remaining topical files (for example, move stable plans/references into clearer subfolders and fold tiny one-off notes back into day files where safe).
|
||||
|
||||
Reference in New Issue
Block a user