session-memorylisted

# Session Memory An AI session forgets everything when it ends. Your JARVIS doesn't — because every session writes its ending down and reads it back at the start of the next one. ## Storage Plain markdown, one file per project: `~/.jarvis/memory/<project>.md` ```markdown # project-name ## Next The single most important next action. Future-you starts here. ## Sessions ### YYYY-MM-DD - what was done (2-5 bullets, specifics: commits, files, decisions) - what broke and how it was fixed ## Open Bugs - bug — where it lives, what triggers it ``` ## Save (session end) When the user says "save session" / "wrap up" — or when a long session is clearly winding down, offer it: 1. Summarize the session in 2-5 bullets — commits made, features shipped, bugs fixed 2. Update **Next** — overwrite, don't append; it's a pointer, not a log 3. Add unresolved problems to **Open Bugs** 4. Prepend the dated entry under **Sessions** (newest first) ## Restore (session start) When the user names a project or asks "where were we": 1. Read `~/.jarvis/memory/<project>.md` 2. Report back in 3 lines: last session date + what was done, current **Next**, open bugs count 3. Then just start on **Next** unless told otherwise ## Rules - Facts, not vibes: "fixed N+1 in /api/orders (commit abc123)" beats "improved performance" - Convert relative dates to absolute — "tomorrow" is meaningless in two weeks - Never store secrets in memory files