Open Knowledge Format and the LLM Wiki

Executive TLDR

What To Take Away

01

Structure beats memory paste

Agents need context that survives outside one chat. A pile of files is not the same thing as a navigable memory system.

02

OKF is early

Open Knowledge Format v0.1 is useful to study as a draft open specification, not as a mature standards-body standard.

03

The bundle is the unit

An LLM wiki becomes more portable when it has a clear entry point, concept pages, source pointers, examples, and caveats.

04

Claims need states

Separate source claim, verified fact, teaching interpretation, speculation, and excluded claim before publishing or reusing the bundle.

05

Agents need paths

Indexes, links, and metadata let an agent enter the bundle, choose the next page, and stop before over-reading.

06

Build conservatively

Start with OKF v0.1 basics, then label extra folder conventions as local implementation choices.

Plain English

The Short Version in Plain English

The idea behind an LLM wiki is simple: instead of stuffing everything into one prompt, you keep durable notes that an agent can read, follow, and reuse later.

The hard part is not markdown. The hard part is making the notes predictable enough that a different agent, teammate, or future version of you can find the right entry point without guessing your folder habits.

Open Knowledge Format v0.1 matters here because it points toward a shared shape for knowledge files: markdown documents, YAML frontmatter, typed concepts, and links that can carry relationships.

This page treats OKF as a draft open format and teaches the practical pattern around it. It does not claim that OKF is fully adopted, final, or required for every knowledge base.

The useful move for builders is to separate the verified OKF basics from local implementation patterns such as source folders, examples, manifests, and agent entry files.

The result is portable agent memory: a bundle that preserves source context, explains what each page means, and gives agents a disciplined path through the knowledge.

Why this matters now

Agents Need Portable Context

Agents are more useful when they can reuse structured context across sessions, tools, people, and teams. Local notes become more valuable when the structure is predictable enough for another agent to traverse without first reverse-engineering the author's folder habits.

Reusable structure

Teams need shared conventions so knowledge survives handoff, onboarding, and repeated agent work.

Consistent traversal

Indexes, links, and metadata help agents decide where to begin and when to drill deeper.

Better provenance

Source-aware bundles make it easier to distinguish evidence from summary, interpretation, and local practice.

Problem

LLM Wikis Without Shared Shape

Before: local wiki dialects

Folder Atags, notes, loose links

Folder Bcategories, summaries, no index

Folder Ctopics, source dumps, unclear provenance

The agent must guess the entry point, field meaning, and relationship path.

After: shared bundle shape

IndexWhat exists and where to start.

MetadataType, title, tags, resource, timestamp.

LinksMarkdown relationships with source context.

The agent can traverse before consuming the whole bundle.

Source context and provenance

What This Artifact Is Grounded In

Source identity

Source title: Finally, an Open Standard for the Karpathy LLM Wiki is HERE
Creator/channel: Cole Medin
Canonical URL: https://www.youtube.com/watch?v=T33iI6izAKw
Recorded details: Publication date recorded as July 2, 2026; duration recorded as 19:37.

How this artifact was prepared

Caption source: YouTube automatic captions; useful source input, not final factual authority.
Acquisition method: Public metadata and captions were acquired with yt-dlp.
Extraction boundary: The source packet was created from public metadata and captions without relying on a separate Gemini extraction step.
Omission boundary: The source workflow did not replace missing material with a vague "not reproduced due to length" placeholder.

Verification posture

Publication wording: Publication wording was softened after verification to avoid overstating OKF v0.1 as a mature standard.
Spec posture: The page uses OKF v0.1 draft format phrasing and keeps explicit draft-spec caveats.
Raw material: Raw transcript text is not published here.

Verification anchors

Publication boundary

Not included: The public page does not include the source packet, transcript files, subtitles, media, screenshots, or normalization blueprint.
Verification anchor: e62021cb47abf294d9c9d80c8d128e7f9cac9d59be63e9bbc486c45e94acaa7c

Concept bridge

From Karpathy-Style Wiki To OKF-Style Bundle

Karpathy's April 4, 2026 llm-wiki.md gist describes an LLM-assisted, interlinked markdown knowledge base. Google Cloud introduced Open Knowledge Format v0.1 as an open specification for representing knowledge as markdown files with YAML frontmatter, with the OKF specification defining the draft details this artifact cites. The bridge between them is minimal shared structure: a wiki becomes more portable when humans and agents can predict its entry points and metadata.

Claim, Evidence, Provenance Separation

Source claimWhat the speaker or source material says.

Verified factWhat the receipt checked against public sources.

Teaching interpretationWhat this artifact explains as a reusable pattern.

Publication handlingSoftened, excluded, cited, or marked as caveated.

How the standard works

Verified OKF v0.1 Basics

Markdown plus YAML

OKF v0.1 represents concepts as UTF-8 markdown files with YAML frontmatter.

Required field

For OKF v0.1 concept documents, type is the only required frontmatter field.

Reserved optional files

index.md and log.md are optional reserved files, not required files for every bundle.

Links as edges

Markdown links can express directed relationship edges; surrounding prose carries the relationship meaning.

Teaching model

Manifest, entities, sources, examples, and agent entry points are local teaching patterns unless a specific bundle defines them.

Adoption posture

There is early public activity, but this artifact does not claim broad ecosystem adoption.

Deep dive

Bundle Anatomy

Open Knowledge Format bundle structure

typeWhat it is: the required OKF v0.1 frontmatter field for concept documents. Role: tells an agent what kind of page it is reading. Why it matters: traversal starts with classification, not guesswork.

index.mdWhat it is: an optional OKF reserved file. Role: entry map and progressive disclosure. Why it matters: agents can scan the bundle before reading every page.

log.mdWhat it is: an optional OKF reserved file. Role: update history. Why it matters: freshness and change context help prevent stale memory reuse.

okf.jsonWhat it is: a local manifest pattern in this teaching model, not asserted as required OKF v0.1. Role: bundle-level metadata. Why it matters: tools often need one place to inspect scope and policy.

entities/What it is: a local implementation pattern for people, tools, systems, or objects. Role: stable reference pages. Why it matters: agents can link concepts to concrete actors without duplicating facts.

sources/What it is: a local source-separation pattern. Role: keep source summaries and provenance apart from concept interpretation. Why it matters: claim state remains visible.

examples/What it is: a local implementation pattern. Role: applied cases and demonstrations. Why it matters: examples make abstract concepts operational without rewriting the source.

agent_indexWhat it is: a local implementation pattern, not an OKF v0.1 requirement. Role: agent-facing entry instructions. Why it matters: automation needs an explicit first read and stop condition.

knowledge-bundle/
  index.md                 # optional OKF reserved file
  log.md                   # optional OKF reserved file
  okf.json                 # local teaching pattern, not OKF v0.1 requirement
  concepts/
    portable-agent-memory.md
  entities/
    open-knowledge-format.md
  sources/
    source-video-summary.md
  examples/
    team-knowledge-handoff.md
  agent_index.md           # local teaching pattern, not OKF v0.1 requirement

Agent traversal model

How An Agent Uses The Bundle

1. QuestionUser asks without knowing the bundle structure.

2. IndexAgent reads the top-level map first.

3. ConceptsAgent resolves relevant concepts and entities.

4. GroundingAgent follows source links and answers with caveats.

This traversal loop is a teaching interpretation from the source demo and verification receipt. It should not be read as a guarantee that all agents will behave identically.

Visual explanation panels

Copyable Visual Prompts

These copyable visual prompts turn the teaching model into nine static infographic panels. Each panel includes a mainline white prompt and a dark expressive prompt, with copied text kept separate from webpage metadata labels.

01. Messy knowledge pile to portable bundle

Show the transformation from local notes into a structured agent memory bundle.

Render a 16:9 serious technical explainer in the SharePlane white-background system.
Intended visible title: "Messy Notes Become Portable Agent Memory".
Intended visible subtitle: "Minimal structure turns scattered knowledge into reusable context for humans and agents."
Intended visible section headers and labels: "1. Scattered notes", "2. LLM wiki", "3. Structured bundle", "4. Portable agent memory", "index", "type metadata", "relationships", "sources", "examples", "claim/evidence lanes", "verification badge", "governance boundary".
Visible callouts: "Scattered notes: useful locally but hard to traverse", "LLM wiki: pages gain names, links, and entry points", "Structured bundle: metadata makes files inspectable", "Sources: claims stay attached to evidence", "Relationships: concepts become navigable", "Portable agent memory: the next agent can enter without guessing".
Visible bottom-line banner: "Bottom line: structure turns a pile of notes into repeatable traversal."
Diagram objects: scattered markdown notes, wiki pages, source snippets, loose links, a sorting layer, clean bundle cards, metadata boxes, evidence lanes, red section numbers, and a red agent route line.
Layout and composition: left-to-right four-stage transformation; cluttered notes on the left, LLM wiki sorting layer next, organized bundle cards next, portable memory panel on the right; red arrows connect stages; light-gray explanation panels, black architecture boxes, gray grid dividers, and compact labels keep dense information readable.
Palette and style: white or near-white background, bold black title with red emphasis, red arrows, red control paths, red section numbers, red left-rule headers, black architecture boxes, light-gray explanation panels, gray grid system, high-trust engineering infographic feel, dense but readable.
Visible text constraints: Render only the specified reader-facing title, subtitle, section headers, labels, badges, callouts, and bottom-line banner. Do not render metadata labels such as "teaching slide", "visual prompt", "prompt", "prompt number", "capstone teaching infographic", "lifecycle diagram", "mainline white prompt", "dark expressive prompt", "aspect ratio", "purpose", "layout notes", or "alt text".
Do not render meta labels. Do not include fake logos, YouTube UI, robot mascots, stock photos, glossy 3D, cartoons, playful mascots, colorful decorative gradients, unverified adoption claims, mature standard wording, or any implication that local teaching folders are required OKF v0.1 elements.

Render a 16:9 dark premium technical explainer with a black/charcoal portal interface and controlled luminous depth.
Intended visible title: "Messy Notes Become Portable Agent Memory".
Intended visible subtitle: "A navigable bundle gives future readers and agents the same entry path."
Intended visible section headers and labels: "Scattered notes", "LLM wiki", "Structured bundle", "Portable agent memory", "index", "metadata", "sources", "concepts", "examples", "agent traversal", "verification badge", "governance boundary".
Visible callouts: "Fragments: context is present but hidden", "Wiki layer: related pages snap into place", "Metadata: each file says what it is", "Sources: evidence travels with the claim", "Traversal path: the agent follows visible routes", "Memory bundle: reusable without private context".
Visible bottom-line banner: "Bottom line: organization is what makes knowledge portable."
Diagram objects: floating note fragments, linked wiki cards, metadata chips, source cards, relationship paths, a glowing bundled memory stack, red traversal path, and compact explanatory callout panels.
Layout and composition: cinematic left-to-right transformation; left side is fragmented and dim, center is a sorting portal, right side is clean and stable; use glassy dark panels, subtle glow, graph lines, red control arrows, and readable white callouts without visual noise.
Palette and style: black and charcoal base, white/near-white text, strong red emphasis, gray glass panels, restrained luminous accents, rich depth, expressive graph lines, high-end AI/knowledge architecture feel, readable at presentation size.
Visible text constraints: Render only the specified reader-facing title, subtitle, section headers, labels, badges, callouts, and bottom-line banner. Do not render metadata labels such as "teaching slide", "visual prompt", "prompt", "prompt number", "capstone teaching infographic", "lifecycle diagram", "mainline white prompt", "dark expressive prompt", "aspect ratio", "purpose", "layout notes", or "alt text".
Do not render meta labels. Do not include fake logos, YouTube UI, robot mascots, overdecorated nonsense, unverified adoption claims, mature standard wording, or any implication that local teaching folders are required OKF v0.1 elements.

02. LLM wiki anatomy

Explain the interlinked markdown layer and its core page types.

Render a 16:9 serious technical architecture diagram in the SharePlane white-background system.
Intended visible title: "LLM Wiki Anatomy".
Intended visible subtitle: "An LLM wiki works when people and agents can find the same paths through it."
Intended visible section headers and labels: "Overview", "Topic pages", "Examples", "Glossary", "Links", "Citations", "index.md", "YAML frontmatter", "type metadata", "source pointer", "verified OKF v0.1 fact", "local teaching pattern".
Visible callouts: "Overview: where the reader enters", "Topic pages: durable explanations", "Examples: concrete reuse patterns", "Glossary: shared language", "Links: relationship paths", "Citations: evidence for trust", "Metadata: what each page is".
Visible bottom-line banner: "Bottom line: an LLM wiki is useful when humans and agents can find the same paths through it."
Diagram objects: central index page, markdown page cards, YAML frontmatter strips, overview card, topic page cards, example cards, glossary card, citation cards, relationship lines, metadata inspection panel, and verification badge.
Layout and composition: central hub-and-spoke map; `index.md` in the center, six labeled anatomy regions around it, red primary relationship lines, gray secondary links, right-side metadata panel, bottom-line banner across the base.
Palette and style: white or near-white background, bold black title with red emphasis, red relationship paths, red section numbers, red left-rule headers, black architecture boxes, light-gray explanation panels, gray grid lines, metadata boxes, sparse black/red line icons, dense but readable.
Visible text constraints: Render only the specified reader-facing title, subtitle, section headers, labels, badges, callouts, and bottom-line banner. Do not render metadata labels such as "teaching slide", "visual prompt", "prompt", "prompt number", "capstone teaching infographic", "lifecycle diagram", "mainline white prompt", "dark expressive prompt", "aspect ratio", "purpose", "layout notes", or "alt text".
Do not render meta labels. Do not include fake logos, YouTube UI, robot mascots, stock photos, glossy 3D, cartoons, colorful decorative gradients, unverified adoption claims, mature standard wording, or any implication that local teaching folders are required OKF v0.1 elements.

Render a 16:9 dark premium knowledge-architecture explainer with a black/charcoal portal interface.
Intended visible title: "LLM Wiki Anatomy".
Intended visible subtitle: "Shared page anatomy gives readers and agents a repeatable route."
Intended visible section headers and labels: "Overview", "Topic pages", "Examples", "Glossary", "Links", "Citations", "index.md", "YAML frontmatter", "type metadata", "source pointer", "verified fact", "local pattern".
Visible callouts: "Overview: starting map", "Topic pages: explain concepts", "Examples: show usage", "Glossary: align terms", "Links: connect related ideas", "Citations: keep evidence visible", "Metadata: supports inspection".
Visible bottom-line banner: "Bottom line: the wiki becomes useful when its routes are visible."
Diagram objects: glowing central index card, linked markdown cards, metadata strips, source cards, topic nodes, glossary node, citation rail, relationship paths, and a small verification badge.
Layout and composition: centered network map with six surrounding page regions; red active traversal links and gray secondary graph lines; callout chips orbit the relevant region; subtle glassy panels and controlled glow.
Palette and style: black and charcoal base, white/near-white text, strong red active paths, gray translucent panels, restrained luminous accents, rich depth, expressive modern visual system, readable labels.
Visible text constraints: Render only the specified reader-facing title, subtitle, section headers, labels, badges, callouts, and bottom-line banner. Do not render metadata labels such as "teaching slide", "visual prompt", "prompt", "prompt number", "capstone teaching infographic", "lifecycle diagram", "mainline white prompt", "dark expressive prompt", "aspect ratio", "purpose", "layout notes", or "alt text".
Do not render meta labels. Do not include fake logos, YouTube UI, robot mascots, neon cyberpunk clutter, unverified adoption claims, mature standard wording, or any implication that local teaching folders are required OKF v0.1 elements.

03. OKF v0.1 basics versus local pattern

Separate verified OKF facts from teaching conventions.

Render a 16:9 serious technical comparison panel in the SharePlane white-background system.
Intended visible title: "OKF v0.1 Basics vs Local Bundle Pattern".
Intended visible subtitle: "Keep verified specification facts separate from the teaching model built around them."
Intended visible section headers and labels: "Verified OKF v0.1 basics", "Local teaching pattern", "Why the distinction matters", "markdown files", "YAML frontmatter", "required field: type", "optional reserved files: index.md and log.md", "manifest", "entities", "sources", "examples", "agent index", "not an OKF requirement".
Visible callouts: "Verified: OKF uses markdown plus YAML frontmatter", "Required: concept documents include type", "Reserved: index.md and log.md are optional", "Local: manifest organizes this teaching bundle", "Local: entities/sources/examples support traversal", "Distinction: do not turn a local pattern into a spec claim".
Visible bottom-line banner: "Bottom line: spec facts and local teaching patterns must stay visually separate."
Diagram objects: three-zone comparison, spec document card, YAML frontmatter strip, `type` badge, optional reserved-file cards, local manifest card, local folder cards, verification badge, evidence footer, and red governance boundary.
Layout and composition: split-screen comparison with a red vertical divider; verified facts on the left, local pattern on the right, "why it matters" explanation band across the bottom; use red warning badge where local pattern is not OKF requirement.
Palette and style: white or near-white background, bold black title with red emphasis, red divider, red badges, red left-rule headers, black architecture boxes, light-gray explanation panels, gray evidence footer, metadata boxes, sparse black/red icons, compact engineering-review style.
Visible text constraints: Render only the specified reader-facing title, subtitle, section headers, labels, badges, callouts, and bottom-line banner. Do not render metadata labels such as "teaching slide", "visual prompt", "prompt", "prompt number", "capstone teaching infographic", "lifecycle diagram", "mainline white prompt", "dark expressive prompt", "aspect ratio", "purpose", "layout notes", or "alt text".
Do not render meta labels. Do not include fake logos, YouTube UI, robot mascots, stock photos, glossy 3D, cartoons, colorful decorative gradients, unverified adoption claims, mature standard wording, or any implication that local teaching folders are required OKF v0.1 elements.

Render a 16:9 dark premium technical comparison using a black/charcoal portal interface.
Intended visible title: "OKF v0.1 Basics vs Local Bundle Pattern".
Intended visible subtitle: "The useful bundle pattern is local; the verified facts remain narrower."
Intended visible section headers and labels: "Verified OKF v0.1 basics", "Local teaching pattern", "Why the distinction matters", "required field: type", "index.md", "log.md", "manifest", "entities", "sources", "examples", "agent index", "not an OKF requirement".
Visible callouts: "Verified fact: markdown with frontmatter", "Required field: type", "Optional reserved files: index.md and log.md", "Local pattern: manifest and folder lanes", "Caution: local folders are not mandatory OKF", "Trust move: label the boundary".
Visible bottom-line banner: "Bottom line: clear boundaries prevent overclaiming."
Diagram objects: two illuminated columns, spec-side cards, local-pattern cards, red boundary line, verification badge, caveat badge, evidence rail, and compact callout chips.
Layout and composition: left column glows subtly as verified surface, right column uses darker local-pattern cards; center red divider and bottom caution band make the boundary impossible to miss.
Palette and style: black/charcoal base, white/near-white text, red caution line, red badges, gray glass panels, controlled luminous accents, rich depth, professional source-discipline tone.
Visible text constraints: Render only the specified reader-facing title, subtitle, section headers, labels, badges, callouts, and bottom-line banner. Do not render metadata labels such as "teaching slide", "visual prompt", "prompt", "prompt number", "capstone teaching infographic", "lifecycle diagram", "mainline white prompt", "dark expressive prompt", "aspect ratio", "purpose", "layout notes", or "alt text".
Do not render meta labels. Do not include fake logos, YouTube UI, robot mascots, neon clutter, unverified adoption claims, mature standard wording, or any implication that local teaching folders are required OKF v0.1 elements.

04. Claim, evidence, provenance ledger

Visualize how the artifact separates claim states before publishing.

Render a 16:9 serious governance-grade infographic in the SharePlane white-background system.
Intended visible title: "Separate Claims, Evidence, and Interpretation".
Intended visible subtitle: "Publish only what the evidence supports, and label the rest as teaching or unresolved."
Intended visible section headers and labels: "Source claim", "Verified fact", "Teaching interpretation", "Speculation", "Publication handling", "confidence: high", "confidence: medium", "confidence: unresolved", "source URL", "verification receipt", "do not publish raw transcript", "governance boundary".
Visible callouts: "Source claim: what the source appears to say", "Verified fact: checked against an anchor", "Teaching interpretation: useful framing, not a spec fact", "Speculation: hold or exclude", "Confidence badge: show trust level", "Publication handling: publish, caveat, or suppress", "Warning: do not publish source claims as verified facts".
Visible bottom-line banner: "Bottom line: do not publish source claims as verified facts."
Diagram objects: four-lane claim ledger, publication-handling column, claim cards, evidence cards, source URL icon, receipt card, confidence badges, red caution markers, gray provenance rail, and governance boundary.
Layout and composition: horizontal ledger across the center; each lane has a short definition and confidence badge; publication-handling column sits at the right; provenance rail beneath it; red warning badges mark speculation and excluded items; gray row structure keeps categories distinct.
Palette and style: white or near-white background, bold black title with red emphasis, red warning badges, red section numbers, red left-rule headers, black ledger boxes, light-gray explanation panels, gray ledger lines, sparse black/red icons, no decorative excess.
Visible text constraints: Render only the specified reader-facing title, subtitle, section headers, labels, badges, callouts, and bottom-line banner. Do not render metadata labels such as "teaching slide", "visual prompt", "prompt", "prompt number", "capstone teaching infographic", "lifecycle diagram", "mainline white prompt", "dark expressive prompt", "aspect ratio", "purpose", "layout notes", or "alt text".
Do not render meta labels. Do not include fake logos, YouTube UI, robot mascots, stock photos, glossy 3D, cartoons, colorful decorative gradients, raw transcript text, private packet filenames, unverified adoption claims, or mature standard wording.

Render a 16:9 dark premium provenance-control interface with black/charcoal depth and controlled red warnings.
Intended visible title: "Separate Claims, Evidence, and Interpretation".
Intended visible subtitle: "Claim state determines whether content is published, caveated, or held back."
Intended visible section headers and labels: "Source claim", "Verified fact", "Teaching interpretation", "Speculation", "Publication handling", "confidence: high", "confidence: medium", "confidence: unresolved", "source URL", "verification receipt", "governance boundary".
Visible callouts: "Source claim: needs checking", "Verified fact: anchored to evidence", "Teaching interpretation: label as framing", "Speculation: do not promote", "Confidence badge: trust signal", "Handling: publish with caveat or suppress", "Warning: do not publish source claims as verified facts".
Visible bottom-line banner: "Bottom line: confidence and handling must travel with every claim."
Diagram objects: luminous four-lane claim ledger, handling rail, evidence chips, source pointer cards, receipt card, confidence badges, red warning markers, and gray glass panels.
Layout and composition: center the ledger as a command surface; place provenance rail below; use red accents to separate safe, caveated, unresolved, and excluded states; keep warning text large and legible.
Palette and style: black/charcoal background, near-white text, red status markers, red warning accents, gray translucent ledger panels, subtle glow, rich depth, high-end AI governance feel, readable labels.
Visible text constraints: Render only the specified reader-facing title, subtitle, section headers, labels, badges, callouts, and bottom-line banner. Do not render metadata labels such as "teaching slide", "visual prompt", "prompt", "prompt number", "capstone teaching infographic", "lifecycle diagram", "mainline white prompt", "dark expressive prompt", "aspect ratio", "purpose", "layout notes", or "alt text".
Do not render meta labels. Do not include fake logos, YouTube UI, robot mascots, raw transcript text, private packet filenames, overdecorated nonsense, unverified adoption claims, or mature standard wording.

05. Agent traversal path

Show how an agent enters, scans, follows links, and answers with caveats.

Render a 16:9 serious technical process graphic in the SharePlane white-background system.
Intended visible title: "How an Agent Traverses a Knowledge Bundle".
Intended visible subtitle: "Traversal is the reason structure matters."
Intended visible section headers and labels: "Enter index", "Read metadata", "Resolve concepts", "Follow relationships", "Ground output", "source", "claim", "confidence", "verification", "answer with caveats", "stop or request more evidence", "governance boundary".
Visible callouts: "Enter index: start from the map", "Read metadata: learn what each file is", "Resolve concepts: choose relevant pages", "Follow relationships: move through linked ideas", "Ground output: cite source and claim state", "Confidence: show how strong the evidence is", "Verification: stop when evidence is missing".
Visible bottom-line banner: "Bottom line: traversal is the reason structure matters."
Diagram objects: user question card, index card, metadata inspection card, concept page, relationship map, source pointer, evidence lane, trust checkpoint badges, caveated answer card, stop marker, verification badge, and red traversal route.
Layout and composition: left-to-right route line with five major stops; trust checkpoints form a bottom rail under the route; top band shows entry context, middle band shows traversal, bottom band shows source/claim/confidence/verification checks and stop conditions.
Palette and style: white or near-white background, bold black title with red emphasis, red route line, red arrows, red step numbers, red control paths, black architecture boxes, light-gray explanation panels, gray support rails, sparse black/red icons.
Visible text constraints: Render only the specified reader-facing title, subtitle, section headers, labels, badges, callouts, and bottom-line banner. Do not render metadata labels such as "teaching slide", "visual prompt", "prompt", "prompt number", "capstone teaching infographic", "lifecycle diagram", "mainline white prompt", "dark expressive prompt", "aspect ratio", "purpose", "layout notes", or "alt text".
Do not render meta labels. Do not include fake logos, YouTube UI, robot mascots, humanoid agents, stock photos, glossy 3D, cartoons, colorful decorative gradients, unverified adoption claims, mature standard wording, or unsupported automation claims.

Render a 16:9 dark premium agent traversal interface with black/charcoal depth and a red control path.
Intended visible title: "How an Agent Traverses a Knowledge Bundle".
Intended visible subtitle: "A structured bundle gives the agent visible checkpoints before it answers."
Intended visible section headers and labels: "Enter index", "Read metadata", "Resolve concepts", "Follow relationships", "Ground output", "source", "claim", "confidence", "verification", "answer with caveats", "stop or request more evidence".
Visible callouts: "Index: where traversal begins", "Metadata: what this file is", "Concepts: what matters to the question", "Relationships: why ideas connect", "Source: evidence behind the claim", "Confidence: how strongly to answer", "Verification: when to stop".
Visible bottom-line banner: "Bottom line: structure makes traversal repeatable."
Diagram objects: abstract cursor route, glowing index card, metadata panel, concept node, relationship graph, source pointer, trust checkpoint rail, evidence lane, caveated answer panel, stop marker, and governance boundary.
Layout and composition: cinematic route from left to right; red path passes through cards and nodes; lower rail shows source, claim, confidence, and verification; keep all labels large enough to read.
Palette and style: black/charcoal background, near-white text, red active path, red checkpoint markers, gray glass panels, subtle glow, graph lines, rich depth, expressive modern visual system.
Visible text constraints: Render only the specified reader-facing title, subtitle, section headers, labels, badges, callouts, and bottom-line banner. Do not render metadata labels such as "teaching slide", "visual prompt", "prompt", "prompt number", "capstone teaching infographic", "lifecycle diagram", "mainline white prompt", "dark expressive prompt", "aspect ratio", "purpose", "layout notes", or "alt text".
Do not render meta labels. Do not include fake logos, YouTube UI, robot mascots, humanoid agents, neon clutter, overdecorated nonsense, unverified adoption claims, mature standard wording, or unsupported automation claims.

06. Human, team, agent reuse loop

Explain how authoring, review, reuse, and updates reinforce portable memory.

Render a 16:9 serious systems graphic in the SharePlane white-background system.
Intended visible title: "Portable Memory Reuse Loop".
Intended visible subtitle: "Humans maintain the bundle; teams review it; agents reuse it with boundaries."
Intended visible section headers and labels: "Human author", "Team review", "Agent ingestion", "Reusable output", "Feedback update", "review gate", "version history", "source boundary", "provenance stays attached", "claim state", "update log", "governance boundary".
Visible callouts: "Human author: writes explainable pages", "Team review: checks claims before reuse", "Agent ingestion: reads structure, not private context", "Reusable output: cites boundaries and caveats", "Feedback update: improves the bundle", "Review gate: prevents full autonomy claims", "Version history: changes stay traceable".
Visible bottom-line banner: "Bottom line: reuse works when governance stays in the loop."
Diagram objects: five loop-stage cards, red directional arrows, central provenance card, audit rail, review gate badge, version history strip, source boundary marker, metadata chips, freshness note, claim-state marker, verification badge, and update log.
Layout and composition: circular five-stage loop in the center; left panel for human/team controls, right panel for agent reuse controls, bottom audit rail for provenance, source boundary, version history, and freshness; use compact bullets instead of paragraphs.
Palette and style: white or near-white background, bold black title with red emphasis, red loop arrows, red stage numbers, red review-gate badge, black architecture boxes, light-gray audit rail, gray support panels, sparse black/red icons, dense but readable.
Visible text constraints: Render only the specified reader-facing title, subtitle, section headers, labels, badges, callouts, and bottom-line banner. Do not render metadata labels such as "teaching slide", "visual prompt", "prompt", "prompt number", "capstone teaching infographic", "lifecycle diagram", "mainline white prompt", "dark expressive prompt", "aspect ratio", "purpose", "layout notes", or "alt text".
Do not render meta labels. Do not include fake logos, YouTube UI, robot mascots, stock photos, glossy 3D, cartoons, colorful decorative gradients, generic productivity marketing copy, unverified adoption claims, or mature standard wording.

Render a 16:9 dark premium systems interface showing a maintained knowledge loop.
Intended visible title: "Portable Memory Reuse Loop".
Intended visible subtitle: "The agent can reuse the bundle, but review and source boundaries remain visible."
Intended visible section headers and labels: "Human author", "Team review", "Agent ingestion", "Reusable output", "Feedback update", "review gate", "version history", "source boundary", "provenance stays attached", "claim state", "update log".
Visible callouts: "Author: creates structured pages", "Review gate: checks before reuse", "Ingestion: structure guides the agent", "Output: cite and caveat", "Feedback: update the bundle", "Version history: trace changes", "Source boundary: no private context leakage".
Visible bottom-line banner: "Bottom line: governed reuse is a loop, not full autonomy."
Diagram objects: luminous circular loop, red directional arrows, glassy stage cards, central provenance core, audit rail, review gate, version-history strip, source-boundary marker, verification badge, and governance boundary.
Layout and composition: centered orbital loop with rich depth; side panels show review and reuse controls; lower rail shows freshness, version history, source boundary, and claim-state maintenance.
Palette and style: black/charcoal base, near-white text, red loop arrows, red governance markers, gray glass cards, subtle glow, graph lines, cinematic technical composition, professional and readable.
Visible text constraints: Render only the specified reader-facing title, subtitle, section headers, labels, badges, callouts, and bottom-line banner. Do not render metadata labels such as "teaching slide", "visual prompt", "prompt", "prompt number", "capstone teaching infographic", "lifecycle diagram", "mainline white prompt", "dark expressive prompt", "aspect ratio", "purpose", "layout notes", or "alt text".
Do not render meta labels. Do not include fake logos, YouTube UI, robot mascots, generic productivity marketing copy, overdecorated nonsense, unverified adoption claims, or mature standard wording.

07. Before and after shared shape

Contrast local folder dialects with predictable bundle structure.

Render a 16:9 serious technical before/after comparison in the SharePlane white-background system.
Intended visible title: "Before and After Shared Structure".
Intended visible subtitle: "Shared shape reduces friction by replacing guessing with traversal."
Intended visible section headers and labels: "Before: random folders", "missing metadata", "weak reuse", "fragile context", "After: predictable entry point", "typed metadata", "relationships", "reusable agent memory", "index", "source-aware traversal", "verification badge", "governance boundary".
Visible callouts: "Random folders: humans remember context manually", "Missing metadata: agents cannot inspect intent", "Weak reuse: each project invents a dialect", "Fragile context: links and claims drift", "Predictable entry point: start at the index", "Typed metadata: files announce their role", "Relationships: traversal replaces guessing", "Reusable memory: context survives handoff".
Visible bottom-line banner: "Bottom line: shared shape reduces friction."
Diagram objects: messy local folders, inconsistent labels, broken path lines, clean bundle stack, index card, metadata box, relationship links, evidence lane, reusable memory card, red divider, and red traversal path.
Layout and composition: strong split-screen comparison with thick red vertical divider; left side cluttered and gray with warning labels, right side clean and structured with numbered red path; bottom strip contrasts "guessing" with "traversal".
Palette and style: white or near-white background, bold black title with red emphasis, red divider, red after-path arrows, red warning badges, black architecture boxes, light-gray explanation panels, gray before-side clutter, gray support panels, metadata boxes, sparse black/red line icons.
Visible text constraints: Render only the specified reader-facing title, subtitle, section headers, labels, badges, callouts, and bottom-line banner. Do not render metadata labels such as "teaching slide", "visual prompt", "prompt", "prompt number", "capstone teaching infographic", "lifecycle diagram", "mainline white prompt", "dark expressive prompt", "aspect ratio", "purpose", "layout notes", or "alt text".
Do not render meta labels. Do not include fake logos, YouTube UI, robot mascots, stock photos, glossy 3D, cartoons, colorful decorative gradients, unverified adoption claims, mature standard wording, or any implication that local teaching folders are required OKF v0.1 elements.

Render a 16:9 dark premium before/after technical composition with black/charcoal depth.
Intended visible title: "Before and After Shared Structure".
Intended visible subtitle: "A shared shape turns fragile context into navigable memory."
Intended visible section headers and labels: "Before: random folders", "missing metadata", "weak reuse", "fragile context", "After: predictable entry point", "typed metadata", "relationships", "reusable agent memory", "index", "source-aware traversal", "governance boundary".
Visible callouts: "No entry point: the next reader guesses", "Missing metadata: role is unclear", "Weak reuse: context stays local", "Predictable entry: index first", "Typed metadata: files become inspectable", "Relationships: paths become visible", "Reusable memory: handoff becomes easier".
Visible bottom-line banner: "Bottom line: shared structure makes memory portable."
Diagram objects: dim cluttered folder cluster on the left, clean luminous bundle on the right, red divider, red traversal path, metadata chips, relationship graph, reusable memory card, and verification badge.
Layout and composition: left side feels fragmented, right side feels stable and navigable; red divider and route line show the change from guessing to traversal; callouts sit close to the objects they explain.
Palette and style: black/charcoal base, near-white text, red active path, red divider, gray glass panels, subtle glow, rich depth, expressive modern knowledge-architecture feel.
Visible text constraints: Render only the specified reader-facing title, subtitle, section headers, labels, badges, callouts, and bottom-line banner. Do not render metadata labels such as "teaching slide", "visual prompt", "prompt", "prompt number", "capstone teaching infographic", "lifecycle diagram", "mainline white prompt", "dark expressive prompt", "aspect ratio", "purpose", "layout notes", or "alt text".
Do not render meta labels. Do not include fake logos, YouTube UI, robot mascots, overdecorated nonsense, unverified adoption claims, mature standard wording, or any implication that local teaching folders are required OKF v0.1 elements.

08. Metadata card example

Turn the YAML frontmatter example into a readable visual teaching card.

Render a 16:9 serious technical metadata and folder-tree explainer in the SharePlane white-background system.
Intended visible title: "Metadata Makes Memory Navigable".
Intended visible subtitle: "A folder tree gives shape; frontmatter tells readers and agents what each file means."
Intended visible section headers and labels: "Folder tree", "YAML frontmatter", "verified OKF", "local pattern", "required vs optional", "type", "title", "tags", "resource", "index.md", "log.md", "manifest", "entities", "sources", "examples", "agent index".
Visible callouts: "verified OKF: markdown files with YAML frontmatter", "required: type on OKF v0.1 concept documents", "optional: index.md and log.md reserved files", "local pattern: manifest, entities, sources, examples", "agent index: teaching model for traversal", "resource: pointer, not a private transcript", "Do not imply local folders are mandatory OKF v0.1".
Visible bottom-line banner: "Bottom line: metadata makes files inspectable; labels keep requirements honest."
Diagram objects: visible folder tree card, large markdown card, YAML/frontmatter card, red callout lines, metadata explanation boxes, required badge, optional badge, local-pattern badge, index reference, relationship link, source pointer, verification badge, and governance boundary.
Layout and composition: left column shows folder tree, center shows YAML/frontmatter card, right governance panel separates verified OKF from local pattern; red callouts point to `type`, `index.md`, `log.md`, manifest, entities, sources, examples, and agent index; bottom strip connects metadata to traversal.
Palette and style: white or near-white background, bold black title with red emphasis, red field highlights, red callout lines, red section headers, black architecture boxes, light-gray code cards, gray support panels, monospace code, sparse black/red icons.
Visible code in the markdown card: "---", "type: concept", "title: Portable agent memory", "tags: [okf, llm-wiki]", "resource: https://example.invalid/local-note", "---".
Visible text constraints: Render only the specified reader-facing title, subtitle, section headers, labels, badges, callouts, code lines, and bottom-line banner. Do not render metadata labels such as "teaching slide", "visual prompt", "prompt", "prompt number", "capstone teaching infographic", "lifecycle diagram", "mainline white prompt", "dark expressive prompt", "aspect ratio", "purpose", "layout notes", or "alt text".
Do not render meta labels. Do not include fake logos, YouTube UI, robot mascots, stock photos, glossy 3D, cartoons, colorful decorative gradients, unverified adoption claims, mature standard wording, or any implication that local teaching folders are required OKF v0.1 elements.

Render a 16:9 dark premium metadata and folder-tree interface with a black/charcoal portal aesthetic.
Intended visible title: "Metadata Makes Memory Navigable".
Intended visible subtitle: "Structure shows where to look; metadata explains what can be trusted."
Intended visible section headers and labels: "Folder tree", "YAML frontmatter", "verified OKF", "local pattern", "required vs optional", "type", "title", "tags", "resource", "index.md", "log.md", "manifest", "entities", "sources", "examples", "agent index".
Visible callouts: "verified OKF: markdown plus frontmatter", "required: type field", "optional: index.md and log.md", "local pattern: manifest and folder lanes", "agent index: traversal helper", "resource: source pointer", "Caution: local folders are teaching model".
Visible bottom-line banner: "Bottom line: requirements and teaching conventions must be labeled separately."
Diagram objects: glowing folder tree card, central markdown card, YAML frontmatter, red field highlights, callout beams, metadata chips, required/optional/local badges, source pointer, verification badge, and governance boundary.
Layout and composition: left glass panel shows folder tree, center code card shows YAML/frontmatter, right governance panel labels verified OKF versus local pattern; red beams connect labels to the exact fields and folders; bottom route line leads toward traversal.
Palette and style: black/charcoal background, near-white text, red field highlights, red caution badge, gray glass panels, subtle glow, monospace code, rich depth, precise technical feel.
Visible code in the markdown card: "---", "type: concept", "title: Portable agent memory", "tags: [okf, llm-wiki]", "resource: https://example.invalid/local-note", "---".
Visible text constraints: Render only the specified reader-facing title, subtitle, section headers, labels, badges, callouts, code lines, and bottom-line banner. Do not render metadata labels such as "teaching slide", "visual prompt", "prompt", "prompt number", "capstone teaching infographic", "lifecycle diagram", "mainline white prompt", "dark expressive prompt", "aspect ratio", "purpose", "layout notes", or "alt text".
Do not render meta labels. Do not include fake logos, YouTube UI, robot mascots, neon clutter, overdecorated nonsense, unverified adoption claims, mature standard wording, or any implication that local teaching folders are required OKF v0.1 elements.

09. Capstone map: portable agent memory system

Combine the full teaching model into one high-density summary panel.

Render a 16:9 serious all-in-one technical explainer in the SharePlane white-background system.
Intended visible title: "Open Knowledge Format and the LLM Wiki".
Intended visible subtitle: "From personal notes to portable agent memory, with evidence and governance attached."
Intended visible section headers and labels: "Problem", "Verified OKF basics", "Local bundle pattern", "Agent traversal", "Claim separation", "Governance/provenance", "Builder takeaway", "index", "type metadata", "relationships", "sources", "examples", "source claim", "verified fact", "teaching interpretation", "speculation", "answer with caveats", "freshness note", "update log".
Visible callouts: "Problem: scattered notes are hard to reuse", "Verified OKF basics: markdown plus YAML frontmatter", "Local bundle pattern: manifest, entities, sources, examples", "Agent traversal: enter index, read metadata, follow relationships", "Claim separation: source claim is not automatically verified fact", "Governance: provenance and freshness stay attached", "Builder takeaway: structure makes context portable", "Caution: do not publish raw transcript or private packet paths".
Visible bottom-line banner: "Bottom line: portable memory depends on shared structure, visible evidence, and honest claim labels."
Diagram objects: seven-section governance-grade map, source card, verification receipt, index card, metadata boxes, concept files, entity/source/example cards, folder-tree mini panel, red traversal route, claim/evidence lanes, confidence badges, freshness note, update log, builder takeaway card, and governance boundary.
Layout and composition: dense seven-section summary with a clear top-to-bottom and left-to-right reading order; top band states the problem and verified OKF basics, middle bands show local bundle pattern and agent traversal, lower bands show claim separation and governance/provenance, final bottom banner states builder takeaway; red numbered section headers and gray dividers.
Palette and style: white or near-white background, bold black title with red emphasis, red arrows, red section numbers, red rules, red warning badges, black architecture boxes, light-gray explanation panels, gray grid lines, support panels, metadata boxes, sparse black/red icons, governance-grade technical poster.
Visible text constraints: Render only the specified reader-facing title, subtitle, section headers, labels, badges, callouts, and bottom-line banner. Do not render metadata labels such as "teaching slide", "visual prompt", "prompt", "prompt number", "capstone teaching infographic", "lifecycle diagram", "mainline white prompt", "dark expressive prompt", "aspect ratio", "purpose", "layout notes", or "alt text".
Do not render meta labels. Do not include fake logos, YouTube UI, robot mascots, stock photos, glossy 3D, cartoons, colorful decorative gradients, raw transcript text, private source packet paths, unverified adoption claims, mature standard wording, or any implication that local teaching folders are required OKF v0.1 elements.

Render a 16:9 dark premium all-in-one knowledge architecture map with black/charcoal depth and controlled luminous accents.
Intended visible title: "Open Knowledge Format and the LLM Wiki".
Intended visible subtitle: "A complete map from scattered notes to governed, reusable agent memory."
Intended visible section headers and labels: "Problem", "Verified OKF basics", "Local bundle pattern", "Agent traversal", "Claim separation", "Governance/provenance", "Builder takeaway", "index", "metadata", "relationships", "sources", "examples", "source claim", "verified fact", "teaching interpretation", "speculation", "answer with caveats", "freshness note", "update log".
Visible callouts: "Problem: scattered context is not portable", "Verified OKF basics: markdown plus frontmatter", "Local pattern: manifest and folder lanes", "Traversal: index -> metadata -> relationships -> grounded output", "Claim separation: confidence controls publication", "Governance: provenance, freshness, update log", "Takeaway: build for repeatable entry and evidence", "Caution: no raw transcript or private paths".
Visible bottom-line banner: "Bottom line: structure plus provenance makes memory reusable without overclaiming."
Diagram objects: cinematic seven-section portal map, source card, receipt card, bundle anatomy cluster, folder-tree mini panel, red traversal path, evidence lanes, confidence badges, governance boundary, freshness marker, update log, and builder takeaway card.
Layout and composition: high-end technical composition with clear top-to-bottom reading order; red path connects problem, verified basics, local bundle structure, agent answer, claim separation, and maintenance; glass panels and graph lines add depth without reducing readability; make the capstone the densest and most complete single-image summary.
Palette and style: black/charcoal background, white/near-white text, red control paths and warning badges, gray glass panels, subtle glow, rich depth, expressive modern AI/knowledge architecture feel, premium but readable.
Visible text constraints: Render only the specified reader-facing title, subtitle, section headers, labels, badges, callouts, and bottom-line banner. Do not render metadata labels such as "teaching slide", "visual prompt", "prompt", "prompt number", "capstone teaching infographic", "lifecycle diagram", "mainline white prompt", "dark expressive prompt", "aspect ratio", "purpose", "layout notes", or "alt text".
Do not render meta labels. Do not include fake logos, YouTube UI, robot mascots, raw transcript text, private source packet paths, overdecorated nonsense, unverified adoption claims, mature standard wording, or any implication that local teaching folders are required OKF v0.1 elements.

Builder playbook

Practical Patterns

Personal second brain

Add indexes and consistent metadata so your own agent can navigate your notes later.

Team knowledge base

Define shared bundle conventions for decisions, recurring concepts, and project memory.

Agent context pack

Package working context as a small traversable bundle instead of one giant prompt dump.

Creator knowledge product

Publish organized concepts and source references without redistributing raw transcripts or media.

Enterprise handoff

Add ownership, freshness, data classification, and validation posture before operational reuse.

Verification discipline

Keep source claims, verified facts, local interpretations, and omitted claims visibly separated before reuse.

Claim and evidence ledger

How Claims Are Handled

Claim	Classification	Confidence	Verification status	Evidence	Publication handling
Google Cloud introduced OKF v0.1 as an open specification.	Verified fact	High	Partially verified with official sources	Google Cloud OKF blog; OKF spec	Publish with softened wording.
OKF concept documents require `type`.	Verified fact	High	Verified against OKF v0.1 spec	OKF v0.1 spec	Publish as v0.1-specific fact.
Entities, sources, examples, and agent indexes are required OKF folders.	Excluded/softened claim	High	Not verified	OKF spec does not establish this as a required folder set.	Mark as local teaching pattern only.
LLM wikis benefit from shared traversal structure.	Teaching interpretation	High	Source-derived interpretation	Karpathy LLM Wiki gist; source video	Publish as teaching model.
OKF has settled ecosystem dominance or universal agent memory authority.	Speculation	Low	Not verified	No checked source establishes settled adoption or universal authority.	Do not publish as fact.

Risks and limits

What This Does Not Prove

Auto-caption limitations

Captions can mishear names, fields, and demos; this artifact does not reproduce raw transcript text.

Draft-spec status

OKF v0.1 is treated as a draft open format, not a mature standards-body standard.

Adoption uncertainty

Early public activity exists, but broad ecosystem adoption is not established here.

Over-structuring risk

A bundle can become busywork if the format grows beyond actual retrieval and maintenance needs.

Tooling fragmentation

Markdown and YAML are portable, but operational compatibility still depends on tools and workflows.

Governance needs

Agents can over-trust stale or inferred content unless bundles carry freshness, source, and review signals.

Implementation pattern

A Conservative Starting Model

Start with the verified OKF v0.1 basics, then clearly label any additional structure as local implementation. The model below is not an OKF requirement; it is a cautious pattern for humans and agents that need provenance-aware traversal.

Agent-readable view

Index, type metadata, concept pages, relationship links, source pointers, and freshness notes.

Human-readable view

Overview, caveats, examples, claim ledger, source list, and update history.

Claim-state view

Every important assertion should carry a visible state: source claim, verified fact, teaching interpretation, speculation, or excluded claim.

Bundle maintenance view

Use freshness notes, ownership, and update logs so the bundle remains trustworthy after the first authoring pass.

---
type: concept
title: Portable agent memory
tags: [okf, llm-wiki]
resource: https://example.invalid/local-note
---

# Portable agent memory

A compact concept page that explains what this idea means, how it relates to the bundle,
and which source pointers or examples should be inspected before reuse.

Closing takeaway

Minimal Shared Structure Makes Knowledge Portable

The value is not the folder format alone. The value is predictable traversal by humans and agents: know what exists, know where to start, know how concepts connect, and know which claims are grounded.