README: lead with agent problems, not document types

[emafriedrich]

Summary

• Reorders the README around five concrete problems agents cause (guessing rules, stale docs, can't tell draft from settled, silent ambiguity resolution, undocumented legacy rules) paired one-to-one with what closes each one — before any DR/RFC/Spec terminology.
• Moves the DR/RFC/Spec breakdown into "The vocabulary, if you want it," opening with why each type exists (checkable approval, explicit not-yet-true, proven-not-declared) instead of leading with definitions.
• Folds the standalone "Why knowledge drifts" section into the matching problem/fix pair instead of repeating it.
• No change to the concrete example, quick start, how-it-works, limits, or comparison sections — only their position and the framing around them.

Goal: make the value legible to a semi-senior/senior reader who has never heard of an RFC or a DR, without losing the concrete evidence (the real decision record, the field numbers) that makes the pitch credible.

Test plan

• Checked no other file links to a now-removed anchor in README.md
• Read-through for tone/accuracy

🤖 Generated with Claude Code