lokf-librarian/references/domain-schema.md: how to extend the vocabulary into a domain - a LinkML schema importing a pinned lokf.yaml, --schema wired into the justfile and both workflows, both plugins’ Known LOKF types settings told, and what it leaves undone for the graph. The curator’s domain-schemas.md says when; this says how. Rule 3 now reads the host’s justfile for a --schema and counts that schema’s Concept descendants as vocabulary.
Fixed
Rule 3 in lokf-librarian/SKILL.md listed fourteen classes, omitting Role, while README.md and docs/for-the-curious.md said fifteen. Confirmed against the raw schema and corrected; the skills now teach one number.
Changed
The curator’s vocabulary-fit line respects a host’s domain schema. Where .lokf/justfile validates with --schema <slug>.yaml, trust-fields.md now has the skill read that file and count its Concept descendants as known - the same widening as Rule 3, so the line goes quiet once a team adopts a schema instead of naming every domain class a misfit. The label reads “doesn’t fit the known vocabulary”, matching the LOKF Curator plugin.
lokf-curator/references/review-session.md states how the curation-policy table is read: class names match ignoring spaces and plural form (“Glossary terms” is GlossaryTerm), and an unknown class binds nothing. Written down because the LOKF Curator plugin matched literally and so ignored four rows of this file’s own template.
README.md polished, not restructured. Each role and label is said once, the plugin table maps onto the four levels of checking, and the Obsidian section moves to docs/obsidian.md.
