Working with log.md

log.md is a short, running record of what happened: the decisions you made and the changes worth remembering. It is your team's memory, kept in the workspace instead of in one person's head or one agent's chat history.

The point is that it stays focused. It is not a transcript of everything, which would bloat every session and stop being useful. It is the handful of durable decisions and changes a teammate or an agent would want to know next month.

What goes in

Dated lines, newest on top. Prefix a real decision with Decision: so the important forks are easy to find later.

**2026-07-15** Decision: moved account briefs from Notion into the workspace.
**2026-07-11** Renamed the "prospects" folder to "accounts".
**2026-07-03** Decision: we sponsor one newsletter a month, not three.

Only log what someone revisiting would care about. Routine work does not need a line.

Why keep it focused

An agent reads the log to catch up on what happened, so a tight log is a feature, not a limitation. If you pour every message and every small edit into it, the file gets long, the agent spends its attention on noise, and the signal is lost. Keep it to decisions and notable changes and it stays worth reading.

Logs, not lessons

log.md is what happened (history, backward-looking). What to do differently goes in lessons.md. The decision goes in the log; the rule you draw from it goes in lessons.

How to add one

Ask your agent, or let it offer at the end of a session.