kerfmaster pin list · The spec — what we build to
rulingA decision by Aristide or Jordan. True because it was decided; it can be superseded, but it cannot be stale.
Content last changed 2026-09-13 — computed from the item itself, not typed.
The rule: whenever work produces something that outlives the conversation — a draft or document, a standing to-do, an open decision waiting on a human, a commissioned build, a parked idea — it gets a pin in the same turn it is created, before the turn is reported done. The pin carries where the thing lives (file path, commit), what gates it, and whose word unblocks it.
Why: the security page draft (docs/security-page-kerfmaster.md, commit 95e479b) was committed and pushed but tracked nowhere a future session would look; Aristide had to ask 'did you document it in the todo list?' before it got its pin. The pin list is the master hitlist he checks — an untracked item is invisible work, and invisible work is the same defect as the stale-record drift the type system was built to stop.
What it covers: code bricks already do this (the record-in-same-commit rule); this ruling extends the discipline to NON-code artifacts — docs, drafts, checklists, questions parked with a human, strategic sittings, anything 'like these'. CLAUDE.md's open work queue mirrors the live items so they survive compaction, but the pin is the tracking home.
The test: if the session reset right now, would a fresh session find this thing by reading the pin list? If no, it needs a pin before the turn ends.