About this bundle

Generated from the authored source at docs/llm-wiki/README.md — the wiki owns these facts (ADR: D1 of docs/plans/20260811_documentation_system_execution.md). Edit that file, then regenerate: python docs/portfolio/_build/generate_wiki_pages.py.

Distilled, agent-facing knowledge about KAP. Each concept document is a set of stable facts about one domain — short bullets with concrete repo paths — designed to be read by an AI agent (or chunked into a retrieval index) in seconds, then followed into the authoritative sources for depth.

This directory is an Open Knowledge Format (OKF) v0.2 bundle: markdown concept documents with YAML frontmatter, a reserved index.md directory listing (which carries the bundle’s okf_version), and a reserved log.md update history.

This wiki owns the facts; the handbooks explain them. A concept is the one place a checkable claim about KAP is written down — a path, a count, a name, a rule. The handbook chapters under docs/handbooks/content/ narrate around those facts and link here rather than restating them, because a number typed into prose is the thing that goes stale.

That is an inversion, decided 2026-08-11 (D1 of docs/plans/20260811_documentation_system_execution.md). This bundle used to distill the handbooks, which made the material agents read a hand-written summary of material written for people — derived, lossy, and one edit behind. The arrow now runs the other way.

Each concept still declares provenance in its sources: frontmatter (OKF — each entry’s resource is a path relative to this bundle; its title is the repo-root path). Those entries now point at what produces the fact — code, specs, generated artifacts — rather than at a prose page that was itself hand-written.

Humans read this too. docs/portfolio/_build/generate_wiki_pages.py renders the bundle into the handbooks site at /knowledge/, and lint_consistency.py check_wiki_pages() fails CI if a rendered page is edited by hand. Edit the concept; never the rendering.

Maintenance contract

  • Every concept carries type (required by OKF), title, description, tags, sources, and the trust fields generated / verified (by/at, actor convention per the OKF spec).
  • When a source changes, update the concept in the same change and append a new verified entry ({ by, at }). Facts verified only by agents are machine-confirmed; a human reviewer should use human:<id> as the actor.
  • Keep concepts short and factual — paths, counts, names, rules. Explanations, tutorials, and narrative belong in the handbooks.
  • A fact lives in exactly one place. When a handbook chapter states one this bundle should own, move it here and leave a link behind. Not a sweep: do it on the next touch of that chapter.
  • New domain → new concept document + a bullet in index.md + a log.md entry. Adding a concept also means adding it to the “Knowledge” category in docs/handbooks/sidebars.js and to CHAPTERS in docs/handbooks/build-pdf.py; both fail quietly.