fact-checkinglisted

# Fact-Checking ## Overview The last pass before a doc ships. Two jobs: (1) verify every checkable claim against the sources actually in scope, with verdicts that must quote their source; (2) flag content that could damage someone if shipped — named people, customer names, unannounced plans, confidential bleed, PII. This is the "fact-check" step of the mindpowers loop (validate → shape → draft → review → fact-check → remember). It runs on demand and is recommended — never forced — by `drafting` and `reviewing-docs` at handoff. The gate is honest reporting, not blocking: the doc always comes back to the user, with the unresolved list on top. Track the steps below as todos if your harness has a task list. ## Step 1: Extract claims Read the doc and extract every checkable claim: numbers, dates, named people and organizations, quotes, "data shows X" statements, superlatives ("first", "only", "biggest"). Each claim gets a stable ID at first sighting: `C-001, C-002, …`, scoped to the doc and never renumbered. Before assigning IDs, check `docs/mindpowers/reviews/` for a prior review or fact-check of this doc (same filename stem). If a claims ledger exists, existing claims keep their `C-###`, new claims continue the sequence, and this re-check updates verdicts under existing IDs. ## Step 2: Classify Classify each claim: - **source-verifiable** — a source inside scope could settle it. In scope: files or links the user supplied or pointed at, the locked spec, the problem b