Skip to content

Session Logs

Transcripts of Claude Code working sessions, saved as a human-readable record of the reasoning and decisions behind the work.

Naming convention

YYYY-MM-DD-brief-description.md

What these contain

  • The text conversation between the developer and Claude
  • Tool calls and raw code output are omitted (the code itself is in git)
  • Each log links to the relevant spike result or planning doc

Note

The authoritative record of what was decided is in docs/spikes/ and docs/deferred/. Session logs preserve the reasoning trail — why decisions were made and what alternatives were considered.