Glossary

• Accession checked by automation only, still a draft
  A museum’s word for an item added to its collection, which the registrar keeps documented with its provenance filed; in the bundle, each concept added is one.

• Collection checked by automation only, still a draft
  A repository’s scattered knowledge as Knowledge Trust Ladder keeps it: catalogued, authenticated and explained, with the trust in every claim left visible. Each item added to the collection is an accession.

• Context layer checked by automation only, still a draft
  A governed layer between an organisation’s sources and whoever consumes them, person or agent, that persists from one task to the next. One knowledge bundle is one repository’s context layer, and KTL federates many bundles into one layer through domains.

• Curator checked by automation only, still a draft
  The role that holds the scales, always a person: in the museum sense, the one who authenticates, weighs provenance and decides what goes on exhibit. The ktl-curator skill and the KTL Curator plugin are that person’s assistants, and reach no verdict of their own.

• Desk checked by automation only, still a draft
  The library word for the place where a role does its work with the bundle: the registrar is knowledge-apply.sh at the librarian’s desk, and knowledge-report.sh at the reader’s and the curator’s.

• Docent checked by automation only, still a draft
  A museum’s name for a guide, and the role that answers a reader’s questions from the bundle, says how far each answer has been checked, and writes nothing in the bundle.

• Domain schema checked by automation only, still a draft
  A schema written in LinkML that extends LOKF’s, for a domain whose concepts stop fitting LOKF’s short list of classes, so the domain’s own types are checked rather than tolerated. The curator flags concepts that no longer fit, the team decides, and the librarian applies it.

• Doorway checked by automation only, still a draft
  knowledge_bundle, the link at a host’s root that ktl-sidecar creates onto the bundle, so the hidden .lokf/knowledge folder has a name a folder picker can see. Obsidian opens the bundle as a vault of its own through it.

• Exhibition checked by automation only, still a draft
  In the two-vault arrangement for Obsidian, the bundle opened as a small vault of its own: the checked part of what the workshop knows, which teammates, CI and agents read. The README’s Exhibitions are the sites that show a repository’s collection.

• Health line checked by automation only, still a draft
  The one line knowledge-report.sh prints for the whole bundle, counting its concepts under eight trust labels, such as “Confirmed by a person: 3 of 40” and “Reopened”. It is derived on every read and never stored, and it is the number to watch over time.

• Knowledge bundle edited since a person last confirmed it (confirmed 2026-10-18, edited 2026-10-19), reopened
  The knowledge bundle, .lokf/knowledge: one Markdown file per concept, readable as documentation and queryable as a graph; how it differs from the .lokf/ sidecar, what its reserved index.md and log.md hold, and the knowledge_bundle doorway that Obsidian opens as a vault of its own.

• Librarian checked by automation only, still a draft
  The role that binds a repository’s knowledge into order, played by the ktl-librarian skill: it derives concepts with their sources, classifies and links them, audits, and hands off for review. It catalogues without vouching, and writes the bundle only through the pen.

• LinkML checked by automation only, still a draft
  The schema language LOKF is written in, created by the LinkML Community. LOKF’s specification is a single LinkML schema, from which the JSON Schema, JSON-LD context, SHACL shapes and OWL ontology are generated, and a domain schema that extends it is written in LinkML too.

• LOKF checked by automation only, still a draft
  The Linked Open Knowledge Format, the semantic profile of OKF this bundle is written in, which binds every field to a public vocabulary so the bundle projects to RDF.

• OKF checked by automation only, still a draft
  The Open Knowledge Format, Google’s specification for a folder of Markdown concept files with YAML frontmatter, which LOKF profiles.

• Registrar checked by automation only, still a draft
  The person in a museum who keeps the collection’s records, and Knowledge Trust Ladder’s fifth role, which programs play: the lokf toolkit, the gate knowledge-registrar.yaml (or knowledge-provenance.sh on another forge or none), the pen and the report script.

• Sidecar checked by automation only, still a draft
  .lokf/, the folder beside a project’s code that holds the bundle and the tooling that checks it, kept out of the project’s build; also the role, and the ktl-sidecar skill, that installs it.

• The pen checked by automation only, still a draft
  The name for knowledge-apply.sh, the only way ktl-librarian writes the bundle: it applies the operations in .lokf/patch.yaml, stamps generated, keeps the index in step, and refuses a human: actor.

• Three lines of defence checked by automation only, still a draft
  The model regulated industries use to say who owns a risk, who keeps the rules and who checks independently, whose reference version is the IIA’s Three Lines Model. In Knowledge Trust Ladder the librarian and the curator are the first line, the registrar the second, and the bundle holds the evidence a third line would need.

• Trust label edited since a person last confirmed it (confirmed 2026-10-19, edited 2026-10-29)
  The plain words the skills use for how far a concept has been checked, derived from its frontmatter on every read and never stored.

• Trust ladder checked by automation only, still a draft
  Knowledge Trust Ladder’s answer to who is responsible for the quality of the context: written into each concept, where it came from and how far it has been checked, as rungs a claim climbs from still a draft to confirmed by a person.

• Work list checked by automation only, still a draft
  What knowledge-report.sh worklist prints for ktl-librarian before each refresh, from frontmatter and git, in paths and dates and nobody’s words: the concepts whose sources moved since they were derived or last checked, the notes a person left and the librarian’s own open questions. It also counts the reader feedback that waits.

• Workshop checked by automation only, still a draft
  In the two-vault arrangement for Obsidian, the vault a person already has, in which nothing is moved or migrated. The bundle opens beside it as the exhibition, a small vault of its own, and the two never index the same file.