Skip to content
KTL Registrar

All versions since 1.2.2

All versions

1.2.2

Fixed

  • Retitling a pull request re-runs the release checks. The title check told the author to retitle, but the workflow listened only for the default pull-request types, so a title change fired nothing and the check stayed red whatever the author did. The trigger now names edited.

1.2.3

Added

  • The family logo, .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 the other two repositories; beside the README title, and the mark to use as the repository avatar.
  • Both diagrams carry the mark and the wordmark, from the same shared definition.

Changed

  • The diagrams no longer glare. A pure-white canvas was the brightest thing on the page, with the tinted cards sitting below it; it is now the warm #E4E1D7, so the cards read as raised.
  • 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.
  • The skills 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.
  • Every link here follows it, and LOKF_SKILLS_REPO in the scheduled librarian names the new repository. The skill names, the pinned LOKF_SKILLS_REF and this plugin’s own name are unchanged; GitHub redirects the old paths either way.
  • A label hidden behind its own card. The curator card’s “a few at a time” was painted before the card that contains it; two labels in the plugins card came within 3px of their edges.
  • Both diagrams match the skills repository’s copies byte for byte.
  • The bundle’s log keeps the name the skills repository had on each day. The rename pass had rewritten entries written weeks before it; CHANGELOG.md was left alone, and the log is the bundle’s own record.

1.2.4

Changed

  • The scheduled librarian installs v0.19.7, up from v0.19.2, so it runs the current skill rather than one five releases behind.
  • LOKF_SKILLS_REPO/LOKF_SKILLS_REF are now TRUST_LADDER_SKILLS_REPO/TRUST_LADDER_SKILLS_REF, following the skills repository’s own rename: the names said “LOKF” for a repository now called knowledge-trust-ladder. The skills keep their lokf-* names.

1.2.5

Security

  • The provenance gate reads a concept whatever its name. Synced from the skills repository’s v0.19.5 templates: both gates list paths with core.quotePath off and refuse a path git still has to quote, so a human: confirmation in a non-ASCII-named concept no longer passes unread.

1.2.6

Fixed

  • An external source or definedBy is no longer flagged as dangling. Both slots are documented as taking an off-site URL, but the audit reported any untyped IRI target as missing. Nothing in this bundle tripped it - every target happens to point at a concept.
  • The predicate list cannot go stale again. It had drifted against the schema, missing holder, measures, memberOf and every reified relations entry; --check-refs reads the slots from the schema instead.
  • The scheduled librarian checks the relations it writes. Its validate step covered frontmatter shape only, leaving a fabricated target - an agent’s likeliest mistake - for the registrar gate to catch. It passes --check-refs now.

Changed

  • The registrar gate validates once. --check-refs rides on the existing validate step, replacing a second lokf validate run through uvx --from rust-just just.

1.2.7

Fixed

  • The scheduled librarian installs v0.21.0, up from v0.19.7, so it runs the current skill rather than two releases behind.
  • The publish job’s path check reads a concept named outside ASCII. It listed the patch’s paths with git’s default quoting, so such a path arrived C-quoted and was refused as outside the bundle. Synced from the skills repository’s template: it now lists with core.quotePath off.

1.2.8

Fixed

  • The type-check survives a TypeScript 7 / @types/node 26 bump. moduleResolution: "bundler" drops the "node" package.json export condition by design; a newer @types/node gates its node:fs/node:path/node:url/node:module subpaths on that condition, so scripts/smoke-test.ts’s plain-Node imports stopped resolving. customConditions: ["node"] in tsconfig.json re-adds it. lib moves to ES2022 for Array.prototype.at() in src/main.ts; esbuild.config.mjs’s own output target is unaffected.

1.3.0

Added

  • A dark counterpart for all three diagrams, *-dark.svg beside each original. Same geometry and wording; only the palette differs, re-toned role for role from the light one. Shared byte-for-byte with the other repositories.
  • The README picks by theme. Each diagram is a <picture> with a prefers-color-scheme: dark source over the existing file, so the light original stays the fallback and its path is unchanged.

Changed

  • The registrar’s logo has no check mark. Its ladder stops at the amber rung, checked by automation; the blue tick, a named person’s confirmation, is the curator’s alone. The logo is no longer shared byte-for-byte with the other repositories.

Fixed

  • A dark copy carries no stale content credential. The originals embed a C2PA manifest that signs their own bytes; recolouring changes those, so the copies ship without one rather than with a signature that cannot verify.

1.4.0

Changed

  • The ribbon and tab carry the trust ladder, not Lucide’s shield-half. No check mark on top: this plugin keeps every record well-formed and never vouches for one, so the check belongs to KTL Curator, whose icon is this ladder with it. Line art at Lucide’s weight, in currentColor, so it sits with Obsidian’s own icons and follows any theme.

1.4.1

Fixed

  • The description names the role as the project does. LOKF is “a semantic profile of OKF”, and the registrar keeps a vault well-formed. The manifest, the package and the community listing entry carry the same sentence.

1.5.0

Added

  • A dimmed counterpart for all three diagrams, *-dimmed.svg beside each original: the same geometry on warm grey paper rather than a dark one. The two shared diagrams are byte-for-byte with the other repositories; the logo keeps this repository’s own ladder, which stops at the amber rung.

Changed

  • The dark-mode source is the dimmed set. Each prefers-color-scheme: dark source now points at *-dimmed.svg; the *-dark.svg files from 1.3.0 stay in .assets/ but nothing references them.

Fixed

  • The dimmed ink follows the dimmed paper. The light diagrams sit right on 4.5:1, so darkening only the backgrounds would have dropped every faint label under it.
  • Three labels that never met 4.5:1 now do, on the greyed-out roles in the plugin card - the darker ink reaches them as well.

1.5.1

Changed

  • The README and docs/for-the-curious.md are restyled for the reader: shorter sentences, plain statements, labels set off with a colon, the OKF base layer as a table. The section Philosophy: warnings, not errors, almost everywhere is now Why almost everything is a warning, and the host-by-host layouts live once in the skills’ docs/obsidian.md.

Fixed

  • The scheduled librarian installs its skill from v0.23.0. The pin still named v0.21.0, which has no skills/ktl-librarian, so the weekly run had failed at that step since the plugin took the KTL name.

Security

  • The sidecar carries knowledge-feedback.sh. ktl-docent records a reader’s gap through it and never opens feedback.md, so no other reader’s text enters its session (Snyk W011). It comes from the v0.23.0 templates, the release the pin now names.

1.5.2

Security

  • The sidecar’s preflight and skills pin match v0.23.1. The preflight now compares a librarian workflow with the template’s apart from TRUST_LADDER_SKILLS_REF, which each repository moves on its own schedule. This repository has no bare skills/ directory for that check to compare against, so its output does not change; no plugin change.

1.5.3

Security

  • The sidecar copies and the skills pin match v0.25.0. The scheduled librarian installs its skill from that release. knowledge-release.yaml is new: it attaches the bundle to a release as knowledge-<tag>-<repository>.zip unless the bundle matches the last release’s, runs when dispatched by hand and on each published release once KNOWLEDGE_RELEASE_ENABLED is true, and is otherwise inert. The librarian workflow and wrapper hand the agent its credential, the AGENT_API_KEY secret or the job’s own token with AGENT_USE_JOB_TOKEN, under the name AGENT_API_KEY_ENV gives and to nothing else; the job requests copilot-requests: write for Copilot CLI, idle until then, and sets up Node 22 for an npx-run agent. knowledge-preflight.sh compares the new workflow with its template.

1.5.4

Security

  • The sidecar copies and the skills pin match v0.26.0. Conventions rule 11 rejects an at: later than the commit that recorded it; the six librarian times in this bundle that broke it now carry that commit’s time. knowledge-librarian.yaml matches its template apart from the pin. No plugin change.

1.5.5

Security

  • The sidecar copies and the skills pin match v0.27.0. Releases now carry the docent as a Microsoft 365 Copilot skill: knowledge-release.yaml attaches ktl-docent-m365-<tag>-<repository>.zip beside the bundle zip, checks each zip against its checksum and attests each one. The new .lokf/m365/ holds that skill’s instructions, ktl-docent-m365.md, and knowledge-m365.sh, which builds it from a snapshot of the bundle; knowledge-preflight.sh compares both with their templates, and CONTRIBUTING.md and SECURITY.md count them among the copies that move with the pin. The release workflow stays inert until KNOWLEDGE_RELEASE_ENABLED is true. No plugin change.

1.5.6

Security

  • The sidecar copies and the skills pin match v0.33.0. The scheduled librarian’s one output is now .lokf/patch.yaml. knowledge-apply.sh, new here, checks every operation in it and writes the bundle, and keeps an index in the shape a person gave it. publish reads each person’s event and note off the patched tree before it pushes, and the registrar gate asks the person behind a confirmation that a change removes, as it asks the one behind a confirmation it adds. knowledge-report.sh, also new, computes the health line and the record changes the pull request carries. A scheduled week with nothing waiting runs no agent, though a month’s first week always does. A handled feedback entry moves to .lokf/questions.md, and the librarian’s hand-off reaches the pull request in a code block. Release assets take their name from KNOWLEDGE_RELEASE_NAME when it is set, and a retrieval score runs only once KNOWLEDGE_RETRIEVAL is true.

    Conventions rule 12 holds an index bullet equal to its concept’s title and description, so the apply script’s reindex operation re-derived the bullets of the five concepts here that had drifted. Rule 13 fails a change to a confirmed concept that does not move its generated stamp past the confirmation. The scripts’ comments read plainer. SECURITY.md names the new path and checks, and says the workflow copy differs from its template only in the pin. No plugin change.

1.5.7

Security

  • The sidecar copies and the skills pin match v0.34.0. The pin names the tag’s commit too, in TRUST_LADDER_SKILLS_SHA, and the librarian’s install step installs nothing unless the tag still names that commit. The librarian workflow has a third job, earlier, which reads the workflow’s earlier pull requests under a token that reads pull requests and nothing else. A scheduled run then opens no second pull request beside an open one, and does not propose again what a person declined. The pen refuses a patch that would change a person’s record, and writes each frontmatter value back as the file held it. The registrar gate and the release workflow install the toolkit with uv sync --locked, and the conventions script and the pen pin PyYAML. A week is quiet again once the librarian has asked about a source it cannot act on.

    CONTRIBUTING.md says the two pin values move together, and no longer says the librarian workflow carries local changes. No plugin change.

1.5.8

Security

  • The sidecar copies and the skills pin match v0.34.1. The Copilot docent’s instructions, .lokf/m365/ktl-docent-m365.md, label a concept as the report script does. A retired concept carries no other label, edited since a person last confirmed it takes the place of confirmed by a person, and an empty verified list reads as nobody has checked this yet. A Miss in its gap report starts with the reader’s question and says whether a concept looked relevant from index.md. No plugin change.

1.5.9

Security

  • The sidecar copies and the skills pin match v0.34.2. The preflight reads the CI variables by indirect expansion rather than eval, so a scanner that searches for eval finds none, and its output is unchanged. When knowledge-feedback.sh or knowledge-report.sh is missing, it names ktl-curator and an earlier ktl-docent as the skills that need it, since ktl-docent now runs its own copies. The scheduled librarian installs a ktl-librarian that reads LOKF’s schema from a commit rather than a tag (Snyk W012). No plugin change.

1.5.10

Fixed

  • The relation rules cover measures, memberOf and holder. The LOKF schema ranges thirteen slots over Concept, and the plugin’s list had the first ten. A bare scalar in one of the three went unflagged, with no Make it a list fix, no target completion, and no edge in the concept graph or in the proposals. The smoke test now holds the list to the pinned schema manifest, as the skills repository’s contract holds its report script’s copy to the schema, and scripts/build-vocab.mjs keeps each slot’s range and cardinality in the manifest. The built-in knownPredicates default stays as it was, so an untouched setting is still refreshed from the schema on upgrade.

1.5.11

Security

  • The sidecar copies and the skills pin match v0.37.1. The provenance gate reads a verified or generated event that spans lines, or that sits behind a byte order mark or CRLF line endings, so a forged confirmation cannot hide in either. The unattended check follows a renamed concept. The pen refuses a provenance key in any letter case, and keeps a curator’s send-back. The report reads every timestamp and event layout, names a retired concept’s successor, marks a concept a reader disputed, and counts reliance through all thirteen relation fields. Conventions rule 14 refuses a commit that records a person’s confirmation and also changes what the concept says. No plugin change.

1.5.12

Changed

  • The sidecar’s README links OKF’s specification in its own repository. Google moved the Open Knowledge Format to GoogleCloudPlatform/open-knowledge-format and froze the copy under knowledge-catalog/okf/.

Security

  • The sidecar copies and the skills pin match v0.38.2. The registrar, librarian and release workflows run the justfile’s lokf-check-refs recipe, and their actions move to newer pinned releases. The docent’s Copilot instructions prefer a retelling for a younger reader, and give the adult concept’s label with it. The pen no longer adds a second “edited since” note to a log line that already has one. The scheduled librarian installs a ktl-librarian that retells a confirmed concept for younger readers when the curation policy declares a band. No plugin change.

1.5.13

Security

  • The sidecar copies and the skills pin match v0.39.0. The preflight looks for ktl-website among the installed skills. The librarian and release workflows say their variables go under Repository variables, never on an environment, which neither job can read, and the scheduled librarian installs a ktl-librarian whose setup page says the same. No plugin change.

1.5.14

Changed

  • The architecture and for-the-curious pages lose their dead sentences. The host-by-host section, the independence paragraph and the warnings section say each fact once, and link what the skills’ pages already record. No plugin change.
  • The README is a doorway, in the style of Knowledge Trust Ladder’s. It keeps the poem, the opening paragraph and the agents note, and links the quick start, the architecture and the usage pages. What a bundle is, the two vaults, which folder is the bundle, privacy, the development layout and the credits moved to docs/architecture.md; the quick start and the install routes to docs/install.md; the report panel, the commands, the settings and the read-only API to docs/using.md. No plugin change.

1.5.15

Security

  • The sidecar copies and the skills pin match v0.41.0. The scheduled librarian takes an agent that wants its prompt somewhere other than after -p, named by the repository variable AGENT_PROMPT_FLAG. It writes its patch with the agent’s own file tool, so an agent refused a shell write no longer gives up. Both came with the v0.40.0 copies, which 1.5.14 included without an entry; v0.41.0 changes only ktl-website, which this repository does not use. No plugin change.

1.5.16

Security

  • The sidecar copies and the skills pin match v0.42.0. Conventions rule 13 no longer reads a move of the bundle’s base_iri as an edit of every confirmed concept. No plugin change.

1.5.17

Security

  • The skills pin matches v0.43.0. The release changed none of the sidecar copies this repository carries. No plugin change.

1.5.18

Fixed

  • .lokf/justfile takes a domain schema as one variable. It was the copy from before ktl-sidecar v0.38.0, which the sidecar sync never carried. No plugin change.

1.5.19

Security

  • The skills pin matches v0.43.1. The release changed none of the sidecar copies this repository carries. No plugin change.

1.6.0

Added

  • A website for the knowledge bundle. website/ builds an Astro Starlight site from .lokf/knowledge, the README, docs/ and this changelog, with a trust label on every concept page; knowledge-website.yaml publishes it to GitHub Pages once KNOWLEDGE_WEBSITE_ENABLED is true. No plugin change.

1.6.1

Fixed

  • The website’s link check reads an address in a code span without its closing backtick. A concept that named the site’s address in backticks failed the build with a broken link in llms.txt. The script matches ktl-website’s fixed template. No plugin change.

1.7.0

Changed

  • The knowledge bundle’s namespace is https://w3id.org/ktl/registrar/knowledge/. It was the placeholder https://ktl-registrar.example/knowledge/, and every concept’s id moved with it, so the bundle can join the KTL federation. The golden fixture of this repository’s own bundle expects one warning fewer, since the placeholder warning is gone. No plugin change.

1.7.1

Security

  • The skills pin matches v0.44.0. The release changed none of the sidecar copies this repository carries. No plugin change.

1.7.2

Security

  • The sidecar copies and the skills pin match v0.45.0. The release changed .lokf/scripts/knowledge-report.sh, .lokf/m365/ktl-docent-m365.md, website/scripts/sync.mjs, website/src/components/ConceptCard.astro, website/src/content.config.ts and website/src/styles/catalogue.css here; its changelog says how.

1.7.3

Security

  • The sidecar copies and the skills pin match v0.45.1. The release changed .lokf/scripts/knowledge-apply.py and .lokf/scripts/knowledge-federate.py here; its changelog says how.

1.7.4

Security

  • The sidecar copies and the skills pin match v0.46.0. The release changed .github/workflows/knowledge-release.yaml, .lokf/scripts/knowledge-federate.py, website/package-lock.json and website/package.json here; its changelog says how.

1.7.5

Security

  • The sidecar copies and the skills pin are at Knowledge Trust Ladder v0.47.0. The release changed .lokf/scripts/knowledge-preflight.sh, .github/workflows/knowledge-sync.yaml, .github/PULL_REQUEST_TEMPLATE/knowledge-sync.md and .lokf/scripts/knowledge-sync.sh here. No plugin change.

1.7.6

Security

  • The sidecar copies and the skills pin are at Knowledge Trust Ladder v0.52.0. The release changed .github/workflows/knowledge-registrar.yaml, .github/PULL_REQUEST_TEMPLATE/knowledge-sync.md, .lokf/scripts/knowledge-conventions.sh, .lokf/scripts/knowledge-conventions.py, .lokf/scripts/knowledge-preflight.sh, .lokf/scripts/knowledge-report.sh and .lokf/scripts/knowledge-sync.sh here. No plugin change.

1.7.7

As it stood at this release: the repository · the docs · the knowledge bundle · the release

Security

  • The sidecar copies and the skills pin are at Knowledge Trust Ladder v0.53.0. The release changed .github/workflows/knowledge-librarian.yaml, .github/workflows/knowledge-sync.yaml, .github/PULL_REQUEST_TEMPLATE/knowledge-sync.md, .lokf/scripts/knowledge-librarian.sh, .lokf/scripts/knowledge-apply.py, .lokf/scripts/knowledge-sync.sh, .lokf/.gitignore, website/scripts/config.mjs, website/scripts/markdown-ktl.mjs, website/scripts/sync.mjs, website/src/components/KnowledgeGraph.astro, website/src/pages/graph.astro, .github/workflows/knowledge-website.yaml and website/scripts/raw-html.mjs here. No plugin change.

1.7.8

As it stood at this release: the repository · the docs · the knowledge bundle · the release

Security

  • The sidecar copies and the skills pin are at Knowledge Trust Ladder v0.55.0. The release changed .github/workflows/knowledge-registrar.yaml, .github/workflows/knowledge-release.yaml, .github/workflows/knowledge-sync.yaml, .lokf/scripts/knowledge-librarian.sh, .lokf/scripts/knowledge-conventions.sh, .lokf/scripts/knowledge-conventions.py, .lokf/scripts/knowledge-preflight.sh, .lokf/scripts/knowledge-provenance.sh, .lokf/scripts/knowledge-feedback.sh, .lokf/scripts/knowledge-apply.sh, .lokf/scripts/knowledge-apply.py, .lokf/scripts/knowledge-report.sh, .lokf/scripts/knowledge-sync.sh, .lokf/.gitignore, .lokf/justfile and website/src/components/KnowledgeGraph.astro here. No plugin change.

1.7.9

As it stood at this release: the repository · the docs · the knowledge bundle · the release

Security

  • The sidecar copies and the skills pin are at Knowledge Trust Ladder v0.55.2. The release changed .lokf/scripts/knowledge-preflight.sh and .lokf/scripts/knowledge-sync.sh here.

1.7.10

As it stood at this release: the repository · the docs · the knowledge bundle · the release

Security

  • The sidecar copies and the skills pin are at Knowledge Trust Ladder v0.56.1. The release changed .github/workflows/knowledge-registrar.yaml, .github/workflows/knowledge-librarian.yaml, .github/workflows/knowledge-release.yaml, .lokf/scripts/knowledge-preflight.sh, .lokf/scripts/knowledge-sync.sh, website/astro.config.mjs, website/scripts/check-links.mjs, website/scripts/config.mjs, website/scripts/markdown-ktl.mjs, website/scripts/raw-html.mjs, website/scripts/routes.mjs, website/scripts/sync.mjs, website/src/components/ConceptCard.astro, website/src/components/ConceptPreviews.astro, website/src/components/KnowledgeGraph.astro, website/src/components/Mermaid.astro, website/src/components/Neighbourhood.astro, website/src/components/TrustChart.astro, website/src/content.config.ts, website/src/pages/og/[...route].ts, website/src/styles/catalogue.css and .github/workflows/knowledge-website.yaml here. No plugin change.

1.7.11

As it stood at this release: the repository · the docs · the knowledge bundle · the release

Security

  • The sidecar copies and the skills pin are at Knowledge Trust Ladder v0.56.2. The release changed .lokf/.gitignore here. No plugin change.

1.7.12

As it stood at this release: the repository · the docs · the knowledge bundle · the release

Fixed

  • A ! after the type marks a breaking change. .releaserc.json names the Conventional Commits preset, so a feat!: commit releases a new major version instead of nothing. No plugin change.

1.7.13 Latest

As it stood at this release: the repository · the docs · the knowledge bundle · the release

Security

  • The sidecar copies and the skills pin are at Knowledge Trust Ladder v0.59.0. The release changed .github/workflows/knowledge-registrar.yaml, .github/workflows/knowledge-librarian.yaml, .github/workflows/knowledge-release.yaml, .github/workflows/knowledge-sync.yaml, .lokf/scripts/knowledge-conventions.sh, .lokf/scripts/knowledge-conventions.py, .lokf/scripts/knowledge-preflight.sh, .lokf/scripts/knowledge-apply.sh, .lokf/scripts/knowledge-apply.py, .lokf/scripts/knowledge-report.sh, .lokf/m365/ktl-docent-m365.md, website/package-lock.json, website/package.json, website/scripts/config.mjs and .github/workflows/knowledge-website.yaml here. No plugin change.