reviewlisted

# Onboard an existing repository ## Plan !`docgov review --json --compact 2>&1 | head -c 24000` ## What to do The JSON above is the full plan; `.docgov/fix-plan.md` is the human-readable version. **Nothing has been changed.** 1. **Summarize honestly, shortest first.** How many documents, how many DocGov could not classify, how many moves, how many real judgement calls. Do not pad the summary with the things that went fine. 2. **Work the low-confidence classifications.** `classifications[]` entries with `needsReview: true` are where the deterministic classifier gave up. Read each document (just enough of it) and decide its class yourself. Run `docgov types` if you need the list. Then write the decision into the document's frontmatter: ``` docgov: id: <kebab-id> type: <class> authority: <from the class> visibility: internal|public|confidential ``` Declaring the type is what turns a guess into a fact — the classifier never overrides a declared type. 3. **Adjudicate the contradiction candidates.** `contradictionCandidates[]` is a narrowed list, not a verdict. For each pair, read both and decide: genuine contradiction, acceptable overlap (different audiences saying the same thing in different words), or genuine duplicate. Use the `architect` agent for the non-obvious ones. Only real contradictions need fixing, and the higher-authority document is the one that is right unless you have a reason to think otherw