Skip to content
KTL Federation

All versions since 0.2.6

All versions

0.2.6

Security

  • The sidecar copies and the skills pin are at Knowledge Trust Ladder v0.48.0. The release changed .github/workflows/knowledge-registrar.yaml, .github/workflows/knowledge-federation.yaml, .github/PULL_REQUEST_TEMPLATE/knowledge-sync.md, .lokf/scripts/knowledge-report.sh, .lokf/scripts/knowledge-federate.py and .lokf/domain.yaml here.

0.3.0

Changed

  • The domain concept is domains/ktl-federation, named for the domain rather than its position. The workspace index and every member’s isPartOf name the new id, and the domain waits for a confirmation of its own.

0.4.0

Changed

  • The members name their newest bundle releases: Knowledge Trust Ladder v0.49.0, AI-LinkMO v0.4.9 and gist v0.3.7. Each zip’s checksum and attestation were verified, and each move waits for a person’s confirmation.

0.5.0

Added

  • KTL Curator 1.6.4 and KTL Registrar 1.7.5 join the domain as members. Each zip’s checksum and attestation were verified, and a person’s confirmation admits each one.

Changed

  • The federation policy states the value test and the diamond rule. No admission condition changed.

0.6.0

Fixed

  • The pages say when a member joins the workspace. The architecture and curation pages and the figure said a release changes nothing until a person confirms it. The build takes every member concept on the default branch, so a release joins when its pull request merges, and the confirmation records that it belongs.

0.6.1

Fixed

  • The build takes each member as a person last confirmed it. It built every member concept at the tag, as the 0.6.0 pages said, so a merged move or a new member joined the workspace before anyone confirmed it. A moved member is now built at its confirmed release while that confirmation stands, and a new one waits outside until confirmed. The domain’s own gate policy and depth count only as confirmed too, and the pages and the figure say so again.

0.6.2

Security

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

0.7.0

Changed

  • The domain concept says a member is a MemberBundle or a MemberDomain, as the architecture page does. A person corrected it and confirmed it against that page’s latest edits.

0.8.0

Changed

  • The Knowledge Trust Ladder member names its v0.50.1 bundle release. The zip’s checksum and attestation were verified, and a person confirmed the move.

0.8.1

Security

  • The sidecar copies and the skills pin are at Knowledge Trust Ladder v0.52.0. The release changed .github/workflows/knowledge-federation.yaml, .lokf/scripts/knowledge-conventions.sh, .lokf/scripts/knowledge-conventions.py, .lokf/scripts/knowledge-report.sh, .lokf/scripts/knowledge-federate.py and .lokf/domain.yaml here.

0.9.0

Changed

  • The federation policy’s diamond rule says the build stays stopped until both owners pin one release, as KTL’s federation page now says.

0.10.0

Changed

  • The Knowledge Trust Ladder, AI-LinkMO and gist members name their v0.52.0, v0.4.10 and v0.3.10 bundle releases. Each zip’s checksum and attestation were verified, and a person confirmed each move.

0.10.1

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-federation.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-federate.py, .lokf/scripts/knowledge-sync.sh, .lokf/domain.yaml, .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.

0.11.0

Changed

  • The graph page’s full screen keeps the graph at full height and stays on when the view changes, and its filters show counts, All and None, and how many concepts are shown. The component is ahead of the skills pin until Knowledge Trust Ladder releases the same change.

0.11.1

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-federation.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-federate.py, .lokf/scripts/knowledge-sync.sh, .lokf/domain.yaml, .lokf/.gitignore and .lokf/justfile here.

0.12.0

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

Added

  • The linkml-sidecar bundle is a member at its v0.0.1 release. Its zip’s checksum and attestation were verified, and a person confirmed it under the admission rule.

Changed

  • The Knowledge Trust Ladder member names its v0.55.0 bundle release. The zip’s checksum and attestation were verified, and a person confirmed the move.

0.12.1

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, .lokf/scripts/knowledge-sync.sh, website/package-lock.json and website/package.json here.

0.12.2

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

Security

  • .lokf/uv.lock pins certifi 2026.10.23. Earlier releases bundle emSign root certificates whose intermediate keys were compromised (GHSA-6q48-6c7w-9gw2), which the lokf toolkit trusts through requests.

0.12.3

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, .github/workflows/knowledge-federation.yaml, .github/workflows/knowledge-sync.yaml, .lokf/scripts/knowledge-preflight.sh, .lokf/scripts/knowledge-federate.py, .lokf/scripts/knowledge-sync.sh, website/astro.config.mjs, website/package-lock.json, website/package.json, 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.

0.13.0

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

Added

  • The bundle gains concepts for confirming a member change, the workspace and the domain schema, playbooks for contributing, releasing and the website, and a map of its sources. Each is a draft until a person confirms it.

Changed

  • The gist, Knowledge Trust Ladder, linkml-sidecar, KTL Curator and KTL Registrar members name their v0.3.13, v0.56.1, v0.3.2, 1.6.9 and 1.7.10 bundle releases, and linkml-sidecar’s namespace moves to https://w3id.org/ktl/linkml-sidecar/knowledge/. Each zip’s checksum and attestation were verified, and a person confirmed each move.
  • The domain concept reads in plain English, and states the fail rule, max_depth, sensitivity and private_addresses as .lokf/domain.yaml defines them. A person corrected it and confirmed it.

0.13.1

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/scripts/knowledge-federate.py and .lokf/.gitignore here.

0.14.0

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

Changed

  • The domain concept says that a Domain carries unowned_targets, max_depth, sensitivity and private_addresses, and that a file that fails a check stops the job and the old snapshot stays. A person corrected it, and it waits for a confirmation.
  • The federation policy is a draft again. A person sent it back for the librarian to review against its sources.

0.14.1

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.57.0. The release changed .github/workflows/knowledge-registrar.yaml, .github/workflows/knowledge-librarian.yaml, .github/workflows/knowledge-release.yaml, .github/workflows/knowledge-federation.yaml, .github/workflows/knowledge-sync.yaml, .lokf/scripts/knowledge-preflight.sh, .lokf/scripts/knowledge-apply.py, .lokf/scripts/knowledge-federate.py, website/package-lock.json, website/package.json, website/scripts/config.mjs and .github/workflows/knowledge-website.yaml here.

0.14.2

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-federation.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/scripts/knowledge-federate.py, .lokf/m365/ktl-docent-m365.md and .github/workflows/knowledge-website.yaml here.

0.14.3 Latest

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

Changed

  • The .lokf toolkit floor is lokf 0.9.0, and .lokf/lokf.yaml is its schema. Knowledge Trust Ladder’s recipes from v0.60.0 pass --schema to convert and serve and --check-excerpts to check-refs, which lokf 0.8.0 lacks. lokf 0.9.0 reads a bare-date stale_after as a datetime, which the 0.8.0 copy rejected.
  • A member names its checksum as LOKF core’s Checksum, {algorithm: sha256, checksum_value: <hex>}, with the same digest. The domain schema’s own string checksum clashed with lokf 0.9.0’s, so lokf convert --schema failed and a core export wrote each digest as an IRI; .lokf/domain.yaml and knowledge-federate.py come from Knowledge Trust Ladder’s fix/domain-host-lokf-0-9-0 ahead of its release, the schema takes sha256 alone, and the script reads both forms.
  • The federation check runs on a pull request that changes .lokf/lokf.yaml or .lokf/justfile. It validates against the schema the justfile names, which imports that copy of LOKF core.