harn-decidelisted

<!-- harnery:generated harn-decide v=a72bc5a9 — machine-owned; regenerated by `harn init`, removed by `harn deinit`. Edit the harnery template, not this file. --> The decision docket is a persistent queue for decisions you would otherwise route to a human. It's built on the `harn decision` engine. This skill is the mechanics — file, find precedent, claim, and resolve with evidence. *When* a decision needs a human at all (versus one you settle yourself) is host policy; if this project defines that rubric, follow it. ## Modes - **A decision you're facing (default)** → capture: record it and proceed. - **`resolve <id>`** → pick up an open decision, research it, resolve it. - **`review`** → surface resolved-but-unreviewed decisions for a human to skim. ## Capture (default) 1. **Check precedent first.** `harn decision search "<key terms>"`. If a resolved decision already answers this, cite it — don't re-litigate. 2. **File it** when the choice has a second consumer (a human will want to see it, or a future agent will face it again) or reversal is expensive. Skip the docket for pure local mechanics (a variable name, one of two equivalent idioms). ```bash harn decision file "<the decision as a clear question>" \ --context "why it matters / what's blocked / the options you see" \ --default-taken "<what you're proceeding with>" ``` For a decision with real substance, write a brief to a file and pass `--brief <path>` so the reviewer sees options