Session Brief
02-working/session-briefsAI memory — written whenever context breaks. The next session reads it first.
What it is
AI agents have no memory between sessions. The Session Brief is the mechanism that provides it — a committed markdown file the next agent reads before touching anything. It does two jobs at once: AI memory continuity and async team communication. One artefact, two jobs.
When to write it
Whenever context is about to break — a phone call, a meeting, closing the laptop, hitting the context limit, ending for the night. Not just end of day. The question is: 'if I came back to this cold, what would I need to know?'
What goes in it
- What was done, per item, linked to the brief
- Decisions made and why; blockers and how they resolved
- Key Discovery — if non-empty, a 03-knowledge/ entry is required in the same commit
- The next-session start state
How it fits
The fifth tier of the Cascade, written every session without exception. It's also the first of C²'s three compaction mechanisms.
Get the templatestarter/docs/02-working/session-briefs/session-brief.md
Related