Template assumptions catalogue
references/template-assumptionsNobody has checked this yet
still a draft
Written 2026-10-26 by ktl-librarian (automation).
The full record
- Checks
- none recorded
- Sources
- About
- Pointed to by
- Contributing (references)
- linkml-scaffold.sh (references)
- linkml-sidecar skill (references)
- linkml-sidecar workflow (references)
- Three cases, one skill (references)
- Who owns which file (references)
- Graph
- Open this concept in the knowledge graph
- IRI
https://w3id.org/ktl/linkml-sidecar/knowledge/references/template-assumptions- Licence
- CC BY 4.0
- Files
- MarkdownJSON-LDSource on GitHubHistory on GitHub
Overview
Section titled “Overview”skills/linkml-sidecar/references/template-assumptions.md is the catalogue the scaffold implements, row by row, at template v0.5.0. It is for whoever maintains the skill. Each row names one root-install assumption, what the skill does about it, and whether a layout: sidecar answer, proposed upstream in linkml-project-copier#187, would remove it.
Some of the rows:
just setuprunsgit init,git add .and a commit, so it is never run, and the scaffold fails if.linkml/.gitappears.just deploypushes the host’sgh-pagesbranch root, so it is never run; the Step 5 docs job publishes under thelinkml/subpath only.- The template’s workflows render inside the project, where GitHub never reads them, so a hoisted workflow runs the gate from the root.
- The upstream example fails
just lint, so the answer isadd_example: false, and a skill-owned dummy that lints clean takes its place. --trustis required, so the tag and its commit are verified before copier runs.config.public.mknames the schema, every recipe derives its paths from it, and upstream calls the file a convenience it may retire. Adoption pointsLINKML_SCHEMA_SOURCE_DIRat the host’s folder, and the preflight falls back to the answers’project_slugwhen the file is absent.config.yamlholds the generators’ settings andconfig.public.mknames it. A new sidecar renames itgenerators.yaml, and--repair generators.yamlmoves an existing project’s file. After the move,copier updateno longer carries the template’s changes to the settings.
Rows marked no are facts about LinkML, uv or git rather than about the template, and stay whatever upstream does. When the pin moves, bump the page’s heading and re-walk the rows.