What Knowledge Trust Ladder is for, and what it is not

Overview

The README states what the project is. It keeps a repository’s scattered knowledge as a collection: catalogued, authenticated and explained, with the trust in every claim visible. The architecture page says what is missing is a context layer, and that a knowledge bundle is the catalogue. A context layer is a governed layer between the sources and whoever consumes them, person or agent. The sources are code, documents, diagrams, policies and operational records. The layer persists from one task to the next. The architecture page’s term links docs/context-layer.md, which sets it beside the industry’s and says one bundle is one repository’s context layer (the context layer).

The architecture page frames it around one question: who is responsible for the quality of this context? An agent derives the bundle, deterministic tools check it, a named person vouches for it, and the bundle records which of the three happened to every claim.

One page now answers this for one kind of repository. docs/skills-repositories.md says that in a repository whose content is Agent Skills, KTL helps with the knowledge around the skills and leaves the skills as they are. It leaves whether a skill works to an evaluation, since KTL’s checks cover the form and the provenance of what the bundle says.

No source says in general which kinds of use KTL fits and which it does not. Two neighbouring concepts cover parts of the ground: three lines of defence places the roles in a governance model, and domain schemas covers modelling a regulated domain (AI governance among them). Neither states intended uses or non-goals.

Open questions

• 2026-09-24, process:ktl-librarian: Readers asked whether KTL can be used for DevSecOps and for technology governance (ktl-docent feedback, 2026-09-24). No repository source states which uses KTL is meant for and which it is not - for example, that it keeps knowledge about systems rather than scanning or enforcing anything. A maintainer should either write that in a source (README or a docs page) for this concept to follow, or retire this placeholder.