session-handover ยท diff
git:20261102.7e43d29 to git:20261102.60af376
2 added, 2 removed. Audit A to A.
What this update changes in the checks
No check changed: every fixed check gives the same answer before and after this update.
A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.
---
name: session-handover
- description: Procedure for ending a working session so the next person or agent can continue without guessing. Use it when finishing a task, stopping part-way, or handing work to someone else.
+ description: Procedure for ending a working session so the next person or agent can continue without guessing, and for picking up work from an earlier note. Use it when finishing a task, stopping part-way, handing work to someone else, or acting on a handover note, session note or earlier claim.
---
# Session handover
The next session knows only what was written down. Leave the facts it needs and nothing else.
## Record
One short line each, in the place your team keeps notes:
- What is now true
- What you verified, and how
- What is not done, or not verified
- Any blocker, and who it is waiting on
- The first next action
## Rules
- Write facts, not a transcript of files and commands. The history is already in version control.
- Use real dates, not "tomorrow" or "last week", because the note will outlive the session.
- Keep secrets and personal data out of notes.
- Mark anything unverified as unverified. The next session will trust what you write.
- - Before acting on an old note, check the live system. Notes go out of date.
+ - Before acting on an old note, check each claim it makes against the system of record, such as the database row or the live ticket, not other notes. Notes go out of date.