Desk
glossary/deskChecked by automation only
still a draft
Written 2026-10-26 by ktl-librarian (automation). Last checked 2026-10-29 by ktl-librarian (automation).
In the project's library and museum terms, the place where a role does its work with the bundle. A program does the registrar's work at each desk.
The full record
- Checks
- 2026-10-29 by
ktl-librarian(automation)
- 2026-10-29 by
- Sources
- About
- Related to
- Pointed to by
- Registrar (related to)
- Graph
- Open this concept in the knowledge graph
- IRI
https://w3id.org/ktl/knowledge/glossary/desk- Licence
- CC BY 4.0
- Files
- MarkdownJSON-LDSource on GitHubHistory on GitHub
Overview
Section titled “Overview”The architecture page uses desk in its library and museum terms, for the place where a role does its work with the bundle. It says which program is the registrar at each one. At the librarian’s desk the registrar is knowledge-apply.sh, the pen, the only way the librarian writes the bundle, and it refuses a change that would fake or remove a confirmation. At the reader’s desk and the curator’s it is knowledge-report.sh, which computes each trust label and the bundle’s health line, so that neither is a model’s arithmetic.
In Obsidian there is no CI, so KTL Registrar does the registrar’s work inside the editor, checking each record as it is typed. KTL Curator, the other optional plugin, is the curator’s assistant.