Skip to content
Knowledge Trust Ladder

Playbooks

  • Build, preview and edit the website edited since a person last confirmed it (confirmed 2026-10-13, edited 2026-10-26), reopened
    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.

  • Contributing checked by automation only, still a draft
    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.

  • Curating a domain bundle checked by automation only, still a draft
    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.

  • Knowledge outside the repository checked by automation only, still a draft
    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.

  • Knowledge sources edited since a person last confirmed it (confirmed 2026-10-13, edited 2026-10-28), reopened 2026-10-27 by noelmcloughlin: 1 question waits
    Map of the repository locations this bundle was derived from, and how to re-check each on a future refresh.

  • ktl-curator skill edited since a person last confirmed it (confirmed 2026-10-13, edited 2026-10-29), reopened 2026-10-29 by noelmcloughlin: 1 question waits
    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.

  • ktl-docent skill edited since a person last confirmed it (confirmed 2026-10-13, edited 2026-10-29), reopened
    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.

  • ktl-librarian skill edited since a person last confirmed it (confirmed 2026-10-13, edited 2026-10-29), reopened
    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.

  • ktl-prose skill checked by automation only, still a draft
    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.

  • ktl-sidecar skill checked by automation only, still a draft
    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.

  • ktl-website skill checked by automation only, still a draft
    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.

  • Open the knowledge bundle in Obsidian checked by automation only, still a draft
    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.

  • Releasing checked by automation only, still a draft
    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.

  • Repository validation checked by automation only, still a draft
    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.

  • The docent in Microsoft 365 Copilot checked by automation only, still a draft
    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.