Metadata is how an LLM Wiki tells humans, crawlers, and AI agents what a page is, where its canonical URL lives, who owns it, whether it is current, what sources support it, and what an agent may do with it.
Recommended Frontmatter
---
type: Reference
title: System Overview
slug: system-overview
canonical_url: https://example.com/reference/system-overview/
description: Current system boundary, owners, components, source traces, and review state.
resource: raw/architecture/2026-05-platform-review.md
tags:
- architecture
timestamp: 2026-05-11T00:00:00Z
llmwiki_status: authoritative
llmwiki_owner: Platform Team
llmwiki_source_status: source-linked
llmwiki_agent_use: read-cite-propose
llmwiki_review_cycle: quarterly
llmwiki_created_at: 2026-05-01T00:00:00Z
llmwiki_modified_at: 2026-05-11T00:00:00Z
llmwiki_version: "1.0.0"
page_type: reference
section: architecture
audience: both
owner: Platform Team
status: current
quality_class: reviewed
source_status: source-linked
last_reviewed: 2026-05-11
review_cycle: quarterly
sensitivity: internal
agent_use: allowed-with-citation
parent: /reference/
children: []
aliases:
- system map
redirects_from:
- /old-system-overview/
primary_topic: system architecture
trust_level: authoritative
source_trace:
- raw/architecture/2026-05-platform-review.md
memory_type: ""
promotion_status: ""
validation_tier: "tier1-public-page"
source_scope: ""
target_scope: ""
source_event_id: ""
evidence_hash: ""
durable_copy_location: ""
redaction_status: ""
public_safe_rewrite_status: ""
claim_status: reviewed
freshness_rule: review every quarter and after major architecture changes
last_verified: 2026-05-11
reviewer: Architecture owner
updated: 2026-05-11
created: 2026-05-01
noindex: false
sitemap_include: true
non_claims: []
jsonld_type: TechArticle
social_title: System Overview
social_description: Current reviewed system boundary and source-backed architecture context.
related:
- title: Services
url: /reference/services/
relation: has_part
typed_relations:
depends_on: []
prerequisite_for: []
part_of:
- /reference/structure/
has_part:
- /reference/services/
example_of: []
implemented_by: []
supersedes: []
superseded_by: []
contradicts: []
source_for: []
related_to:
- /reference/navigation/
see_also:
- /reference/metadata/
---
Required Fields
| Field | Why it matters |
|---|---|
type |
OKF concept-document type. Required for non-reserved Markdown files under wiki/. |
title |
Stable page identity for humans, search, and citations. |
slug |
Lowercase kebab-case route component. |
canonical_url |
One durable public URL per important concept, entity, workflow, standard, source type, or task. |
description |
Answer-first summary for search snippets, agents, cards, and llms.txt. |
routing_summary |
One-paragraph route hint that explains why and when agents should open a durable report, architecture record, coding standard, best-practice note, or preserved handoff record. |
page_type |
Allowed values: concept, guide, reference, tool, template, example, comparison, glossary, changelog, evidence, or report. |
section |
Navigation parent or handbook section. |
audience |
Allowed values: human, agent, or both. |
status |
Allowed values: draft, reviewed, current, stale, deprecated, archived, or blocked. |
quality_class |
Editorial quality level such as stub, start, reviewed, canonical, or needs-repair. |
source_status |
Whether the page is source-linked, source-needed, canonical-linked, derived, or unsupported. |
llmwiki_status, llmwiki_owner, llmwiki_source_status, llmwiki_agent_use |
Governance overlay that turns OKF-readable pages into LLMWikis-safe pages. |
owner |
Prevents ownerless authority. |
last_reviewed |
Makes freshness visible. |
review_cycle |
Defines when stale detection should trigger. |
sensitivity |
Prevents accidental exposure or unsafe agent use. |
agent_use |
States whether agents may read, cite, summarize, propose edits, or must avoid the page. |
matm_scope and memory_kind |
Name scope, memory kind, source event, curator decision, review state, sensitivity, and retrieval policy for governed MATM records. Practical MATM deployments should distinguish global_public, global_private, project_public, project_private, agent_session, and emergency_reconnect_archive when those boundaries affect retrieval or recovery. |
parent and children |
Power breadcrumbs, hub pages, and local hierarchy. |
aliases and redirects_from |
Preserve alternate names without creating duplicate canonicals. |
related |
Keeps navigation explicit and retrieval-ready. |
Strongly Recommended Fields
Use resource, tags, timestamp, llmwiki_review_cycle, llmwiki_created_at, llmwiki_modified_at, llmwiki_version, llmwiki_confidence, primary_topic, trust_level, source_trace, claim_status, freshness_rule, reviewer, updated, created, noindex, sitemap_include, jsonld_type, social_title, social_description, social_image, and typed_relations when the page is public, source-backed, OKF-exportable, or agent-facing.
OKF-compatible frontmatter profile
- Keep OKF fields and LLMWikis fields together; do not replace
page_type,source_status, oragent_usewith looser tags. - Use
typefor OKF concept type andpage_typefor the LLMWikis taxonomy. - Use
resourcefor the primary source pointer when one exists, and keep richer evidence insource_trace. - Use
timestampfor the OKF-friendly date-time and keep human review semantics inlast_reviewed,updated, andllmwiki_modified_at. - Preserve unknown frontmatter keys during migration.
- Run migration helpers in dry-run mode first.
- Make OKF link issues warnings during draft repair and strict failures during public release.
- Never treat OKF field validity as proof of authority, source trust, privacy review, or edit permission.
OKF and LLMWikis mapping
| OKF field | LlmWikis field | Required? | Mapping rule |
|---|---|---|---|
type |
page_type |
Yes for OKF concept docs | Keep both; type can be title-case, page_type stays controlled lowercase. |
title |
title |
Required in LLMWikis public pages | Use the durable concept name. |
description |
description and routing_summary |
Required or strongly recommended | Description identifies the page; routing summary tells agents when to load it. |
resource |
source_trace, checksum_or_source_identity |
When sourced | Point to raw evidence or durable source identity; keep multi-source trails in source_trace. |
tags |
tags, primary_category, section |
Optional | Useful for filtering but not a replacement for canonical route structure. |
timestamp |
last_reviewed, updated, llmwiki_modified_at |
Recommended | Prefer UTC date-time; keep review meaning visible. |
Two-Tier Metadata Model
| Tier | Use for | Required posture |
|---|---|---|
| Tier 1: ordinary public page | Guides, references, examples, comparisons, entity pages, source summaries, and public handbook routes. | Use the normal required fields, source status, owner, review date, sensitivity, and agent-use rule. |
| Tier 2: promoted memory or dogfood evidence | Pages or packets derived from private agent-memory, MATM-style events, protected tool submissions, handoff traces, or internal dogfood evidence. | Add promotion status, memory type, source scope, target scope, evidence hash, redaction state, lane review, public-safe rewrite status, supersession fields, and explicit non-claims. |
Promotion Metadata Fields
| Field | Allowed values or shape | When required |
|---|---|---|
memory_type |
fact, decision, procedure, risk, preference, hypothesis, evidence, deprecation, conflict | Tier 2 promotion packets and dogfood-evidence-backed pages. |
promotion_status |
candidate, blocked, redacted, reviewed, published, superseded | Any content moving from private memory into public guidance. |
validation_tier |
tier1-public-page, tier2-promoted-memory, tier3-external-standard | Public routes that need machine-readable review posture. |
source_scope |
global_public, global_private, project_public, project_private, agent_session, emergency_reconnect_archive, plus legacy or local values such as session, project, agent_team, and agent_repo when mapped explicitly | Promotion, MATM, and private-memory evidence. |
target_scope |
project, organization, public | When a narrower private observation is generalized. |
source_event_id |
Stable private or public source event identifier. | Promotion packets, tool-submit cases, Memory Events, and handoff-derived guidance. |
evidence_hash |
Algorithm-prefixed hash such as sha256:.... |
Tier 2 when source content cannot be public. |
durable_copy_location |
Private resolver, archive path, source-record URL, or canonical external route. | Tier 2 source possession gate. |
redaction_status |
not-needed, needed, in-review, reviewed, blocked | Any private or sensitive source-derived public copy. |
public_safe_rewrite_status |
not-needed, draft, reviewed, blocked | Private-memory and dogfood-derived public pages. |
last_verified |
ISO date. | Time-sensitive public claims and promoted lessons. |
non_claims |
List of unsupported interpretations the page explicitly denies. | Profile G, MATM, protocol, tool, and standards-adjacent pages. |
Search result fields
| Field | Where it appears | Search behavior |
|---|---|---|
title |
Result heading, route card, citation label. | Should name the durable concept, not a vague report title. |
description |
Search excerpt, llms.txt summary, social metadata. | Should answer what the page is for in one sentence. |
canonical_url |
Result target and citation path. | Aliases and old URLs should redirect here instead of competing. |
page_type and section |
Result grouping and route shortcuts. | Lets broad searches recover into guide, reference, operation, example, or comparison lanes. |
status, source_status, and last_reviewed |
Freshness and trust signals. | Agents should treat stale, draft, source-needed, and contradicted results differently from current reviewed pages. |
routing_summary, checksum_or_source_identity, and discovery_surface |
Agent-routing and crawlability signals for durable source-memory pages. | Lets agents decide what to load without broad archive scans. |
aliases and redirects_from |
Query recall and migration compatibility. | Search can recognize old names without creating duplicate canonical answers. |
Validation Rules
- Missing
typein a non-reservedwiki/Markdown concept file fails OKF lint. - Root
wiki/index.mdfrontmatter containing anything exceptokf_versionfails OKF lint. - Nested
index.mdfrontmatter fails OKF lint; nested indexes should be plain routing files. - Migration that drops unknown custom keys fails review.
- Missing
llmwiki_status,llmwiki_owner,llmwiki_source_status, orllmwiki_agent_usefails LLMWikis governance lint unless the tool is intentionally running OKF-only syntax checks. - Missing
title, invalidstatus, invalidpage_type, duplicatecanonical_url, or missing publiccanonical_urlfails lint. - Missing public
description, breadcrumb data, or local related link warns or fails depending on publication policy. - Durable report, coding-standard, architecture, best-practice, and handoff-preservation pages missing
routing_summary,checksum_or_source_identity, ordiscovery_surfacefail agent-routing lint. - Tier 2 promoted-memory pages missing
promotion_status,memory_type,source_scope,target_scope,evidence_hash,redaction_status, orpublic_safe_rewrite_statusfail promotion lint. - A public page with
trust_level: dogfood-evidence-backedmust includenon_claims,last_verified, and a link to a promotion gate or release note. - Duplicate titles warn; duplicate canonical URLs fail.
- Stale pages without review status warn.
- Contradicted pages without a
contradictsrelation fail. - Public pages with
noindex: trueneed an archive, evidence, duplicate, or privacy reason.