Wrap-Up

Reach for this at the end of any working session that changed files or stopped with work still open, because the next session shouldn't spend its first twenty minutes rebuilding context you still had in your head.

Of 151 sessions in one operator's records, 16 ended on a scheduled command that a machine typed, and the last thing typed proves only that something ran, not that a person chose to stop there.

Wrap-Up 2.0 closes a working session in writing before anyone leaves it, across seven fixed stages. It writes one continuation note for each project the session changed.

The Seven Stages

  1. Debrief. List the decisions, failures, corrections and open questions the session produced.
  2. Pick the project. Its key is the folder the changed files belong to.
  3. Run the earned checks. Only the checks each changed file needs. Failures go under Open Threads.
  4. Draft three lines. What got done, its state, and one next action.
  5. Confirm the action. The owner corrects or confirms it before any write.
  6. Supersede and write. Older live notes get a superseded status line. The new note is written last.
  7. Close. Drafts are listed, each changed repository gets a commit suggestion, and nothing is pushed.

The Four Tests

A next action must pass four tests, and it's the owner who confirms it: imperative, a named object, one step, and resumable cold.

Test Fails Passes
Imperative Continue the deployment Merge the branch
Named object Run the test Run the import test against the Q3 file
Single step Finish the migration and ship the docs Re-run the import
Resumable cold Pick up where I left off Re-run the import and compare row counts to Friday's export

What The Note Will Not Claim

A check that did not run is written as not run, with its reason, and it is never written as passed. Notes are evidence, so a correction becomes a new entry, and we don't edit a written note afterwards. Weekly Review reads four of its fields, so they must be accurate.