Skip to content
Knowledge Trust Ladder

Trust label

Glossary termreferenceglossary/trust-label

Edited since a person last confirmed it (confirmed 2026-10-19, edited 2026-10-29)

Written 2026-10-29 by ktl-librarian (automation). Last checked 2026-10-19 by noelmcloughlin (a person).

The plain-language phrase a skill uses for how far a concept has been checked - "confirmed by a person", "checked by automation only", "nobody has checked this yet" - derived from frontmatter, never stored.

The full record
Checks
  • 2026-10-28 by ktl-librarian (automation)
  • 2026-10-13 by noelmcloughlin (a person)
  • 2026-10-19 by noelmcloughlin (a person)
Review by
2027-10-19
Sources
References
About
Pointed to by
Graph
Open this concept in the knowledge graph
IRI
https://w3id.org/ktl/knowledge/glossary/trust-label
Licence
CC BY 4.0
Files
MarkdownJSON-LDSource on GitHubHistory on GitHub

Overview

Section titled “Overview”

The labels restate OKF v0.2 section 5’s trust fields in words a non-specialist can act on. knowledge-report.sh computes them each time from verified, status, generated.at and stale_after. It also uses the relation fields for reliance. It computes each label except two, which are both worked out by hand: doesn’t fit the known vocabulary and not tied to a signed commit.

  • Any verified actor prefixed human: means confirmed by a person.
  • Events by non-human actors alone mean checked by automation.
  • No verified key, or one with no events, means nobody has checked it.
  • status: draft with no human: verified event means still a draft.
  • status: draft with a human: verified event means reopened: the pen’s question and the curator’s send-back set it. The label gives the earliest open question asked on or after the confirmation’s day, its asker, and how many wait. The confirmation still counts as one, so the rung stays.

knowledge-report.sh reads resource, sources[].resource and git history for the label a source moved since the confirmation.

It reads .lokf/feedback.md for the label a reader disputed this: a waiting **Disagreement** that names the concept, never on a retired concept. It reads the newest **Deprecation** line in log.md for the successor a retired concept names. It reads derivedFrom for the label derived from a concept edited since its confirmation.

A revision on an event (lokf 0.9.0 and later) is shown beside that event’s date but changes no label: its absence means unrecorded, never unchanged.

The labels overlap. A concept can be confirmed and past its review date, so the counts in a curator report are not a partition. One pair never overlaps: a concept edited since its confirmation is counted under edited since confirmed and not as confirmed, because the person confirmed an earlier text. Nothing is scored and nothing is stored: the spec keeps scores out of frontmatter.

A question asked after a confirmation reopens a concept and flags what waits. It never drops the rung: only an edit after the confirmation does that. The health line counts the two apart since 0.45.0: Drafts for a concept no person has confirmed, and Reopened for one a person confirmed and a question has since put back to status: draft.