session-closeout

Closing a governance session involves recording breadcrumbs in artifacts, refreshing Primer.md, and committing a readable summary. This three-action workflow ensures changes are traceable in artifacts and git history.

Breadcrumbs in session closeout are one-line records automatically written into artifacts touched during the session. They provide a concise trail of what changed to ensure continuity for future artifact readers.

Refreshing a Primer after governance changes involves updating Primer.md to reflect the latest state and next moves. This occurs automatically during the closeout workflow after capturing breadcrumbs and before committing.

You need to run a session closeout workflow whenever a session has produced commits or governance-level changes. It ensures changes are reflected in artifacts, the Primer, and git history for continuity.

Yes, you can use this session closeout process for product management tasks. It helps product teams wrap up sessions by recording changes, refreshing the forward-looking Primer, and committing a summary.

The best way to commit a readable summary is using a deterministic closeout workflow that auto-commits with a body summarizing what shipped and what is next. This follows breadcrumb generation and Primer refresh.