---
name: doc-audit-reads-whole-file
description: "a doc-parity audit that reads only the DIFF misses stale passages outside it — audit the whole published page against the head's rendered behavior"
metadata: 
  node_type: memory
  type: feedback
  originSessionId: 494e107d-2583-476c-96b4-210b1e214503
  modified: 2026-08-02T03:59:30.745Z
---

At the W5 gate I verified knocking.md by reading the 13e94d5..31b4d2f **diff** and confirmed the same-machine caveat was replaced — while ~10 lines below the diff, an untouched passage still told users cross-node `redeem --mutual` "currently does nothing", falsified by #92 **in the same wave**. deployah caught it at intake by rendering `spt knock redeem --help` from the head binary and reading the whole page.

**Why:** the stale-carried-forward-sentence class ([[stale-carried-forward-sentence]]) lives precisely OUTSIDE the diff — the sentences whose condition died are by definition the ones nobody touched. Same shape as tagging-a-doc-without-auditing-it (todlando's #88-time miss, named the same day).

**How to apply:** when a wave changes behavior a published doc describes, the gate audit reads the ENTIRE page (and greps the docs-site for hedges like "currently does nothing", "until it lands", "tracked as its own request") and verifies each against the head's rendered output — never just the changed hunks. Cost me a golden respin window on v0.51.0 (2026-08-01).