Skip to content
KTL Federation

All versions since 0.14.2

All versions

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.