update-documentation

Name the change in one sentence tied to a commit or ADR, choose the target path using the placement gates, rewrite stale claims with evidence=path:line citations you actually opened, then record the change in the project ledger. Corrections of false statements also require an amendment row.

Run the placement gates in order: the falsification test separates work records from documentation, forcing conditions send plans and findings to work/, decisions go to ADRs, and the Diátaxis compass assigns the rest to tutorials, how-to, reference, or explanation.

An evidence marker is an HTML comment such as trust:trustchecked with evidence=<path>:<line> attached to a factual claim about the running system. Every cited line must be re-opened and confirmed before the task completes; inferred line numbers are treated as failures.

Do not use it to create the documentation tree from scratch (use scaffold-documentation) or to reorganize the tree wholesale (use migrate-documentation). It handles individual updates, corrections, and placement of new pages.

The cap prevents a documentation edit from turning into a full verification project that never lands. Spans beyond two are recorded in the docs tree's trust-debt file with a blocked note describing what would settle them.

No. The ledger extension activates only when the project config sets docs.tool, automating the evidence, record, and link checks. Without it, the same obligations are performed manually, including hand-verifying every evidence line.