Project › Published pages

Published pages.

At a glance

Nav entries

Pages listed in docs.config.json.

Spec-backed

Canonical source lives in external/ai-contributor-spec.

Generated MD

Unique upstream Markdown sources copied into src/content/generated-spec.

Site-authored

Presentation, orientation, or site self-documentation.

What counts as covered

A page is covered when it has a route in docs.config.json, a matching Astro page or content-collection MD/MDX, and a canonical source mapping. Spec-backed pages point at the pinned spec submodule or a generated projection from it. Site-authored pages are allowed only for navigation, orientation, presentation, and this site’s own operating documentation.

The drift gate for this inventory is scripts/check-doc-nav.mjs. It checks that configured doc entries have pages, that docs pages are present in the config, and that cross-page anchors referenced from docs content resolve.

Coverage by section

Section	Pages
Start	3
Specification	6
Audit	4
Skills	3
Project	7

Published inventory

Section	Page	Canonical source	Inputs	Type
Start	Overview	`src/content/docs/docs/index.mdx`	`src/content/docs/docs/index.mdx`source	site-authored
Start	Quickstart	`README.md`	`README.md`source	spec-backed
Start	Adoption guide	`AI-CONTRIBUTOR-GUIDE.md`	`AI-CONTRIBUTOR-GUIDE.md`source	spec-backed
Specification	Full specification	`AI-CONTRIBUTOR-SPECIFICATION.md`	`AI-CONTRIBUTOR-SPECIFICATION.md`canonical prose `AI-CONTRIBUTOR-RULE-CATALOG.json`rule data	spec-backed
Specification	Pillars overview	`AI-CONTRIBUTOR-RULE-CATALOG.json`	`AI-CONTRIBUTOR-RULE-CATALOG.json`source	spec-backed
Specification	Levels overview	`AI-CONTRIBUTOR-RULE-CATALOG.json`	`AI-CONTRIBUTOR-RULE-CATALOG.json`source	spec-backed
Specification	Coverage map	`AI-CONTRIBUTOR-COVERAGE.md`	`AI-CONTRIBUTOR-COVERAGE.md`coverage prose `AI-CONTRIBUTOR-RULE-CATALOG.json`coverage data	spec-backed
Specification	Rule catalog	`docs/RULE-CATALOG-FORMAT.md`	`AI-CONTRIBUTOR-RULE-CATALOG.json`rule data `docs/RULE-CATALOG-FORMAT.md`format prose	spec-backed
Specification	Threat model template	`docs/threat-model-template.md`	`docs/threat-model-template.md`source	spec-backed
Audit	How the audit works	`AI-CONTRIBUTOR-AUDIT-MODEL.md`	`AI-CONTRIBUTOR-AUDIT-MODEL.md`source	spec-backed
Audit	The profile	`docs/AI-CONTRIBUTOR-AUDIT-PROFILE.md`	`docs/AI-CONTRIBUTOR-AUDIT-PROFILE.md`source	spec-backed
Audit	No-install prompt	`AI-CONTRIBUTOR-AUDIT-PROMPT.md`	`AI-CONTRIBUTOR-AUDIT-PROMPT.md`source	spec-backed
Audit	A stamped audit	`AI-CONTRIBUTOR-AUDIT.md`	`AI-CONTRIBUTOR-AUDIT.md`root summary `.ai-contributor-audit/AI-CONTRIBUTOR-CHECKLIST.md`checklist `.ai-contributor-audit/AI-CONTRIBUTOR-AUDIT-LOG.md`audit log	spec-backed
Skills	ai-contributor-audit-profile	`skills/ai-contributor-audit-profile/SKILL.md`	`skills/ai-contributor-audit-profile/SKILL.md`source	spec-backed
Skills	ai-contributor-audit	`skills/ai-contributor-audit/SKILL.md`	`skills/ai-contributor-audit/SKILL.md`source	spec-backed
Skills	ai-contributor-audit-fix	`skills/ai-contributor-audit-fix/SKILL.md`	`skills/ai-contributor-audit-fix/SKILL.md`source	spec-backed
Project	Releases	`CHANGELOG.md`	`CHANGELOG.md`source	spec-backed
Project	Contributing	`CONTRIBUTING.md`	`CONTRIBUTING.md`source	spec-backed
Project	Authors	`AUTHORS.md`	`AUTHORS.md`source	spec-backed
Project	Tooling	`TOOLING.md`	`TOOLING.md`source	spec-backed
Project	Security policy	`SECURITY.md`	`SECURITY.md`source	spec-backed
Project	Glossary	`docs/glossary.md`	`docs/glossary.md`source	spec-backed
Project	Published pages	`src/content/docs/docs/doc-coverage.mdx`	`src/content/docs/docs/doc-coverage.mdx`source	site-authored

Generated upstream sources

These unique Markdown sources are projected into two locations by pnpm prepare:spec:

src/content/docs/ — the Starlight route the page is served from.
src/content/generated-spec/ — the body-only projection that composed MDX pages (e.g. coverage-map.mdx, rule-catalog.mdx) pull in via getEntry('generatedSpec', key) + render() so they can mix upstream prose with their own component chrome.

Source	Projection
`README.md`	generated Markdown
`AI-CONTRIBUTOR-GUIDE.md`	generated Markdown
`AI-CONTRIBUTOR-SPECIFICATION.md`	generated Markdown
`AI-CONTRIBUTOR-COVERAGE.md`	generated Markdown
`docs/RULE-CATALOG-FORMAT.md`	generated Markdown
`docs/threat-model-template.md`	generated Markdown
`AI-CONTRIBUTOR-AUDIT-MODEL.md`	generated Markdown
`docs/AI-CONTRIBUTOR-AUDIT-PROFILE.md`	generated Markdown
`AI-CONTRIBUTOR-AUDIT-PROMPT.md`	generated Markdown
`AI-CONTRIBUTOR-AUDIT.md`	generated Markdown
`skills/ai-contributor-audit-profile/SKILL.md`	generated Markdown
`skills/ai-contributor-audit/SKILL.md`	generated Markdown
`skills/ai-contributor-audit-fix/SKILL.md`	generated Markdown
`CHANGELOG.md`	generated Markdown
`CONTRIBUTING.md`	generated Markdown
`AUTHORS.md`	generated Markdown
`TOOLING.md`	generated Markdown
`SECURITY.md`	generated Markdown
`docs/glossary.md`	generated Markdown

The rule catalog is intentionally not generated as Markdown; it is consumed as structured data for the rule-catalog page and specification data.

Source	Projection
`AI-CONTRIBUTOR-RULE-CATALOG.json`	JSON projection

What is not covered

There are no known missing docs pages in the current navigation. The boundaries are deliberate:

Internal implementation files under tools/, test fixtures, and collector internals are not documented page by page. The public docs cover their command surface through Tooling, Rule catalog, and the audit pages.
Example template contents are not mirrored file by file. The TypeScript + pnpm recipe documents the scaffold path and the expected adoption flow.
License files are represented in the site footer rather than a dedicated docs page.
Unpinned upstream changes are not covered until the spec submodule is updated and pnpm prepare:spec is run.

Maintenance rule

When adding, removing, or renaming a docs page, update docs.config.json first. The config is the single source of truth for sidebar order, breadcrumbs, pagination, search, source links, and this coverage page. Do not edit src/content/generated-spec/ or src/content/docs/ by hand for spec-backed entries; change the pinned spec source or route mapping, then regenerate.