Installation Manifest

There are two related manifest boundaries:

• The commercial package manifest identifies package version, installer/runtime revisions, image references, config schema version, upgrade baseline, migration expectations, installer commands, and SBOM inventory.
• The materialized edition manifest records edition identity, market profile, namespaces, source/file hashes, materializer version, and managed files without leaking an operator’s absolute source path.

The installer result also includes an application version, migration state, provider state, generated time, and checksum. These values identify the observed workflow; they do not replace database migration or health verification.

Verification

Compare the manifest to the authorized release metadata, verify checksums before use, and retain the redacted result with the installation record. Do not publish private image references or real release digests.