# Artifacts

The categorization of artifacts does not enforce anything on the structure of the associated files and key-value data. However, there must be some consistency and rules to be able to a make a meaningful use of the system.

The Available artifacts section documents the various categories that we use to manage a Debian-based distribution. For each category, we explain:

- what associated files you can find

- what key-value data you can expect

- what relationships with other artifacts are likely to exist

Data key names are used in `pydantic` models, and must therefore be valid Python identifiers.

See the explanation for an overview, and below for technical details.

- Relationships
- Available artifacts
  - Category `debian:autopkgtest`
  - Category `debian:binary-package`
  - Category `debian:binary-packages`
  - Category `debian:blhc`
  - Category `debian:debdiff`
  - Category `debian:lintian`
  - Category `debian:package-build-log`
  - Category `debian:piuparts`
  - Category `debian:repository-index`
  - Category `debusine:signing-input`
  - Category `debusine:signing-output`
  - Category `debian:source-package`
  - Category `debian:system-image`
    - `raw` image format
    - `qcow2` image format
  - Category `debian:system-tarball`
  - Category `debian:upload`
  - Category `debusine:work-request-debug-logs`