Skip to content
LlmWikis.orgLLM Wiki handbook
UAIX canonical
Menu
UAIX canonical
Source map LLM Wiki handbook llms.txt What is an LLM Wiki? Setup wizard Checklist Specification Metadata Navigation vs RAG vs AI Memory Source policy UAI-1 spec

LlmWikis knowledge page

Navigation Standard

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 Scoped routing map for hubs, child indexes, page types, owners, status, core tasks, and project index/log counterparts in multi-project roots. Read before opening broad page sets.
source-memory guide Routing map for durable reports, coding standards, architecture records, best practices, and handoff-preservation evidence. Use before opening raw archives or broad report folders.
wiki/log.md Append-only evidence and review trail at the relevant scope. Use root log for workspace coordination and project logs for detailed 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.

OKF reserved files

  • Root wiki/index.md is the OKF routing entry. It may include frontmatter with only okf_version.
  • Nested index.md files are local routing pages and should not include frontmatter.
  • wiki/log.md is the OKF history file. Use newest-first date headings.
  • Every other Markdown file under wiki/ is a concept file and should include frontmatter with type.
  • Broken local links warn during draft repair and fail strict public release checks.

Index/log context budget

  • An index answers where to go next; it should route to child indexes and high-value entry points rather than become an all-files inventory.
  • A log answers what changed at this level; it should point to child logs rather than become an all-project event stream.
  • Use explicit tenant or project paths such as wiki/{client}/{workspace}/{project}/index.md, wiki/{client}/{workspace}/{project}/log.md, and wiki/{client}/{workspace}/{project}/concepts/ when boundaries matter.

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.
  • Durable source-memory records have stable paths, clear headings, routing summaries, review state, last reviewed dates, source/evidence links, checksum or source identity, and an index/source-memory guide/sitemap/llms.txt route.