Differences

This shows you the differences between two versions of the page.

--- dido:99_annexes:annex-b-terms-and-definitions:i:image_baseline [2026/07/13 11:30] – created nick_dido
+++ dido:99_annexes:annex-b-terms-and-definitions:i:image_baseline [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 9: / Line 9: @@
 The Image Baseline may identify installation media, operating-system version, processor architecture, partitioning, filesystems, packages, provisioning roles, security settings, compliance profiles, source revisions, and build-tool versions.
-An Image Baseline defines how an image is reproduced. The resulting Machine Image is an artefact produced from that Baseline rather than the Baseline itself.
+An Image Baseline defines how an image is reproduced. The resulting Machine Image is an artifact produced from that Baseline rather than the Baseline itself.
 Within Crucible, an Image Baseline may serve as a source layer in a [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_composition|Baseline Composition]] and may support multiple provider-specific image realizations.
@@ Line 23: / Line 23: @@
 ===== Note =====
-An Image Baseline differs from a Machine Image. The Image Baseline defines the controlled configuration and process, while the Machine Image is a realized build artefact.
+An Image Baseline differs from a Machine Image. The Image Baseline defines the controlled configuration and process, while the Machine Image is a realized build artifact.
 Changes to operating-system media, packages, provisioning logic, hardening settings, or compliance settings may require a new Image Baseline.
@@ Line 29: / Line 29: @@
 ===== Example =====
-An Image Baseline identifies the RHEL 9 installation medium, required packages, Packer configuration, Ansible roles, STIG profile, remediation setting, processor architecture, and pinned source revisions used to produce a hardened guest image.
+An Image Baseline identifies the [[dido:99_annexes:annex-b-terms-and-definitions:r:rhel]] 9 installation medium, required packages, Packer configuration, Ansible roles, STIG profile, remediation setting, processor architecture, and pinned source revisions used to produce a hardened guest image.
 ----