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

Open Knowledge Format for LLM Wikis

Open Knowledge Format (OKF) gives LLM Wikis a portable file shape: a directory of Markdown files with YAML frontmatter, reserved index.md and log.md files, and tolerant readers. LLMWikis uses OKF as the bundle layer and adds the governance layer: source status, ownership, trust labels, citation rules, redaction, review gates, and agent stop conditions.

Compatibility claim

LlmWikis publishes an OKF-compatible profile for starter bundles and local wiki folders. This is not certification, registry enrollment, hosted validation, automatic import, automatic sync, public MCP, public write API, or a claim that Google or UAIX endorses this site.

What OKF Provides

OKF layer Practical effect LlmWikis use
Markdown files Human-readable knowledge survives outside a proprietary app. Use wiki/ as the bundle root for reviewed concept files.
YAML frontmatter Agents and tools can inspect structured fields before reading prose. Require type and preserve unknown custom keys.
index.md Progressive-disclosure routing entry point. Root wiki/index.md routes namespaces, names project index/log counterparts, and may contain only okf_version frontmatter.
log.md Human-readable history and change trail. Use newest-first date headings. In multi-project roots, record workspace coordination and point to project logs.
Tolerant consumers Readers should not break on unknown fields, missing optional metadata, or unresolved local links. Lint warnings guide cleanup, but agents keep unknown fields intact.

Scope: This base file contract applies across LLMWikis profiles, including ordinary internal wikis, public handbook wikis, handoff-ready wikis, long-run agent wikis, promotion-ready dogfood wikis, OKF packages, and governed MATM Wiki extensions. MATM Memory Events and Memory Records add scoped agent-memory artifacts; they do not replace reviewed Markdown concept pages or reserved index/log routing.

What LLMWikis Adds

LlmWikis rule Required fields or behavior Reason
Governance overlay llmwiki_status, llmwiki_owner, llmwiki_source_status, and llmwiki_agent_use. OKF validity is not authority, review, permission, or source trust.
Source lane raw/ remains immutable and outside the compiled OKF concept graph unless linked. Compiled wiki pages stay inspectable while raw evidence stays preserved.
Agent boundary Agents read, cite, propose, and stop; reviewed pages are not silently overwritten. Prevents format compatibility from becoming automatic write permission.
Discovery boundary sitemap, llms.txt, manifests, and public pages list canonical public routes only. Private intake, archives, proposals, and package mirrors stay out of public discovery.
Promotion gates Private evidence needs durable copy, redaction, lane review, public-safe rewrite, and release notes before public use. Private dogfood evidence can inform guidance without leaking the trace.

Recommended Bundle Shape

README.md
AGENTS.md
SCHEMA.md
okf.profile.json
frontmatter.schema.json
raw/
  README.md
wiki/
  index.md
  log.md
  knowledge-map.md
  global/
    index.md
    governance.md
    source-map.md
  {Site}/
    index.md
    source-policy.md
    review-gates.md
scripts/
  llmwiki-okf-validate.js
  llmwiki-okf-migrate-frontmatter.js

Multi-Tenant Path Example

wiki/{client}/{workspace}/{project}/index.md
wiki/{client}/{workspace}/{project}/log.md
wiki/{client}/{workspace}/{project}/concepts/
wiki/{client}/{workspace}/{project}/runbooks/
wiki/{client}/{workspace}/{project}/decisions/

Use this shape when client, workspace, or project boundaries matter. The root wiki/index.md routes to tenant and project counterparts; it should not absorb every client file into wiki/global/ or one broad site folder. Project indexes can route to child indexes, concept hubs, and high-value entry points as the project grows.

Index/Log Context Budget

File Should answer Should not become
wiki/index.md Where should I go next for this scope? A complete inventory of every file under the wiki.
wiki/log.md What changed at this level? A combined event stream for every project, client, or workspace.
Child indexes/logs What detail belongs below this namespace? A reason to flatten all child detail back into the root.

Metadata Mapping

OKF field LLMWikis field Required? Notes
type page_type Yes Keep type for OKF. Preserve page_type for LLMWikis page taxonomy.
title title Strongly recommended Used for search cards, route labels, and citations.
description description and routing_summary Recommended Description says what the page is; routing summary says when to load it.
resource source_trace or checksum_or_source_identity When sourced Point to raw evidence, canonical external routes, or durable source identity.
tags tags, primary_category, section Optional Useful for retrieval and clustering, not a replacement for typed links.
timestamp last_reviewed, updated, or llmwiki_modified_at Recommended Use UTC date-time when possible; keep review dates visible.

Minimal Concept File

---
type: "Reference"
title: "Deployment Process"
description: "Reviewed deployment workflow, approvals, rollback path, and agent boundaries."
resource: "raw/releases/2026-05-process-review.md"
tags: ["operations", "deployment"]
timestamp: "2026-07-02T00:00:00Z"
llmwiki_status: "authoritative"
llmwiki_owner: "Platform Team"
llmwiki_source_status: "source-linked"
llmwiki_agent_use: "read-cite-propose"
page_type: "runbook"
source_status: "source-linked"
agent_use: "read-cite-propose"
---

# Deployment Process

State the current workflow, approvals, rollback path, source evidence, and stop conditions.

Agent Consumption Rules

  1. Phase 1: parse the bundle. Load wiki/index.md, validate reserved files, preserve unknown frontmatter keys, and record warnings without dropping content.
  2. Phase 2: apply governance. Inspect status, owner, source status, sensitivity, agent use, citations, and review gates before answering or editing.
  3. Stop on governance gaps. Missing owner, source status, permission, redaction, or authority should block confident answers and durable writes.
  4. Stage updates. Use proposal-only updates unless a human has granted scoped write permission and required checks pass.

Wizard And Starter Integration

The setup wizard emits OKF profile fields in the generated model and a copyable Visitor AI OKF Digest. The starter bundle ships okf.profile.json, wiki/index.md, wiki/log.md, OKF-ready templates, and helper scripts for validation and frontmatter migration.

Non-Claims

  • OKF compatibility is not certification or endorsement.
  • OKF validation is not source trust, legal review, privacy review, or production approval.
  • The LLMWikis starter does not create a public MCP server, public write API, hosted importer, event bus, vector database, or autonomous publisher.
  • Unknown OKF fields should be preserved; they do not automatically become LLMWikis authority fields.

Sources