notelisted

# Note ## Core Rule A long writing session **will** compact. When it does, the conversation summary keeps the gist and drops the detail — the gotcha you found three hours ago, the reason you picked one framing over another, the exact key you decided not to cite. `/note` is the kit's defense: it writes one timestamped line to a durable-within-the-session journal *before* the detail is at risk, so `CLAUDE.md → After Compaction` can re-read it and restore what the summary lost. This is **deterministic memory, not judgment** (`CLAUDE.md → Model vs Code`). Do not paraphrase a finding back into the chat and hope it survives — append it. The skill never reasons about the text; it timestamps and stores it. One line, one fact. ## When to Use Invoke with `/note <tag> <text>` the moment something is worth not re-deriving: - You discovered a fact or gotcha that cost you effort — a source's real scope, a notation collision, a compile quirk. Tag it `finding`. - You made a choice with a reason — picked one term for a concept, settled a framing, decided a claim is the author's own and not citeable. Tag it `decision`. - You want a transient breadcrumb for *this* working block — "left off mid-paragraph in Results §3.2, the CI still needs checking." Tag it `summary`. - Proactively, when you sense a session is getting long and dense, before compaction takes the detail. Do **not** use `/note` for things with a permanent home: a settled framing/scope/methods decision belongs in `tasks/decis