Sidecar
glossary/sidecarChecked by automation only
still a draft
Written 2026-10-13 by ktl-librarian (automation). Last checked 2026-10-29 by ktl-librarian (automation).
The .lokf/ folder beside a project's code, like .git/, which holds the bundle and the tooling that validates it and is kept out of the project's build. The ktl-sidecar skill, the first role to run, installs it from bundled templates.
The full record
- Checks
- 2026-10-29 by
ktl-librarian(automation)
- 2026-10-29 by
- Sources
- About
- Related to
- Pointed to by
- Doorway (related to)
- Graph
- Open this concept in the knowledge graph
- IRI
https://w3id.org/ktl/knowledge/glossary/sidecar- Licence
- CC BY 4.0
- Files
- MarkdownJSON-LDSource on GitHubHistory on GitHub
Overview
Section titled “Overview”The sidecar is .lokf/, a dot-folder beside a project’s code, like .git/, and kept out of the project’s build. The README it carries says it “does not touch the app build; it is independent tooling you can run on its own”. It holds the bundle at .lokf/knowledge/, the scripts that check and write the bundle, and their docs. A knowledge_bundle link beside it names the bundle for folder pickers that hide dot-folders.
The same word names the first role in the architecture page’s table, which lays the network, and the ktl-sidecar skill that plays it. The skill installs .lokf/ from bundled templates once, and later repairs a broken sidecar file.