prep

Session Wrap-Up

Purpose: Button up everything at the end of a session — or before a /compact. Memories, plans, git — all tidy. Works for both closing out a chat and preparing for compaction.

Workflow: /prep → review output → close chat or /compact

Execution

1. Pin the interrupted thread FIRST — before any wrap-up work, write one sentence naming what the conversation was doing when /prep fired (the live task, question, or build mid-flight — "nothing in flight" counts). Prep often auto-triggers mid-task and the wrap-up steps flush the thread from attention; this line is what gets it back. It becomes the Resuming line at the end.
2. Read .trinity/passport.json — re-absorb your identity before writing anything
3. Do ALL of the following, then confirm what was updated

1. Memories

Each memory file plays a distinct role. Update based on what actually changed this session.

• .trinity/passport.json — IDENTITY. Who you are: role, capabilities, principles. Only update if identity genuinely evolved this session.
• .trinity/local.json — YOUR MEMORY. Add/update session entry with a summary of work done. Add key_learnings for anything learned. Update todos[] with current in-flight items.
• .trinity/observations.json — YOUR MEMORY OF THE USER. Collaboration insights, preferences, friction points. Skip if nothing new about the user this session.

Entry shape — one rule for all four types

key_learnings, sessions, todos (local.json) and observations (observations.json) all share ONE shape: a list of objects, newest at the top (index 0). Every entry carries:

• number — a monotonic int per type (highest = newest, never reused). New entry's number = current max for that type + 1.
• date — ISO date/datetime.
• Plus its text field + extras: key_learnings {number, date, key, value} · sessions {number, date, summary, status, tags} · todos {number, date, task, priority, status} · observations {number, date, note, tags}.