Page anchors
Every approved suggestion proves a link: the docs files it changed document behavior implemented at the source paths the originating change touched. DraftStack records each of those links as a page anchor.
Anchors accumulate automatically. Approving a suggestion again for the same pages strengthens its anchors and refreshes their verification time, so the ledger doubles as a per-page freshness record: the longer since a page’s anchors were last verified, the more likely it has drifted.
Freshness
Section titled “Freshness”The project.pageFreshness API returns every anchored page with its last verified time, oldest first. Use it to find the pages most likely to be stale instead of guessing.
Anchor pre-filter
Section titled “Anchor pre-filter”For high-volume repositories, anchors can act as a cheap deterministic gate ahead of the model. With the anchor pre-filter enabled, a pull request whose changed files touch nothing the docs have ever anchored to is skipped before any model call.
The pre-filter stays dormant until a repository has at least 20 anchor edges, and it is off by default. Leave it off until the ledger has organic coverage of the repository’s active areas, then watch the skipped activity for a week before trusting it.