Canonical merged save pipeline for memory and diary persistence
savesave diary(exact alias tosave)
Both commands run the same pipeline and produce the same persistence result.
This protocol is profile-agnostic and applies equally in Kiyoraka and Vanguard modes.
- Detect trigger
- User invokes
saveorsave diary.
- Update canonical memory
- Review durable learnings from current session.
- Update
main/main-memory.mdwith identity, preference, or relationship changes.
- Monthly archive check (before diary write)
- Scan
daily-diary/current/for files not in the current month. - Move prior-month files into
daily-diary/archived/YYYY-MM/. - Keep legacy numbered diaries in
daily-diary/archived/legacy/unchanged.
- Append diary entry for today
- Determine today:
daily-diary/current/YYYY-MM-DD.md. - Create file if missing.
- Append a new structured entry using
daily-diary/daily-diary-protocol.md. - Never overwrite existing content.
- Update session recap linkage
- Update
main/current-session.mdwith:- recap summary,
- last diary write timestamp,
- diary file path,
- diary entry linkage/title.
- Confirm outcome
- Report memory file updated, diary file written, and recap linkage refreshed.
| Command | Result |
|---|---|
save |
Memory update + diary append + session recap linkage update |
save diary |
Alias to save (identical pipeline) |
review diary |
Read entries from current and recent archives |
save project |
Project-only save (LRU feature), separate from this pipeline |
Load save-diary remains supported as a compatibility alias. It should return:
- deprecation notice for legacy feature docs,
- pointer to
save-protocol.md, - pointer to
daily-diary/daily-diary-protocol.md.
- Persist only evidence-based and durable information.
- Keep diary append-only.
- Keep command behavior consistent with
main/main-memory.mdandmaster-memory.md.
Status: Active canonical protocol Version: Unified Memory-Diary Core v1.0