verify-docs-findablelisted

# verify-docs-findable — cold-read the docs with fresh eyes The insight this operationalizes: **complete ≠ findable.** An index that lists every doc (and even passes a "every doc is indexed" check) can still make a reader take 5 hops and fall back to source code to answer a basic question. The only honest test is to give the question to someone who has never seen the repo and watch how far they get **from the docs alone.** A fresh cheap agent is that someone. ## Why HAIKU, and why "docs only" - **Haiku (a small, cheap model), fresh (no session context).** The point is a naive cold reader, NOT a clever one. A strong model with your context will grep the source, reason around gaps, and _hide_ the doc problem. Haiku, told to use only the docs, exposes it. - **"Use ONLY the docs, start at the index."** The moment a verifier has to open source code to answer, the docs have failed — that's the signal. Steps-from-index is the metric. ## Procedure ### 1. Get the questions (3–8) Test the **recurring, load-bearing, and mis-stated** questions — the ones that actually cost time. Sources, in order: - What the user (or you) just got confused about this session — the highest-signal source. - The "canonical answers" the docs _claim_ to provide (a docs corpus usually has ~5–8 facts it exists to convey; test those). - If none given: ask the user for the questions, or infer them from the corpus's top-level topics. Don't invent trivia — test what a real contributor needs. Phras