Session end

The goal is that the next session, or a teammate, can pick up exactly here. Write facts, not impressions: every claim in these files must come from something that happened in this session.

1. Gather the facts

• The session id: the abcd1234 shown in the session briefing.
• What changed: git log --oneline <start>..HEAD. The start commit is in .claude/state/sessions/<session id>.json (start_head); without it, use the commits you made in this conversation.
• What was verified: only tests and checks that actually ran in this session, with their real counts.
• What was decided, what is still open, and what is blocked.

2. Append to session-logs.md

Add one entry at the end, in this shape:

## YYYY-MM-DD · `abcd1234` · <branch>

**Goal:** what the user asked for, in one line.

- **Done:** each result, with its commit (`7091b76`).
- **Verified:** for example "616 Python tests passed with PostgreSQL; CI run 43 green".
- **Decisions:** each one, with its reason, and the ADR if one was written.
- **Open / next:** what the next session should do first.
- **Blockers:** anything waiting on the user or on access.

The backticked session id in the heading is what the hooks look for. Without it, the Stop hook will ask again, and SessionEnd will add an automatic entry.

3. Update project-progress.md

• Move finished items to Done, with a date. Set milestone statuses, and change Now and Next to match reality.
• Update the Last updated line.
• Never mark something done that was not verified.

4. Update Memory.md

Keep only what a future session needs and cannot get quickly from the code: user preferences, environment quirks, conventions and standing decisions.

• Update an existing line rather than adding a near-duplicate.
• Delete lines that are no longer true.
• Keep the file under about 150 lines.

5. Update the brain

• Edit the notes this session's work touched, such as brain/Projects/Agentic OS.md for a new feature, or the matching concept note for a design change.
• Set their updated: date to today.
• A genuinely new concept, dataset or decision gets a new note from brain/_templates/Note.md, linked from [[Home]] and from at least one related note.
• Use [[wikilinks]] for every connection. Do not create a note that only restates another.
• If the user's goals or preferences changed, update brain/User.md.
• Run python scripts/brain_check.py --strict. It must report no broken links, missing fields or missing sources.

6. Commit and push

• Commit the tracking files with a message such as Session log: <date>, <one-line summary>.
• Push to the working branch only, with git push -u origin <branch>.
• Never force-push, and never commit secrets, .env files, course files or personal data.

Rules

• Do not invent test counts, scores or results. Write "not run" when a check did not run.
• A session that changed nothing still gets a one-line entry if a decision was made; otherwise it needs no entry.