Knowledge Health and Agent Calls

Knowledge health (/know/health, under Trust in the Know sub-nav) reports what Leed records about your documentation: what is being edited, what has no source commit, and where each page came from. It needs the Growth plan.

It does not say a page has drifted, or that a page was checked against your code. Leed cannot know that from what it records. Checking a page against its code is done by running the Leed plugin, whose edits then show here as pages in revision and suggestions to review.

The view defaults to your documentation page types; the page type filter picks another, and an owner filter keeps the pages whose latest revision lists that person among its authors. It is not date-ranged: each section that needs a window fixes its own.

The headline figures

FigureWhat it counts
In revisionPages being edited now. This is the number on the Knowledge health badge in the sub-nav, left out at zero.
Since last revisionThe median time since a published page was last revised
UnverifiedPublished pages that have never carried a source id
Open review itemsOpen comment threads and pending suggestions
Broken linksExternal links found broken by the latest link check
The Knowledge health header with its page type and owner filters and the In revision, Since last revision, Unverified, Open review items and Broken links tiles

Next release preview

What release:docs will publish from staging, and what will fail, from the latest dry run: Will publish and Will fail, with the reason for each failure. Every past dry run is listed under it. Once the release exists, its run history is on its release scorecard.

Repeat corrections

Pages revised again within 7 days of being published. It is a signal to look at, not a verdict: a quick correction can mean the product changed, not that the docs were wrong.

Review backlog

Open comments and pending suggestions by age: under 2 days, 2–7 days, 1–2 weeks, and older.

Suggestion acceptance

Suggestions accepted against rejected over the last 90 days (or as far back as your plan’s history reaches), by source and by the person who made them. The sources are Operator MCP, Leed assistant, Editor, and Unknown for suggestions made before sources were recorded. Only people accept or reject suggestions; an agent can only make them.

Broken external links lists the broken links from the latest link check, and Link checks over time shows the bad links found on these pages in each daily run over the last 30 days. See link health.

Provenance

Each page row offers Edit, Analytics and Provenance. Provenance opens a side panel on the version live now:

  • Source: the source id the live version carries, or No source id;
  • Published: when it was published, with the publish type and the release name;
  • Written by: the revision’s creator and authors, with the Operator MCP or the Leed assistant when they edited the page during the revision;
  • Suggestions accepted and rejected while it was written, and the agent calls it was Served to agents.

The release name and the publish type both need release analytics (Growth). Without it the panel shows the publish date and how many published revisions shipped in a release, with Upgrade to see release names and publish types. The same panel appears in a page’s detail in Know and in the editor’s Page Analytics panel.

Agent calls

Agent calls (/know/health/agent-calls), titled What did the agent rely on?, is the evidence trail when an agent’s answer causes rework. It lists every Docs MCP call with the exact page versions it was served, whether the reader was signed in or anonymous, what the reader read in the next 15 minutes, and View this version for each page as it was then. The agent’s type is not recorded. The list takes a text search and the page type and agents filters, and pages through the calls.

Below Growth

Without the Growth plan the view still opens and shows its totals for pages in revision and unverified pages, with sample rows blurred beneath an upgrade prompt. Broken links stay available on every plan through leed settings brokenlinks list and the list_broken_links MCP tool.

Over MCP and the CLI

get_know_view reads this view as knowledgeHealth and Agent calls as agentCalls; get_next_release_preview returns the latest dry run. From a terminal: leed know show knowledgeHealth and leed know show agentCalls. See Reading Know from MCP and the CLI.

ESC