Files
swarm-zap/memory/2026-03-11.md

90 lines
4.5 KiB
Markdown

# 2026-03-11
## Memory maintenance
- Reviewed recent memory habits and did a cleanup pass.
- Assessment:
- capture frequency: good
- long-term curation: decent but lagging behind capture
- organization: getting messy due to a mix of daily logs, one-off topical notes, references, plans, logs, and machine-readable state in `memory/`
- Cleaned up `MEMORY.md` so it stores durable facts/lessons instead of mixed-in runtime/instruction text.
- Added a clearer rule to `AGENTS.md`: use named memory files only for long-lived plans/references/investigations; otherwise prefer the daily note.
## Durable lessons promoted to MEMORY.md
- Check current state before suggesting setup/re-setup.
- Treat Telegram DM and TUI/webchat as separate main-session contexts when `session.dmScope = "per-channel-peer"` is active.
- 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.
## Reclassification pass
- Moved substantive non-daily topical notes out of top-level `memory/` into clearer buckets:
- `memory/ops/` for workflow/setup/operational notes
- `memory/incidents/` for debugging, outages, and issue investigation notes
- Result: top-level `memory/` now contains mostly daily notes, which makes the default inbox much clearer.
## Memory taxonomy/docs
- Added a compact memory taxonomy section to `AGENTS.md` so future sessions know where different kinds of notes belong.
- Added `memory/README.md` to explain the folder layout, writing rules, and how embeddings should be used: lookup first, source verification second.
- Added `memory/projects.md` as a lightweight human-readable registry for bigger-picture ongoing efforts.
- Added `memory/tasks.md` as a human-readable guide for the structured task system in `memory/tasks.json`.
- Strengthened the explicit `remember this` rule so future sessions know to persist, promote, and route remembered items appropriately.
## LAN/local capability follow-ups
- Added TODO tasks for the main remaining capability gaps:
- calendar access/backend
- email/inbox access
- broader personal document/search corpus
- more homelab observability/status endpoints
- Added broader tool wishlist TODOs too:
- stronger GitHub tooling
- Google Workspace access
- local OCR / PDF extraction
- notes-system connector
- carefully scoped secret-manager integration
- Home Assistant / smart-home integration
- structured data connectors where useful
- Added second-wave improvement TODOs for workflow quality and leverage:
- local code indexing
- alert ingestion
- stronger local media pipeline
- lightweight people-context layer
- meeting-prep / briefing pipeline
- better notification routing
- external action audit log
- safer sandboxed execution helpers
- package/update intelligence
- local docs/manuals RAG
- lightweight decision log
- standard operating playbooks
- dependency / credential inventory
- eval / regression harness
- Reflected the same direction in `memory/projects.md` under `Local service expansion` and `Workflow quality and trust improvements`.
## Roadmap
- Added `memory/roadmap.md` to rank the growing backlog into `Now / Soon / Later`.
- Current `Now` focus:
- subagent reliability
- eval / regression harness
- calendar access/backend
- alert ingestion
- standard operating playbooks
- Mirrored the same prioritization in `memory/projects.md` for quick skimming.
## 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.
- Keep top-level `memory/` mostly reserved for daily notes; use subfolders for topical material.
- Use a light weekly memory-maintenance pass during heartbeats instead of waiting for clutter to build up.