logbooklisted

# Logbook The repository keeps a work logbook: `LOGBOOK.md` plus append-only daily files under `journal/`. It exists because sessions are disposable and repositories are not. A decision that lives only in a closed session is lost; a decision in the logbook survives the session, the model, and the person. `docs/FORMAT.md` in the agent-logbook project is the authoritative syntax. This file is the working habit. ## Start by reading it Before touching anything, read the logbook. Not when you sit down to write an entry — when you pick up the task, before the first edit. The point of the format is that the last session left a written handover, and a handover nobody reads is the same as no handover. In this order: 1. `LOGBOOK.md`, the `Status:` line first. One sentence saying where the work actually stands right now, which is the thing you are least likely to guess correctly from the code. 2. `## Standing decisions` in the same file, if it has one: the decisions that still hold, each ending with the journal entry it rests on. Follow the citation when you need the reasoning. 3. The `## Document index` in the same file. It tells you which long documents exist and, in the status column, which ones no longer hold. Reading a design note that was superseded three weeks ago is worse than reading nothing. 4. The most recent files in `journal/`, newest first. Far enough back to cover the area you are about to touch. You are reading for three things: a decision tha