Skip to content
linkml-sidecar

Explanation

  • KTL mode checked by automation only, still a draft
    What changes when the host carries a .lokf/ Knowledge Trust Ladder bundle: the sidecar’s dummy schema becomes the bundle’s domain schema, and the scaffold pins .lokf/lokf.yaml, writes an ExampleConcept dummy, excuses LOKF’s camelCase slots in the linter and names the schema in .lokf/justfile and as [tool.lokf] schema; an adopted schema is not made the domain schema.

  • Three cases, one skill checked by automation only, still a draft
    Why there are three ways to give a repository a LinkML schema: a schema project runs copier at its root and needs no sidecar, a codebase whose maintainers do not want a schema project in their root folder gets the hidden .linkml/ sidecar around a dummy schema, and a repository holding a schema but no project gets the sidecar around that schema (–adopt).

  • Who owns which file nobody has checked this yet, still a draft
    Who owns each file in a .linkml/ sidecar (the template, the host or the skill) and how each changes, which template recipes never run, and how just update keeps a sidecar current.