Wiki Audit Demand and Freshness Loop

The evidence-driven maintenance loop attached to periodic wiki audits, established by the Content Program Policy. Two checks, both using live MCP tools.

D1 — Under-served real queries

misses = list_retrieval_queries(max_avg_results=1, since_days=N)   # admin-mcp, real traffic
for each miss:
    bundle = assemble_bundle(query=miss.query)                     # knowledge-mcp, the live gate

• Miss confirmed, owning page exists → a frontmatter/heading fix: put the query's discriminating vocabulary in the page summary (lifts every chunk) and the answering section's heading (lifts that section). Re-check after the async re-embed.
• Miss confirmed, no owning page → a content gap; queue it for the next writing tranche.

D2 — Tool-practice staleness

For the practice clusters (operations-research, data-science-practice, software-engineering-practices and other tool-heavy content): flag pages where verified_at is absent or older than ~12 months. Re-verification is a web check of the fast-decaying claims — versions, licensing, maintenance status, API spellings — followed by fixes and mark_page_verified. Decision-rule content decays slowly; tool-status content decays in a year.

Where this runs

The checks are steps in the local wiki-audit skill (whose legacy compound-tool pipeline is retired — implement with list_clusters/list_pages_by_filter/verify_pages/get_broken_links/get_orphaned_pages). SEO follow-ups ride the same loop: position/CTR deltas come from the search-visibility metrics on docker2.

See Also

• Content Program Policy
• Search Visibility Exporter