The problem
Every work item gets its own memory file, with a checker.
How it works
AI sessions forget. Work items last weeks. Without a durable record, every new session re-asks the same questions.
Each work item is one Markdown note with fixed fields: status, owner, due date, where things stand, and the live source to check. An index lists them all, a viewer shows them, and a checker flags notes that are stale or missing fields.
Live, in daily use, as durable memory per work item. Sessions are disposable; the notes are the memory.
- One Markdown note per work item
- Index and viewer across all of them
- A checker flags stale or broken notes
Outcome
A session can end at any point: the next one picks the work up from the note, not from anyone's memory.
Stack
- knowledge-management
- markdown
- ai-memory
- claude-code
Code
github.com/HenryLop/thread-notes
Transcript
Every work item gets its own memory file, with a checker. AI sessions forget; client work lasts weeks. So each item is one note: status, owner, due date, where things stand. An index lists them, a viewer shows them, and a checker flags anything stale. Sessions are disposable. The notes are the memory.
How this was made
Voiceover is text-to-speech (Microsoft Edge neural voice). Background art is AI-generated (Gemini). Titles and captions are set in code, not generated. The build itself was made with Claude Code.