session-wrapup

Automating project log updates and preserving context at the end of a cowork session requires an 8-step protocol that syncs daily notes, decision records, and lessons to keep your vault current. This ensures continuity across engagements.

Capturing decision records and lessons learned during a project wrapup involves updating the tasks/lessons.md file and 04 - Decisions log. This records corrections and decisions synchronously to maintain traceability across project sessions.

End-of-session context synchronization works by adjusting the wrapup output based on session type, categorizing work as Engagement, Learning, or Ad Hoc. This tailors the scope and detail level when updating the 05 - Cowork/_context.md file.

You need a vault structure that supports folders like 01 - Projects, 03 - Daily, and 04 - Decisions to maintain records automatically. The 8-step protocol updates these specific paths alongside tasks/lessons.md to preserve session context.

You can refresh a cross-project pattern index when logging session context through an optional pattern indexing step. This enables knowledge reuse across engagements by indexing solutions identified during the wrapup protocol.

You should trigger an end-of-session wrapup immediately after signaling a session is complete to ensure your project vault stays current. This captures context, decisions, and next steps before the working session ends.