Navigation is the visible graph of an LLM Wiki. Canonical pages come first; graph views, local maps, retrieval, JSON, and APIs are secondary traversal surfaces that should point back to durable URLs.
Required navigation surfaces
| Surface | Purpose | Agent rule |
|---|---|---|
wiki/index.md |
Routing map for hubs, child pages, page types, owners, status, and core tasks. | Read before opening broad page sets. |
wiki/log.md |
Append-only evidence and review trail. | Use for changes, contradictions, and promotion history. |
| Breadcrumbs | Show parent hierarchy and canonical location. | Use to understand page scope and section membership. |
| Children | Expose local subtopics from hub pages. | Use when expanding from a hub to a precise page. |
| Typed related links | State why another page matters. | Prefer typed links over generic resources lists. |
| Backlinks and used-by | Show dependency and impact where available. | Check before moving or merging pages. |
| Sitemap and llms.txt | Public discovery for crawlers and agents. | List canonical public pages, not private artifacts or duplicates. |
Typed relation vocabulary
Use depends_on, prerequisite_for, part_of, has_part, example_of, implemented_by, supersedes, superseded_by, contradicts, source_for, related_to, and see_also.
Validation checks
- No orphan public pages.
- No duplicate canonical URLs.
- All public pages have breadcrumbs and at least one local related link.
- Moved routes redirect to final URLs and internal links point to the final URLs.
- llms.txt and sitemap.xml include canonical routes and exclude private or archive-only records.