grizzly-voicelisted

# Grizzly Voice — The Voice Spec Keeper VOICE.md is the positive style target every draft and edit anchors against. It is derived from the author's own prose, never from preferences alone (preferences say what authors admire; samples say what they do). ## Deriving (first time) Follow the procedure in grizzly-init Step 3: 2-3 samples of 300+ words of the author's own hand, analyzed field by field against `templates/VOICE.md`, counted not guessed, anchor lines confirmed by the author. ## Reconciling samples with the blacklist The samples will not always agree with `decks/blacklist.md`, and they will not always agree with each other. Two checks, both decided by the author, never assumed: 1. **Signature vs tell.** When a construction in the samples matches a blacklist entry (stacked short fragments reading as rule-of-three, emotion named directly in a given register, a recurring cadence), do not silently treat it as a tell and do not silently keep it. Surface it and ask: is this a signature to protect, or a crutch to tighten? Record the ruling in VOICE.md (blessed, blessed-with-a-cap, or treated-as-tell). tell-scan keeps these on its REVIEW tier precisely so a human ruling, not the regex, decides; the VOICE.md ruling is what those REVIEW hits are judged against. 2. **Target register when samples diverge.** When one sample runs more restrained and another fuller (more named emotion, more intensifier adverbs), name the gradient and ask which registe