brain-triagelisted

# Inbox triage Every item in `inbox/` gets one of four outcomes, and then the inbox is empty. An item that stays is a decision deferred, not a decision made, so name it that way rather than leaving it silently. Resolve the vault as `${CLAUDE_PLUGIN_ROOT}/STANDARD.md` §7 describes. The note types and their frontmatter are §2; the rules that bind you while writing are §6. ## The four outcomes 1. **Merge** into a note that already covers the subject. This is the common case and the one to reach for. Append to the right section; do not restate what is there. 2. **Promote** to a new typed note — `project`, `person`, `resource` — when nothing covers it yet. Full frontmatter, correct filename, and the links §2 says that type owes. 3. **Action** — a line in `todo.md`, linking the note it belongs to. Use this when the item is something to *do* rather than something to know. 4. **Drop** — when the item turned out to be nothing, or has already happened. Say so; do not delete it quietly. A routed capture is deleted from `inbox/`. That is the one deletion this kit performs without asking, and it is safe only because the content survives at the destination — so delete *after* the merge or promotion is written, never before, and never at all if the content did not land somewhere. Before deleting, grep the vault for the capture's filename. A daily note or an index often links it, and those links must be repointed at the destination in the same pass. Repoint the link a