Skip to content
This page is also available as markdown at /docs/knowledge-health/overview.md. For the complete documentation index, see llms.txt.
Get started

How Knowledge Health works

Find contradictions, gaps, and stale pages across your docs, code, and connected sources.

The Knowledge Health page with the run banner, the open findings chart, and counts for each category

Knowledge Health scans your connected sources, compares them with each other and with your code, and finds existing issues.

Start a scan with Run now, or put scans on a schedule. You can assign any finding to Falconer, which drafts the proposed fix for you to review. You can also fix issues with your preferred coding agent through the Falconer MCP.

  • At least one connected source.
  • Credits in your balance, or your organization’s own model provider key.

Run now and Schedule appear on the Knowledge Health page when your organization uses credits or its own model provider key.

CategoryWhat it means
ContradictionTwo sources make claims that can’t both be true.
Stale docA doc describes knowledge that has since changed.
Coverage gapA topic comes up in Slack, meetings, code, or tickets, but no doc covers it.
RedundancyThe same knowledge is documented in more than one place.
Code driftA doc no longer matches what the code does.
  1. Knowledge Health checks the findings it already filed, so it doesn’t report the same problem twice.
  2. It compares your sources with each other and with your code, and checks recent pull requests.
  3. It files findings as it goes. The scan keeps running if you leave the page.
flowchart LR
  review["Review existing findings"]
  subgraph checks["Check in parallel"]
    cross["Across sources"]
    code["Against code and PRs"]
    stale["Stale content"]
    gaps["Coverage gaps"]
  end
  filed["File findings with evidence"]
  review --> cross & code & stale & gaps
  cross & code & stale & gaps --> filed