unsourcelisted

# unsource Compilation spreads one source across many pages. A bad source touches fifteen pages before anyone notices, and none of the published write-ups of this pattern offer a way back. This is the way back. It is also the deletion mechanism — removing information about a person means removing every page their source touched, which is the same operation. ## Why not just `git revert` Because later good edits sit on top of the bad ones. Reverting the commit throws away everything compiled since. This works claim-by-claim instead, which is why `CLAUDE.md` requires every page to record the source ids that shaped it. ## Procedure **1. Identify.** Resolve the user's description to a `sources/` page and its raw id. If ambiguous, list candidates and ask — unsourcing the wrong thing is expensive. **2. Find the blast radius.** `grep` the vault for the source id. Every page with it in `sources:`, every citation pointing at it, every loop extracted from it. Read `log.md` for the original ingest entry. **3. Report before touching anything:** - pages that exist *only* because of this source → will be deleted - pages where it is one of several sources → claims removed, page survives - loops extracted from it → will be closed as `killed` - claims that lose their only citation → **flag these individually and ask.** A claim you still believe but can no longer cite is the genuinely hard case, and it is the user's call whether to drop it or find a new source. **4. Wait for confir