What changed in the knowledge bundle, a day to an entry, newest first. https://w3id.org/lmodel/github-actions/knowledge/log 2026-10-30T15:51:21Z Noel McLoughlin CC BY 4.0 https://w3id.org/lmodel/github-actions/knowledge/log#2026-10-30 2026-10-30T15:51:21Z 2026-10-30T15:51:21Z <ul> <li><strong>Changed</strong>: the export script prints an organization's rulesets with <code>rulesets --organization</code>.</li> <li><strong>Changed</strong>: SECURITY.md names the ruleset that holds <code>main</code>.</li> </ul> https://w3id.org/lmodel/github-actions/knowledge/log#2026-10-29 2026-10-29T01:12:54Z 2026-10-29T17:19:18Z <ul> <li><strong>Prose</strong>: reworded 2 concept bodies in plain English. No fact, link, number or frontmatter changed.</li> <li><strong>Changed</strong>: Derive and check concepts from workflow files, Test data and Required status check say that a job's <code>needs</code> is a skip condition and <code>if: always()</code> is not, and count twenty-four derive.py tests.</li> <li><strong>Changed</strong>: Knowledge sources map adds <code>scripts/github_export.py</code> and its tests to the derive.py row.</li> <li><strong>Changed</strong>: Test data counts twenty-one derive.py tests and adds the export script's tests and the two export files.</li> <li><strong>Changed</strong>: Required status check says which skips let a required check pass and which leave it pending, as the schema's comment now does.</li> <li><strong>Changed</strong>: Derive and check concepts from workflow files covers github_export.py, --rulesets, --check-runs, the skip-condition rule and checks another app reports.</li> <li><strong>Prose</strong>: reworded 5 concept bodies in plain English. No fact, link, number or frontmatter changed.</li> <li><strong>Changed</strong>: Derive and check concepts from workflow files says that <code>CHANGELOG.md</code> lists the script under 0.1.0, since that release promoted the section.</li> <li><strong>Changed</strong>: github-actions documentation site drops the conditions that held before the repository was public and 0.1.0 was released, and names the log's Atom feed that <code>website/README.md</code> lists.</li> <li><strong>Changed</strong>: Test data and schema tests gets back the two sources the last patch dropped: CONTRIBUTING.md's rule on example data and <code>examples/README.md</code>, which says that <code>examples/output/</code> is ignored.</li> </ul> https://w3id.org/lmodel/github-actions/knowledge/log#2026-10-28 2026-10-28T19:14:45Z 2026-10-28T22:46:33Z <ul> <li><strong>Changed</strong>: Scope, influences and mappings now says that the rules module declares the <code>in_toto:</code> prefix and names the Test Result predicate by a CURIE, as cd7488c made it.</li> <li><strong>Changed</strong>: Test data and schema tests now counts eight schema tests, including the new check that every mapping in the adapt copy uses a bound prefix, and says that the slsa neighbour is slsa's v0.7.0 release asset.</li> <li><strong>Changed</strong>: Workflow syntax, Metadata syntax, REST API rules and check runs, and GitHub Actions build type now cite the README's What it models section for each page, since <code>docs/about.md</code> no longer lists the model's sources.</li> <li><strong>Rewrite</strong>: Scope, influences and mappings follows the README's shorter sections; it drops the claims no source now makes, that no single specification stands behind the model and that the mapped vocabularies did not shape it.</li> <li><strong>Changed</strong>: Element names cites the naming paragraph of <code>docs/about.md</code> at its new place, and takes the rule for a renamed key from that page, which the README now points to.</li> <li><strong>Changed</strong>: SchemaStore copy no longer calls the two files a machine-readable form, a phrase the README dropped.</li> <li><strong>Changed</strong>: Security policy follows SECURITY.md's renamed section, What this repository releases, and its wording on staying below 1.0.</li> <li><strong>Changed</strong>: Derive and check follows the README's reworded Deriving section and SECURITY.md's renamed section.</li> <li><strong>Changed</strong>: Required status check no longer says that none of GitHub's pages states the called-job rule, a claim the README dropped.</li> <li><strong>Changed</strong>: Knowledge Release cites CONTRIBUTING.md for when a release carries the schema copy, since the README now points there.</li> <li><strong>Changed</strong>: Release the schema follows CONTRIBUTING.md's wording on which commit types start a release.</li> <li><strong>Changed</strong>: github-actions LinkML schema records that <code>LINKML_SCHEMA_NAME</code> in <code>config.public.mk</code> names the umbrella file, as the schema directory's README now says.</li> <li><strong>Prose</strong>: reworded 2 more concept bodies, cutting phrases that carried no fact. No fact, link, number or frontmatter changed.</li> <li><strong>Prose</strong>: reworded 16 concept bodies in plain English. No fact, link, number or frontmatter changed.</li> <li><strong>Added</strong>: Derive and check concepts from workflow files, from <code>scripts/derive.py</code>, its tests and the README's section on it, which d38a5e0 added.</li> <li><strong>Changed</strong>: the test data concept gives the naming rule as <code>ClassName-###.yaml</code>, as <code>tests/data/README.md</code> has since a86d859, and names <code>tests/test_derive.py</code> and its fixtures, which d38a5e0 added.</li> <li><strong>Changed</strong>: the security policy names both scripts under <code>scripts/</code>, says that <code>scripts/derive.py</code> runs in no workflow here, and words the librarian's row as <code>SECURITY.md</code> has since a86d859 and d38a5e0.</li> <li><strong>Changed</strong>: the schema concept says when the knowledge release attaches the adapt copy, as the README's Knowledge Trust Ladder (KTL) section has since a86d859.</li> <li><strong>Changed</strong>: the knowledge release concept says that the README and CONTRIBUTING.md now agree with the workflow on when the schema copy is attached, since a86d859.</li> <li><strong>Resolved</strong>: README.md and CONTRIBUTING.md say since a86d859 that the knowledge release attaches the schema copy when the bundle has changed, and that a run with <code>force</code> attaches it otherwise.</li> <li><strong>Changed</strong>: the librarian workflow concept says that the skills pin stays at v0.57.0 until the first weekly sync moves it, as <code>CHANGELOG.md</code> has since a86d859.</li> <li><strong>Resolved</strong>: CHANGELOG.md says since a86d859 that the v0.58.0 templates leave the skills pin at v0.57.0 and that the first weekly sync moves it.</li> <li><strong>Changed</strong>: the release playbook says when the knowledge release attaches the schema copy, and to run it with <code>force</code> when only the schema changed, as CONTRIBUTING.md's Releasing section has since a86d859.</li> <li><strong>Changed</strong>: the required status check term adds the details of the naming rule that <code>scripts/derive.py</code> states, from d38a5e0.</li> <li><strong>Changed</strong>: the source map adds <code>scripts/derive.py</code>, its fixtures and tests, and the README's section on it, and names the derivation check as a way to re-check the workflow concepts.</li> <li><strong>Added</strong>: github-actions LinkML schema, from <code>src/github_actions/schema/github_actions.yaml</code>.</li> <li><strong>Added</strong>: SchemaStore copy, from <code>src/github_actions/schema/schemastore</code>.</li> <li><strong>Added</strong>: Generated artefacts, from <code>project</code>.</li> <li><strong>Added</strong>: Test data and schema tests, from <code>tests/data</code>.</li> <li><strong>Added</strong>: GitHub workflow syntax, from <code>https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax</code>.</li> <li><strong>Added</strong>: GitHub metadata syntax, from <code>https://docs.github.com/en/actions/reference/workflows-and-actions/metadata-syntax</code>.</li> <li><strong>Added</strong>: GitHub REST API rules and check runs, from <code>https://docs.github.com/en/rest/repos/rules</code>.</li> <li><strong>Added</strong>: GitHub Actions build type, from <code>https://actions.github.io/buildtypes/workflow/v1</code>.</li> <li><strong>Added</strong>: Required status check, from <code>src/github_actions/schema/github_actions_rules.yaml</code>.</li> <li><strong>Added</strong>: Repository ruleset, from <code>src/github_actions/schema/github_actions_rules.yaml</code>.</li> <li><strong>Added</strong>: Reusable workflow, from <code>src/github_actions/schema/github_actions_workflow.yaml</code>.</li> <li><strong>Added</strong>: GITHUB_TOKEN permission, from <code>src/github_actions/schema/github_actions_workflow.yaml</code>.</li> <li><strong>Added</strong>: Element names and the shared namespace, from <code>docs/about.md</code>.</li> <li><strong>Added</strong>: Scope, influences and mappings, from <code>README.md</code>.</li> <li><strong>Added</strong>: Regenerate and test the schema, from <code>CONTRIBUTING.md</code>.</li> <li><strong>Added</strong>: Release the schema, from <code>CONTRIBUTING.md</code>.</li> <li><strong>Added</strong>: Validate data against the schema, from <code>docs/index.md</code>.</li> <li><strong>Added</strong>: Move the upstream pins, from <code>scripts/check_upstream_release.py</code>.</li> <li><strong>Added</strong>: github-actions documentation site, from <code>website</code>.</li> <li><strong>Added</strong>: License and attribution, from <code>NOTICE</code>.</li> <li><strong>Added</strong>: Security policy, from <code>SECURITY.md</code>.</li> <li><strong>Added</strong>: AI covenant, from <code>AI_COVENANT.md</code>.</li> <li><strong>Added</strong>: Build and test (main.yaml), from <code>.github/workflows/main.yaml</code>.</li> <li><strong>Added</strong>: Lint &amp; docs (lint-and-docs.yaml), from <code>.github/workflows/lint-and-docs.yaml</code>.</li> <li><strong>Added</strong>: Semantic release (semantic-release.yml), from <code>.github/workflows/semantic-release.yml</code>.</li> <li><strong>Added</strong>: Upstream watch (upstream-watch.yaml), from <code>.github/workflows/upstream-watch.yaml</code>.</li> <li><strong>Added</strong>: Knowledge website (knowledge-website.yaml), from <code>.github/workflows/knowledge-website.yaml</code>.</li> <li><strong>Added</strong>: Knowledge Registrar (knowledge-registrar.yaml), from <code>.github/workflows/knowledge-registrar.yaml</code>.</li> <li><strong>Added</strong>: Knowledge Librarian (knowledge-librarian.yaml), from <code>.github/workflows/knowledge-librarian.yaml</code>.</li> <li><strong>Added</strong>: Knowledge Release (knowledge-release.yaml), from <code>.github/workflows/knowledge-release.yaml</code>.</li> <li><strong>Added</strong>: Knowledge sync (knowledge-sync.yaml), from <code>.github/workflows/knowledge-sync.yaml</code>.</li> <li><strong>Added</strong>: Knowledge sources map, which lists every repository path and page this bundle derives from, how to re-check each, and the paths left out and why.</li> <li><strong>Open question</strong>: Knowledge Release (knowledge-release.yaml): README.md says that each release attaches the schema copy as <code>schema-&lt;tag&gt;-github-actions.yaml</code>, and CONTRIBUTING.md and CHANGELOG.md say the same, but knowledge-release.yaml packs the domain schema only when the bundle's tree differs from the newest earlier release that carries a bundle, or when force is set. Should a release whose bundle is unchanged still carry the schema copy, or should the README say when it does?</li> <li><strong>Open question</strong>: Knowledge Librarian (knowledge-librarian.yaml): CHANGELOG.md says that the sidecar automation comes from the KTL v0.58.0 templates, and CONTRIBUTING.md says that the skills pin moves with the sidecar copies, but knowledge-librarian.yaml sets TRUST_LADDER_SKILLS_REF to v0.57.0. Which release should the scheduled librarian install?</li> <li><strong>Removal</strong>: Example Service A and Example Service B, the sidecar's placeholders, now that real concepts describe the repository.</li> <li><strong>Initialization</strong>: Scaffolded the LOKF bundle for github-actions with placeholder services. Real concepts to follow.</li> </ul>