Knowledge Registrar (knowledge-registrar.yaml)
workflows/knowledge-registrarChecked by automation only
still a draft
Written 2026-10-28 by ktl-librarian (automation). Last checked 2026-10-28 by ktl-librarian (automation).
The full record
- Checks
- 2026-10-28 by
ktl-librarian(automation)
- 2026-10-28 by
- Sources
- Pointed to by
- Security policy (references)
- Graph
- Open this concept in the knowledge graph
- IRI
https://w3id.org/lmodel/github-actions/knowledge/workflows/knowledge-registrar- Licence
- CC BY 4.0
- Files
- MarkdownJSON-LDSource on GitHubHistory on GitHub
Knowledge Registrar (knowledge-registrar.yaml)
Section titled “Knowledge Registrar (knowledge-registrar.yaml)”.github/workflows/knowledge-registrar.yaml is the workflow named “Knowledge Registrar”. A header comment says that it keeps the knowledge bundle’s records well formed, with their provenance recorded, and never judges whether their content is true, which is the curator’s job.1 NOTICE says that it is a copy of a ktl-sidecar template from the Knowledge Trust Ladder (KTL) repository.2 It runs on a pull request that touches .lokf/, knowledge_bundle/ or the workflow itself, every Monday at 06:00 UTC, and by hand.
None of its three jobs can write to the repository: each runs with a read-only token, keeps no credential on disk, and runs no LLM or agent.
validate, named “Validate the LOKF bundle”, runs every time, withcontents: read. It runsjust lokf-check-refs, which islokf validate --check-refswith the domain schema, and then the conventions script,.lokf/scripts/knowledge-conventions.sh.provenance, named “Check new human confirmations”, runs on pull requests, withcontents: readandpull-requests: read. For each new confirmation by a person in the diff, it passes when that person approved the pull request or signed the commit, as GitHub reports it, and otherwise calls the confirmation unbacked. With curators’ keys in.lokf/curators/, a second check verifies the same signatures with plain git.attestation, named “Attest to an unbacked confirmation”, runs only for an unbacked confirmation, with no token scope. It waits until a reviewer of the Environment that the repository variableKNOWLEDGE_CURATION_ENVIRONMENTnames approves the run, and the approval is logged with the run.
The header comment adds that the evidence is GitHub’s own record of approvals and signature checks, never the pull request’s text, and that the workflow does not prove that the named person read the source. CONTRIBUTING.md says that it runs on any .lokf/** change.