---
type: Dataset
id: https://w3id.org/lmodel/slsa/knowledge/datasets/generated-artefacts
genre: reference
title: Generated artifacts
description: "Files generated from the slsa schema and never edited by hand, committed or git-ignored: the two merged schemas in docs/schema/, the Python data models, project/ (JSON Schema, OWL, SHACL, Java and more), docs/elements/ and the bundle's domain schema .lokf/slsa.yaml, which a release also attaches as its schema asset."
resource: project/
sources:
  - resource: justfile
    title: the gen-project, gen-python and gen-doc recipes
  - resource: project.justfile
    title: the gen-merged and lokf-adapt recipes
  - resource: .linkml/generators.yaml
    title: the gen-project generator settings
  - resource: src/slsa/datamodel/
    title: the generated Python data models
  - resource: docs/schema/
    title: the merged schemas
  - resource: CONTRIBUTING.md
    title: the list of generated files
  - resource: .github/workflows/main.yaml
    title: the comment on the adapted schema copy check
  - resource: .github/workflows/knowledge-release.yaml
    title: the comparison with the last released bundle and the Pack the domain schema step
derivedFrom:
  - https://w3id.org/lmodel/slsa/knowledge/datasets/slsa-linkml-schema
generated:
  by: process:ktl-librarian
  at: "2026-10-30T23:20:11Z"
status: draft
verified:
  - by: process:ktl-librarian
    at: "2026-10-27T12:57:54Z"
references:
  - https://w3id.org/lmodel/slsa/knowledge/playbooks/release
---

# Generated artifacts

The recipes in `justfile` and `project.justfile` generate these from `src/slsa/schema/slsa.yaml` and the modules it imports:

- **`project/`**, by `just gen-project`: Excel, GraphQL, Java, JSON-LD, JSON Schema, OWL, prefix map, Protobuf, SHACL, ShEx, SQL schema and TypeScript. `.linkml/generators.yaml`, which `config.public.mk` names, sets the generator options and excludes the Markdown generator.
- **`src/slsa/datamodel/slsa.py` and `slsa_pydantic.py`**, by `just gen-project` or `just gen-python`: the dataclass and Pydantic models.
- **`docs/schema/slsa.yaml`**, by `just gen-doc` through its `_gen-yaml` step: the schema written by `gen-yaml`. `project.justfile` says that it holds the modules' elements folded in but keeps the `imports:` list, so a tool that loads it looks for the modules beside it.
- **`docs/schema/slsa_merged.yaml`**, by `just gen-merged`, run after `gen-doc`: the same schema with no imports, written by `gen-linkml --mergeimports`, for vendoring or loading offline.
- **`docs/elements/*.md`**, by `just gen-doc`: the per-element documentation pages, which `.gitignore` excludes.
- **`.lokf/slsa.yaml`**, by `just lokf-adapt`: the bundle's domain schema, which `lokf adapt` writes from the schema, and the release's schema asset. See [slsa LinkML schema](slsa-linkml-schema.md).

The README marks `project/` as auto-generated and not to be edited. `CONTRIBUTING.md` names `project/`, `src/slsa/datamodel/`, `docs/schema/` and `.lokf/slsa.yaml` as generated.

## The domain schema in a release

A comment in `.github/workflows/main.yaml` says that the knowledge bundle validates against `.lokf/slsa.yaml` and that the release attaches it, so the copy must match the schema and `.lokf/lokf.yaml`. On Python 3.13, the build checks that it does.

`.github/workflows/knowledge-release.yaml` attaches the copy to a release beside the bundle's zip file, as `schema-<tag>-<name>.yaml` with its own `.sha256` file. `<name>` is the repository's name unless the `KNOWLEDGE_RELEASE_NAME` repository variable gives another. The workflow attaches nothing when three things match the newest other published release that carries a bundle:

- the bundle's git tree;
- the `schema :=` line of `.lokf/justfile`;
- the schema's files: the file that line names, and the local files it imports in turn, apart from `lokf.yaml`.

A manual run that sets `force` skips the comparison. [Release the slsa package](../playbooks/release.md) says when the workflow runs.

The released copy must import LOKF core by the name `lokf`. The step that packs it rewrites a relative import of `.lokf/lokf.yaml` to that name, and merges into the copy any other local file the schema imports. `.lokf/slsa.yaml` imports only `linkml:types` and `lokf`, so the step attaches it as it is. The job that uploads the files checks each against its checksum, and in a public repository it attests the build provenance of the zip and the schema file.