Skip to content

References

  • LOKF specification checked by automation only, still a draft
    The Linked Open Knowledge Format specification - the semantic profile of OKF this plugin’s trust labels and typed relations are defined against.

  • lokf toolkit (PyPI) checked by automation only, still a draft
    The Python package that this repository’s own .lokf/ sidecar uses to validate the bundle, check its relation targets and convert it to RDF. The plugin never uses it at runtime, and only the scripts/build-vocab.mjs maintenance step reads its schema.

  • Obsidian plugin developer guidelines checked by automation only, still a draft
    The platform API surface and review guidelines this plugin is built against - declarative settings (1.13+), processFrontMatter, metadataCache, and the eslint-plugin-obsidianmd ruleset that encodes them.

  • OKF v0.2 specification checked by automation only, still a draft
    The Open Knowledge Format specification LOKF profiles - one concept per Markdown file, provenance/trust/lifecycle fields, permissive consumption.

  • Review session (ktl-curator skill) checked by automation only, still a draft
    The exact frontmatter/body edit for each of the five verbs, the log.md line format, and the curation-policy and missing-placeholder templates - the spec of record edits-engine.md implements.

  • Trust fields (ktl-curator skill) checked by automation only, still a draft
    The exact rule for each plain-language trust label: the spec of record that trust-engine.md implements, and the source that the health-line chips in docs/using.md and the label table in docs/for-the-curious.md summarize.