Sort docs/governance from 63 documents into three, and check doc links

[Masterplanner25]

An audit prompt is an instrument, not policy

AUDIT_ARCHITECTURE.md opens with "Applies to: any language runtime with a
compiler, VM, and embedding API" and describes no Nodus rule at all. You run
one, fix what it finds, and re-run it. Nine of those sat in docs/governance/.
They are docs/audits/ now.

The same reading applies to the records — and each says so in its own header:

4 docset-sweep documents	carry "a dated record ... do not update it to match the tree"
5 version plans	superseded; the live one is V6_0_PLAN.md
2 release notes	predate CHANGELOG.md
HIGH_CONFLICT_DOC_RECONCILIATION_PLAN.md	CLOSED; CLAUDE.md already warns it is not a to-do list
3 ecosystem analyses	pinned to released versions (v4.0.7, 5.0.4, COMPLETE)
INVARIANT_TEST_MAPPING.md	"Superseded by tools/invariant_coverage.json", in its own header

None of those governs anything. They are docs/history/, grouped so sibling
links keep working. The three eval prompts joined the results they produce in
docs/evals/.

Governance keeps the 34 documents that actually govern. The size was itself
the problem: a folder nobody can navigate does not govern anything.

The paths inside the dated records were deliberately not rewritten

A record is a statement about the tree on a given day. Editing
docs/governance/V2_1_PLAN.md to the current path would make the sweep claim it
saw a file somewhere it never was.

So markdown links were repointed so they resolve — a link is navigation, not
a claim — while prose naming an old location was left alone. Same reasoning
for CHANGELOG.md, whose entries describe releases that happened.
docs/history/README.md records the distinction so the next reader does not
"fix" it.

Mechanical care — 57 files mention a moved document

• a link checker found 11 genuinely broken links across 6 files; all fixed
• 36 full-path references updated, in live documents only
• version_claims.json's discovery sweep globbed docs/governance/*.md, so it
  silently stopped covering the moved files — widened to the three new directories
• .gitignore pointed at docs/governance/V3_0_PLAN.md, which no longer exists
• docs/README.md's directory map gained audits/ and history/

Every move is recorded by git as a rename, so history follows the files.

The check that was missing

nodus_gate verifies documented symbols, runnable blocks, opcodes, version
claims, invariants and staged flips — and nothing verified that a link went
anywhere. That is why this move broke eleven links silently, and why every one
of them was found by writing tests/test_doc_links_resolve.py rather than by
reading the diff.

Bounded deliberately: tracked files, relative links, .md targets, anchors
stripped. A link checker that needs the network gets disabled the first week it
goes red on someone's train.

Falsified: breaking one link in docs/README.md turns it red naming the file and
the target; the hermetic cases cover missing, present, anchored, external and
parent-relative targets, with a control so none of them can pass for a broken
matcher.

Checks

• nodus_gate --all — all ten phases, 306/306 doc blocks
• 0 broken links across every tracked markdown file
• 81 tests over the affected suites · ruff check . clean

🤖 Generated with Claude Code

https://claude.ai/code/session_01TnzKwmx6XecNEqP2482MuA