{"explanation/context-layer":{"title":"The curated context layer: one bundle, and a federation of bundles","type":"Explanation","genre":"explanation","label":"checked by automation only, still a draft","tone":"automation","definition":"What a context layer is, and why one KTL bundle is already one repository's context layer and where it stops. How bundles federate into one: domains as thin LOKF bundles that select releases, tiers of domains and the diamond rule, a workspace with one named graph per bundle served over SPARQL and MCP, and the products it can use."},"explanation/domain-schemas":{"title":"When the built-in vocabulary stops fitting: domain schemas","type":"Explanation","genre":"explanation","label":"edited since a person last confirmed it (confirmed 2026-10-13, edited 2026-10-29), reopened 2026-10-29 by noelmcloughlin: 1 question waits","tone":"edited","definition":"How a bundle in a specialised or regulated domain goes beyond LOKF's core classes: the signs a domain schema is due, a LinkML schema importing LOKF's, named by one `schema` variable in the sidecar's justfile and checked with `lokf validate --schema`, the three layouts that variable allows, the `domain.yaml` the sidecar ships for a bundle that federates other bundles, reusing a domain's own vocabulary such as the AI Risk Ontology through `lokf adapt`, the Microsoft 365 identity shape held in reserve, and who raises, decides and applies it."},"explanation/hosts-and-doorways":{"title":"Hosts and doorways: where the bundle's real folder lives","type":"Explanation","genre":"explanation","label":"edited since a person last confirmed it (confirmed 2026-10-13, edited 2026-10-26), reopened","tone":"edited","definition":"Why the bundle is `.lokf/knowledge`, one real folder on every host, with `knowledge_bundle` beside it as a link for people and folder pickers; what each host can do, from GitLab, Codeberg, Forgejo and Gitea to Microsoft 365 Copilot; what the visible layout tried and why it was retired; what a shared folder that is not a vault may still do by hand; and how one vault can link many hosts' bundles."},"explanation/intended-uses":{"title":"What Knowledge Trust Ladder is for, and what it is not","type":"Explanation","genre":"explanation","label":"checked by automation only, still a draft","tone":"automation","definition":"A draft placeholder for a reader's question no source settles: which uses Knowledge Trust Ladder is meant for, such as DevSecOps or technology governance, and which it is not. The README, `docs/architecture.md` and `docs/context-layer.md` state the purpose and name no use case or non-goal, and `docs/skills-repositories.md` answers it only for a repository whose content is Agent Skills."},"explanation/skills-repositories":{"title":"Knowledge Trust Ladder in a skills repository","type":"Explanation","genre":"explanation","label":"edited since a person last confirmed it (confirmed 2026-10-13, edited 2026-10-29), reopened","tone":"edited","definition":"Whether to install Knowledge Trust Ladder (KTL) in a repository whose content is Agent Skills, as `docs/skills-repositories.md` answers: what it adds (the knowledge around the skills), what it leaves to evaluations (whether a skill works), what it costs when skills change weekly, this repository's six skills and a run on anthropics/skills, how the librarian maps skills, and what remains to do."},"explanation/skillwiki":{"title":"What KTL took from SkillWiki","type":"Explanation","genre":"explanation","label":"edited since a person last confirmed it (confirmed 2026-10-19, edited 2026-10-29), reopened","tone":"edited","definition":"What Knowledge Trust Ladder (KTL) took from the SkillWiki paper (Huang et al., 2026) and its code: the four changes the reading made to the skills, the excerpt check that arrived with LOKF 0.9.0, and where the two designs part, such as who stands behind a decision."},"explanation/three-lines-of-defence":{"title":"Three lines of defence - where each role sits, and what an auditor can check","type":"Explanation","genre":"explanation","label":"edited since a person last confirmed it (confirmed 2026-10-19, edited 2026-10-29)","tone":"edited","definition":"The librarian, curator, registrar, sidecar and docent placed in the IIA's Three Lines Model, for whoever adopts KTL: who owns a claim, what a machine checks, what a person can examine afterwards, the four limits on that evidence, the model's critics with KTL's answer to each, and what remains to do and who does it."},"explanation/why-a-distribution-repository":{"title":"Why the skills live in their own repository","type":"Explanation","genre":"explanation","label":"checked by automation only, still a draft","tone":"automation","definition":"Why the six skills are published from one installable repository: three install routes plus Microsoft 365 Copilot for the docent, one tag for all of them, one changelog, a bundle of its own that the docent answers from, and the repository's rename."},"explanation/why-a-registrar-role":{"title":"Why a registrar role, and why it is not a skill","type":"Explanation","genre":"explanation","label":"edited since a person last confirmed it (confirmed 2026-10-13, edited 2026-10-19), reopened","tone":"edited","definition":"What the registrar, the fifth role and not a skill, does: it keeps every bundle record in order and ties every confirmation to a person, through the `lokf` toolkit, CI's `knowledge-registrar.yaml`, the pen `knowledge-apply.sh` and `knowledge-report.sh`, while the KTL Registrar plugin does that work in Obsidian, where there is no CI."},"explanation/why-four-roles":{"title":"Why four skill roles rather than one skill","type":"Explanation","genre":"explanation","label":"edited since a person last confirmed it (confirmed 2026-10-19, edited 2026-10-25)","tone":"edited","definition":"Why the work is split into four skills, sidecar, librarian, curator and docent, named for the library and museum professions and run first in order and then as a loop, beside a fifth role that is not a skill (the registrar) and two optional skills beside the roles (ktl-prose, and ktl-website, which publishes the bundle)."},"explanation/wikiskill":{"title":"What KTL took from WikiSkill","type":"Explanation","genre":"explanation","label":"checked by automation only, still a draft","tone":"automation","definition":"What Knowledge Trust Ladder (KTL) took from the WikiSkill paper (Tang et al., 2026), and what the paper leaves open. Both run one loop of maintainer, pen, consumer and gate, and the reading made seven changes to the skills, such as a consumer that writes nothing, a bounded run and a retrieval score."},"glossary/accession":{"title":"Accession","type":"Glossary term","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"A museum's word for an item added to its collection. The registrar keeps each accession documented and its provenance filed."},"glossary/collection":{"title":"Collection","type":"Glossary term","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"A repository's scattered knowledge kept, in museum terms, catalogued, authenticated and explained, with the trust in every claim left visible."},"glossary/context-layer":{"title":"Context layer","type":"Glossary term","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"A governed layer between an organisation's sources (code, documents, diagrams, policies, operational records) and whoever consumes them, a person or an agent, that persists from one task to the next."},"glossary/curator":{"title":"Curator","type":"Glossary term","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"The role, always played by a person, that records a verdict on a concept against its source: confirm, correct, retire or send back. Curator is the museum sense, the one who authenticates, weighs provenance and decides what goes on exhibit, not the data-management sense, which is the librarian's job."},"glossary/desk":{"title":"Desk","type":"Glossary term","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"In the project's library and museum terms, the place where a role does its work with the bundle. A program does the registrar's work at each desk."},"glossary/docent":{"title":"Docent","type":"Glossary term","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"A museum's name for a guide, who explains the exhibition to visitors without moving anything on the shelves. In Knowledge Trust Ladder it names the role that answers questions from the bundle and labels how far each concept has been trusted, which the ktl-docent skill plays."},"glossary/domain-schema":{"title":"Domain schema","type":"Glossary term","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"A schema written in LinkML that extends LOKF's, for a domain whose concepts stop fitting LOKF's classes."},"glossary/doorway":{"title":"Doorway","type":"Glossary term","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"The `knowledge_bundle` link at a host's root onto the bundle, which ktl-sidecar creates so the bundle has a name a folder picker can see."},"glossary/exhibition":{"title":"Exhibition","type":"Glossary term","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"The bundle as a vault of its own: the checked part of what the workshop knows, and the part that teammates, CI and agents read."},"glossary/health-line":{"title":"Health line","type":"Glossary term","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"The line `knowledge-report.sh` computes for the whole bundle, counting its concepts under eight trust labels. \"Confirmed by a person, a of N\" rising is the bundle earning trust."},"glossary/knowledge-bundle":{"title":"Knowledge bundle","type":"Glossary term","genre":"reference","label":"edited since a person last confirmed it (confirmed 2026-10-18, edited 2026-10-19), reopened","tone":"edited","definition":"The `.lokf/knowledge` folder: one Markdown file per concept, each with YAML frontmatter, which a person reads as documentation and a tool queries as a knowledge graph. A `knowledge_bundle` link beside `.lokf/` shows the same folder under a visible name."},"glossary/librarian":{"title":"Librarian","type":"Glossary term","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"The role that derives the bundle's concepts from the repository with their sources, classifies them, links them with typed relationships, audits, and hands off for review. It records facts about the repository, never verdicts about truth."},"glossary/linkml":{"title":"LinkML","type":"Glossary term","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"The schema language LOKF is written in, created by the LinkML Community. LOKF's specification is a single LinkML schema, `lokf.yaml`."},"glossary/lokf":{"title":"LOKF","type":"Glossary term","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"Linked Open Knowledge Format - a semantic profile of OKF in which every field, type, and relationship is bound to a public vocabulary, so the same Markdown expands losslessly to JSON-LD and RDF."},"glossary/okf":{"title":"OKF","type":"Glossary term","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"Open Knowledge Format - Google's specification for a folder of Markdown concept files with YAML frontmatter, where the file path is the concept ID and `type` is the only strictly required field."},"glossary/registrar":{"title":"Registrar","type":"Glossary term","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"In a museum, the person who keeps the collection's records. In Knowledge Trust Ladder, the role that keeps the bundle's records in order and ties each confirmation to the person who gave it, which no person has to play."},"glossary/sidecar":{"title":"Sidecar","type":"Glossary term","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"The `.lokf/` folder beside a project's code, like `.git/`, which holds the bundle and the tooling that validates it and is kept out of the project's build. The ktl-sidecar skill, the first role to run, installs it from bundled templates."},"glossary/the-pen":{"title":"The pen","type":"Glossary term","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"The name the docs give `knowledge-apply.sh`, the script through which ktl-librarian writes every change to the bundle. The librarian describes each change as an operation in `.lokf/patch.yaml`, and the pen checks every operation and writes the files, or writes nothing."},"glossary/three-lines-of-defence":{"title":"Three lines of defence","type":"Glossary term","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"The model regulated industries use to say who owns a risk, who keeps the rules, and who checks independently."},"glossary/trust-label":{"title":"Trust label","type":"Glossary term","genre":"reference","label":"edited since a person last confirmed it (confirmed 2026-10-19, edited 2026-10-29)","tone":"edited","definition":"The plain-language phrase a skill uses for how far a concept has been checked - \"confirmed by a person\", \"checked by automation only\", \"nobody has checked this yet\" - derived from frontmatter, never stored."},"glossary/trust-ladder":{"title":"Trust ladder","type":"Glossary term","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"The answer, written into each entry of the bundle, to who is responsible for the quality of the context. It says where the entry came from and how far it has been checked, in plain words."},"glossary/work-list":{"title":"Work list","type":"Glossary term","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"The list `knowledge-report.sh worklist` computes from frontmatter and git, which ktl-librarian starts every refresh from."},"glossary/workshop":{"title":"Workshop","type":"Glossary term","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"The vault a person already has, in which nothing is moved or migrated, beside the bundle opened as the exhibition."},"playbooks/contributing":{"title":"Contributing","type":"Playbook","genre":"how-to","label":"checked by automation only, still a draft","tone":"automation","definition":"How to work on the skills: no build step but the website's, the local checks to run before opening a pull request, the role boundary a change must respect, and which pages now hold the release and signing detail."},"playbooks/docent-in-m365-copilot":{"title":"The docent in Microsoft 365 Copilot","type":"Playbook","genre":"how-to","label":"checked by automation only, still a draft","tone":"automation","definition":"How a person gets ktl-docent-m365, the docent packed with a snapshot of the bundle as a Microsoft 365 Copilot custom skill, from a release or by building it, adds it to a declarative agent, checks the first answer and keeps it current, what to do when a step fails, and why only the read-only roles go there."},"playbooks/domain-bundle":{"title":"Curating a domain bundle","type":"Playbook","genre":"how-to","label":"checked by automation only, still a draft","tone":"automation","definition":"How the curator of a domain host confirms that a bundle belongs, what the domain's four concept types hold, what moves a member, and how to read the workspace the domain's releases build."},"playbooks/knowledge-outside-the-repository":{"title":"Knowledge outside the repository","type":"Playbook","genre":"how-to","label":"checked by automation only, still a draft","tone":"automation","definition":"How the ingest mirrors Confluence pages, web pages and PDFs, files in another git repository and a command's output into `.lokf/mirror/`, with the manifest `.lokf/ingest.yaml`, the lock, sensitivity, the weekly pull request, and how the librarian cites a mirror file."},"playbooks/knowledge-sources":{"title":"Knowledge sources","type":"Playbook","genre":"how-to","label":"edited since a person last confirmed it (confirmed 2026-10-13, edited 2026-10-28), reopened 2026-10-27 by noelmcloughlin: 1 question waits","tone":"edited","definition":"Map of the repository locations this bundle was derived from, and how to re-check each on a future refresh."},"playbooks/ktl-curator-skill":{"title":"ktl-curator skill","type":"Playbook","genre":"how-to","label":"edited since a person last confirmed it (confirmed 2026-10-13, edited 2026-10-29), reopened 2026-10-29 by noelmcloughlin: 1 question waits","tone":"edited","definition":"A human curator's assistant: a one-screen report of what needs a person's attention, then a review session that records that person's confirm, correct, retire or send-back verdicts in the bundle's frontmatter, including on a domain host's member concepts."},"playbooks/ktl-docent-skill":{"title":"ktl-docent skill","type":"Playbook","genre":"how-to","label":"edited since a person last confirmed it (confirmed 2026-10-13, edited 2026-10-29), reopened","tone":"edited","definition":"The reader's side: it answers questions from the bundle first, with each concept's trust label, falls back to the repository when the bundle cannot answer, and records misses and disagreements for the librarian; it also answers for younger readers and from a domain host's workspace."},"playbooks/ktl-librarian-skill":{"title":"ktl-librarian skill","type":"Playbook","genre":"how-to","label":"edited since a person last confirmed it (confirmed 2026-10-13, edited 2026-10-29), reopened","tone":"edited","definition":"Recurring procedure that scrapes the host repository, derives and maintains the .lokf/ concepts and their typed relations, audits the bundle, and hands off for human review."},"playbooks/ktl-prose-skill":{"title":"ktl-prose skill","type":"Playbook","genre":"how-to","label":"checked by automation only, still a draft","tone":"automation","definition":"The librarian's copy editor. It rewords the body of a concept an agent wrote, in plain English, before a person confirms it, changing the wording and never a fact or a frontmatter byte, and its script proves that only the wording changed."},"playbooks/ktl-sidecar-skill":{"title":"ktl-sidecar skill","type":"Playbook","genre":"how-to","label":"checked by automation only, still a draft","tone":"automation","definition":"Procedure that creates a .lokf/ sidecar, tooling, docs, a dummy skeleton, and the knowledge_bundle doorway link beside it, from bundled templates, or repairs a missing or broken sidecar file, then hands off to ktl-librarian."},"playbooks/ktl-website-skill":{"title":"ktl-website skill","type":"Playbook","genre":"how-to","label":"checked by automation only, still a draft","tone":"automation","definition":"Procedure that installs an Astro Starlight website for the knowledge bundle in `website/` from bundled templates, with a page per concept and its trust label, a health page and the knowledge graph, and a workflow that publishes it to GitHub Pages once `KNOWLEDGE_WEBSITE_ENABLED` is set; or repairs and updates a site it installed, and hands the maintainer the steps that retire an mkdocs site it replaces."},"playbooks/open-bundle-in-obsidian":{"title":"Open the knowledge bundle in Obsidian","type":"Playbook","genre":"how-to","label":"checked by automation only, still a draft","tone":"automation","definition":"How a knowledge bundle meets an Obsidian vault: two vaults, the workshop someone keeps and the bundle opened as its own through the `knowledge_bundle` doorway, what Obsidian does with the link on each host, and why the bundle is never a real folder inside a vault."},"playbooks/releasing":{"title":"Releasing","type":"Playbook","genre":"how-to","label":"checked by automation only, still a draft","tone":"automation","definition":"How a release happens: `semantic-release.yml` computes the version from Conventional Commits and promotes `CHANGELOG.md` on merge to `main` but never tags, and a maintainer's `publish.yml` run checks that version against the changelog, lets `gh skill publish` create the tag and release, dispatches `knowledge-release.yaml` to attach the bundle, domain schema and Copilot zips, and asks the sibling hosts to sync."},"playbooks/repository-validation":{"title":"Repository validation","type":"Playbook","genre":"how-to","label":"checked by automation only, still a draft","tone":"automation","definition":"What CI checks on every pull request and weekly: the repository contract, the Agent Skills spec, shell and workflow linting, the install and website smoke tests, and Markdown, link and spelling checks."},"playbooks/website":{"title":"Build, preview and edit the website","type":"Playbook","genre":"how-to","label":"edited since a person last confirmed it (confirmed 2026-10-13, edited 2026-10-26), reopened","tone":"edited","definition":"How the project website in `website/` is built with Astro Starlight from the README, `docs/`, the knowledge bundle, `CHANGELOG.md` and, when shown, the LinkML schema's pages and data; how to preview it locally with npm and uv; which file to edit for each kind of change; and how `knowledge-website.yaml` publishes it to GitHub Pages, on a push, weekly or by hand."},"policies/ai-covenant":{"title":"AI covenant","type":"Policy","genre":"reference","label":"confirmed by a person, 2026-10-13","tone":"person","definition":"Community norms for AI use - contributors own what they submit regardless of tooling, AI systems must not be used to autonomously post comments, replies, or messages, AI co-authorship in commit messages is discouraged, and a repository-owned agent (e.g. ktl-librarian) must commit under a bot or maintainer identity with no trailer either way and land only as a human-reviewed PR."},"policies/code-of-conduct":{"title":"Code of conduct","type":"Policy","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"Contributor Covenant v2.1: its scope over issues, pull requests and discussions, and how to report unacceptable behaviour."},"policies/security":{"title":"Security policy","type":"Policy","genre":"reference","label":"edited since a person last confirmed it (confirmed 2026-10-19, edited 2026-10-28), reopened","tone":"edited","definition":"How to report a vulnerability privately, supported versions, and a surface table (what executes here, what guards it) that links to the shared threat model instead of restating it."},"policies/threat-model":{"title":"Threat model","type":"Policy","genre":"reference","label":"edited since a person last confirmed it (confirmed 2026-10-13, edited 2026-10-28), reopened","tone":"edited","definition":"The security design the three KTL repositories share, kept in one place so each SECURITY.md can link to it: repository hardening, the human:-attribution gate on a verified event, and the prompt-injection guard for each input path that reads content it did not author."},"policies/versioning":{"title":"Versioning policy","type":"Policy","genre":"reference","label":"edited since a person last confirmed it (confirmed 2026-10-03, edited 2026-10-28), reopened","tone":"edited","definition":"One repository-level semantic version covering all six skills, released together under a single tag, with patch, minor and major decided by Conventional Commits."},"references/agent-skills-specification":{"title":"Agent Skills specification","type":"Reference","genre":"reference","label":"confirmed by a person, 2026-10-13","tone":"person","definition":"The specification defining a skill directory - a required SKILL.md with name/description frontmatter, plus optional scripts/, references/, and assets/."},"references/gh-skill-cli":{"title":"gh skill (GitHub CLI)","type":"Reference","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"The GitHub CLI command group that installs, pins, and publishes agent skills from GitHub repositories; the publish path this repository uses for releases."},"references/linkml":{"title":"LinkML (linkml.io)","type":"Reference","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"The schema-modelling language LOKF is written in, and the generator suite that turns a schema into JSON Schema, Pydantic models, SHACL shapes, docs, and OWL."},"references/lokf-specification":{"title":"LOKF specification","type":"Reference","genre":"reference","label":"confirmed by a person, 2026-09-26","tone":"person","definition":"The canonical definition of the Linked Open Knowledge Format - a semantic profile of OKF binding every field, type, and relationship to schema.org, DCAT, and PROV-O."},"references/lokf-toolkit":{"title":"LOKF toolkit (lokf on PyPI)","type":"Reference","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"The lokf Python package, which validates, converts and serves a LOKF bundle and is the dependency the scaffolded .lokf/pyproject.toml declares."},"references/okf-specification":{"title":"OKF specification (v0.2)","type":"Reference","genre":"reference","label":"confirmed by a person, 2026-10-13","tone":"person","definition":"Google's Open Knowledge Format - a folder of Markdown concept files with YAML frontmatter, requiring only `type`, plus the v0.2 provenance, trust, and lifecycle families."},"references/open-skills-cli":{"title":"Open Skills CLI (npx skills)","type":"Reference","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"The vendor-neutral installer for agent skills, `npx skills add`, which takes a local path as its source, so this repository uses it as a pre-publication install check."},"young-readers/the-pen":{"title":"The pen, for readers aged 13 to 18","type":"Glossary term","genre":"reference","label":"checked by automation only, still a draft","tone":"automation","definition":"The name the docs give `knowledge-apply.sh`, the script through which ktl-librarian writes every change to the bundle."}}