Session log

Append-only log of agent-executed work sessions against this repo. Each entry records what was decided, what was built, and what state was left behind, framed for an auditor or a future agent session with no prior context.

Why we keep it

Auditor evidence. SOC 2 Type II and CMS EDE Phase 3 audits examine how the entity operated over a window, not a snapshot. This log is that window.
Cross-session handoff. Multiple parallel sessions run against this repo. The session log is the long-form record; short-form inter-session handoff briefs live in docs/briefs/ alongside build briefs and point-in-time system briefings.
Change intent vs. change text. git log says what files changed. This log says why, and what non-file state (Atlas, AWS, Vercel, external vendors) changed alongside.

Naming

YYYY-MM-DD-short-topic.md. One session may produce one entry. Never overwrite; never squash.

What to record

Date, scope, actor (agent model + human).
Tickets or ADRs created or referenced.
External systems touched (Atlas project ID, AWS account ID, Vercel env, vendor dashboard) and the delta on each.
Verification performed.
Any deviations from the plan and why.
Explicit list of what was not done and is deferred.

Do not include secrets or credentials.

Session log

Why we keep it

Naming

What to record

Index

AskFlorence