A logo mark, .assets/knowledge-trust-ladder-logo.svg: a ladder rising out of an open book, its top rung the check mark, the rungs grey then amber then the curator’s blue. Shared byte-for-byte with both plugin repositories, and the mark to use as the repository avatar.
Every diagram carries the mark and the wordmark, from one shared definition. The social-preview card’s title is the wordmark and a tagline, not the repository slug.
docs/install.md: the gh skill commands, the per-skill prerequisites and the pinning rule, moved out of the README.
The README states the runtime claim. OKF’s fourth goal asks for frontmatter that makes a corpus trustable “without prescribing any runtime”; this is such a runtime.
The README names its order of work: specification first, schema first, interoperability first - nothing here invents a field, a format or a validator.
The README names the context layer, and the question that layer comes back to - who is responsible for the quality of this context - as the one the trust ladder answers.
The README claims the domain schemas OKF puts out of scope, in scope here by construction, and points at the curator’s domain-schemas.md for the flag and the recipe.
Changed
The README is a front door, not the manual. 1,792 words to 1,864: much the same length, a different shape. Install commands out to docs/install.md; the closing sections collapsed into one Read on table.
The opening says “collection”, not “library”, which this audience reads as a code library. A collection is what a librarian, a registrar, a curator and a docent all serve.
The opening names the whole system - four skills, the registrar automation, the lokf toolkit underneath - and the two Obsidian plugins as optional.
The sidecar bootstraps a fresh knowledge_bundle in the README’s words, the visible doorway, with .lokf/ named as what lies behind it.
This repository is now knowledge-trust-ladder, formerly lokf-agent-skills. Upstream LOKF ships its own bundled skills, and a third-party repository named after the format read as their official home.
The four skill names are unchanged - they are installed paths in every host. GitHub redirects the old clone and npx skills add paths.
TRUST_LADDER_SKILLS_REPO moves with the repository (renamed from LOKF_SKILLS_REPO, to match the repository’s own name). A host that copied the template earlier keeps working through the redirect until it copies again.
The bundle’s base_iri is https://knowledge-trust-ladder.example/knowledge/, which re-ids all 30 concepts and every typed-relation target.
lokf-trust-ladder.svg is now trust-ladder.svg: under the new repository name the old filename read as the project’s mark rather than the diagram’s.
The bundle’s log keeps the name the project had on each day. The rename pass had rewritten entries written weeks earlier, including the one recording the old base_iri; CHANGELOG.md was left alone, and the log is the bundle’s own record.
The repository contract refuses the old name (check 16). CHANGELOG.md, the bundle’s log.md and one “formerly” line in docs/install.md are the exceptions, because they record history.
The three-lines diagram is keyed to the legend it shares. Its bands made the first line green and the second blue, where green means agent work and blue a named person - so the registrar sat in the person’s colour and the curator in the agent’s. Neutral bands now, and each card takes the colour of whoever acts.
Labels no longer collide with their own boxes: six across four diagrams overflowed or came within 2px, one of them hidden behind a card painted over it.
The diagrams no longer glare. A pure-white canvas was the brightest thing on the page, with the tinted cards below it; all seven assets now use the warm #E4E1D7, an even three-step ramp from canvas to panel to card. Green and blue were rejected for it - in these diagrams they mean agent work and a named person.
Small grey labels are legible again: the faint ink moved from #888780 to #6E6D66, clearing 4.5:1 where it had been 3.6:1.
LOKF_SKILLS_REPO/LOKF_SKILLS_REF are now TRUST_LADDER_SKILLS_REPO/TRUST_LADDER_SKILLS_REF. The old names said “LOKF” for the repository itself, which is now knowledge-trust-ladder; the skills stay lokf-*, only the repository pointer is renamed. Each sibling’s own copy of the workflow needs the same rename before it next syncs from the template.
Fixed
The librarian template pins a release that exists.publish.yml promotes the top CHANGELOG.md heading before its tag exists, so pinning to that heading fails check 15’s own clone test until the tag lands; the template now pins v0.19.5, the newest release a host can actually clone.
