Page Coverage Guide
The Content checklist in PageStatus tracks content enrichment layers that a page can have. Pages with more layers are better sourced, more useful, and easier to maintain. This guide explains each layer.
Some items are type-specific: the Overview check only applies to article and diagram format pages; the Facts check only applies to person and organization pages. Other items appear on all pages.
Numeric metrics (tables, diagrams, links, footnotes, references) show a target that scales with page word count — a 5,000-word article is expected to have more tables and citations than a 500-word stub. Targets also vary by content format (table-format pages expect more tables; index pages expect more links). Boolean items (summary, schedule, entity, edit history, overview) are simply present or absent.
Structured Summary
A machine-generated summary with three parts: a one-liner, 3-5 key points, and a bottom line. Generated by the improve pipeline and stored in frontmatter as structuredSummary. A basic llmSummary (flat text) also counts, but the structured format is preferred.
Why it matters: Gives readers a quick overview without reading the full page. Powers search result snippets and the page card views.
How to add:
pnpm crux content improve <page-id> --tier=standard --apply
Update Schedule
The updateFrequency frontmatter field (in days) that says how often a page should be reviewed. Drives the overdue tracking system on the /internal/updates dashboard.
Why it matters: Prevents pages from going stale. Fast-moving topics (LLM capabilities, policy developments) need frequent updates; evergreen topics (historical events) need less.
How to add: Set updateFrequency: N in the page's frontmatter, where N is the number of days between reviews. Common values: 21 (3 weeks), 60 (bimonthly), 90 (quarterly), 180 (biannual).
Entity Data
A YAML entity definition in data/entities/ with type, description, related entries, and sources. Entities power the info box, related pages sidebar, backlinks, and the explore table.
Why it matters: Pages without entity data are invisible to the wiki's graph — they don't appear in related pages, can't be linked via <EntityLink>, and lack structured metadata.
How to add: Create a YAML file in the appropriate data/entities/*.yaml file for the entity's type. See existing entities for the schema.
Overview Section
A ## Overview heading section that introduces the page's topic and scope. Detected by the presence of a heading literally named "Overview" in the page content. Scored for article and diagram format pages only.
Why it matters: An overview section helps readers orient themselves quickly and improves AI-generated summaries and search snippets. Structural quality scoring rewards pages that clearly introduce their topic.
How to add: Add ## Overview as the first or second heading in the MDX file, followed by 1-3 paragraphs that summarize the topic. Many high-quality wiki pages use this pattern.
Anchor: overview-section
Tables
Data tables (markdown or HTML) that present structured information. The chip shows the count of tables on the page.
Why it matters: Tables make pages more scannable and useful as reference material. They're especially important for comparison pages and quantitative topics.
How to add: Add markdown tables to the page content.
Diagrams
Visual content: Mermaid diagrams, charts, or Squiggle estimate models. The chip shows the count of diagrams on the page.
Why it matters: Diagrams convey relationships, flows, and quantitative estimates that are hard to express in prose. They make complex topics more accessible.
How to add: Add <MermaidDiagram> components or <SquiggleEstimate> components to the page content.
Internal Links
Links to other wiki pages via <EntityLink> or standard markdown links. The chip shows the count of internal links.
Why it matters: Internal links improve graph connectivity. More links mean better related-page suggestions, stronger backlink networks, and easier navigation between topics.
How to add: Use EntityLink with the id prop for registered entities, or standard markdown links like /wiki/E123 for other pages.
Footnotes
Footnote citations [^N] with source references at the bottom of the page. The chip shows the count of footnotes.
Why it matters: Footnotes connect specific claims to their sources. They're the foundation for the citation verification system (quotes + accuracy checking).
How to add: Add [^N] footnote markers in the text and corresponding [^N]: source definitions at the bottom.
References
Curated external resources linked to the page via <R> (ResourceLink) components, cited_by fields in resource YAML, or URL matching at build time. The chip shows the total count.
Why it matters: References connect wiki content to primary sources — papers, blog posts, official documents. They appear in the References section at the bottom of the page.
How to add: Use <R id="resource-id"> in the page content, or add cited_by entries in data/resources/*.yaml.
Citation Quotes
Supporting quotes extracted from cited sources that back up specific claims on the page. Shown as 12/15 meaning 12 of 15 citations have extracted quotes.
Why it matters: Quotes provide verifiable evidence for claims. They power the citation overlay UI that lets readers see the source text for each footnote.
How to add:
pnpm crux citations extract-quotes <page-id>
Accuracy Checked
Citations that have been verified against their original sources for factual accuracy. Shown as 10/15 meaning 10 of 15 citations have been accuracy-checked.
Why it matters: Accuracy checking catches hallucinated citations, misquoted sources, and outdated information. It's the most important layer for trustworthiness.
How to add:
pnpm crux citations verify <page-id>
Edit History
Tracked changes from improve pipeline runs and manual editing sessions. Stored in the wiki-server PostgreSQL database and displayed in the Change History section.
Why it matters: Edit history creates accountability — you can see when a page was last improved, by which model, and what changed. It also helps identify pages that haven't been touched in a long time.
How to add: Edit history is created automatically by the improve pipeline (--apply flag) and by manual session logs. Use pnpm crux edit-log view <page-id> to inspect.
Entity Facts
Canonical facts defined for this entity in KB YAML files. Used by <KBF> components in the page content to render structured data inline. Scored for person and organization pages only (not concept, approach, risk, or analysis pages).
Scoring: green = 5+ facts, amber = 1-4 facts, red = 0 facts.
Why it matters: Canonical facts make entity data machine-readable and maintainable. Instead of burying numbers in prose (where they go stale), facts are defined once and updated in a single YAML file.
How to add: Create or update the entity's entry in packages/kb/data/things/ YAML files. Use <KBF entity="slug" property="property-name" /> in the page content to render values.
Anchor: entity-facts
Backlinks (info-only)
The number of other wiki pages that link to this page. Shown as an informational item — not scored (it's not directly under the page author's control).
Why it matters: A page with many backlinks is well-integrated into the knowledge graph. Low backlink counts suggest the page is an orphan that readers can't easily discover.
How to increase: Add EntityLink references (pointing to this page) from related pages. Improve the page quality so other pages naturally reference it.