Skip to main content

APTlantis Release Hashing Standard Adoption Guide

When To Adopt​

Any project under APTlantis that produces software release artifacts, such as ISO images, archives, datasets, virtual machine images, and software collections.

Required Steps​

  1. Read the specification.
  2. Read ARHS.manifest.toml to understand the suite boundary.
  3. Integrate hashing steps into your CI/CD or build pipeline to generate SHA256, BLAKE3, and KangarooTwelve hashes for all release artifacts.
  4. Publish the hashes alongside the release artifacts.
  5. Run or complete validation to ensure all three hashes are present and accurate.
  6. Record known gaps (e.g. lack of tooling for a specific environment).
  7. Ensure the release document and hash record name the same final artifact.
  8. Use AAMHS when the artifact is being preserved as part of a long-term archive.

Manifest Model​

ARHS.manifest.toml describes this standard. Adopter manifests, schemas, and document templates describe the projects or artifacts governed by this standard.