Use cases

Keep the docs true

Have an agent check a doc page against the code it describes, and fix the parts that drifted.

The work

Point an agent at a doc page and the code it claims to describe. It checks each statement against the current code, corrects what has drifted, and opens a pull request. A person confirms each correction is right before it merges.

Why it stalls

Code changes on every merge. A doc only changes when a person remembers to update it, so it falls behind quietly, and nobody notices until a reader hits the gap first.

How it runs

Plan, code, review, merge, verify

plan
Reads the doc page and the code it describes, and lists every claim that needs checking.
code
Corrects each claim that no longer matches the code, and cites the symbol it checked against.
review
Re-checks every correction against the current code, ignoring the doc's old wording.
merge
Opens a pull request limited to the doc page named.
verify
Confirms the doc's claims now match the code, and nothing it corrected was already right.

What you need on hand

The doc page that might be stale
The code it should describe
A person to confirm each correction before it ships

Proof, not a promise

No example task or measured figure fits this job yet. What's real is the mechanism: an agent reads the code a doc page claims to describe, corrects each statement that no longer matches, and a person confirms the correction before it merges.

Don't know what to write