lokf toolkit (PyPI)
references/lokf-toolkitChecked by automation only
still a draft
Written 2026-10-29 by ktl-librarian (automation). Last checked 2026-10-16 by ktl-librarian (automation).
The full record
- Checks
- 2026-10-16 by
ktl-librarian(automation)
- 2026-10-16 by
- Sources
- Derived from
- Pointed to by
- In-editor aids (depends on)
- Knowledge registrar gate (depends on)
- Knowledge website (depends on)
- Graph
- Open this concept in the knowledge graph
- IRI
https://w3id.org/ktl/curator/knowledge/references/lokf-toolkit- Licence
- CC BY 4.0
- Files
- MarkdownJSON-LDSource on GitHubHistory on GitHub
.lokf/pyproject.toml declares the toolkit as lokf[build]>=0.9.0, and .lokf/uv.lock decides the version. From .lokf/, just lokf-validate runs lokf validate, which checks the bundle against the JSON Schema that the toolkit generates from the LOKF schema. just lokf-check-refs adds a check that every relation target in this bundle’s own namespace names a concept in it.
The plugin never imports Python or calls into this toolkit at runtime, and npm run build does not use it. One maintenance step does: scripts/build-vocab.mjs reads the LOKF schema, lokf.yaml, that the pinned toolkit includes, and writes src/lokf-vocab.json, the static manifest the plugin includes. Its header says to re-run it, and commit the result, when the pin moves.