Skip to main content

Aptlantis Archive Multi-Hash Standard (AAMHS)

AAMHS defines long-term archive verification and integrity validation for Aptlantis archival systems.

AAMHS is the preservation integrity standard. ARHS defines the minimum release-artifact hash set; AAMHS adds archive manifests, validation records, detached signature policy, and preservation notes.

:::info Status Candidate v1.0.3. :::

Document Suite​

FilePurpose
Aptlantis Archive Multi-Hash Standard.mdPrimary AAMHS specification wrapper.
AAMHS.manifest.tomlStandard manifest.
templates/Archive-Integrity-Record.mdArchive integrity record template.
templates/Hash-Manifest.tomlHash manifest template.
Adoption-Guide.mdAAMHS adoption procedure.
Validation-Checklist.mdArchive integrity checklist.
CHANGELOG.mdAAMHS version history.

Existing source material remains in references/APTlantis Release Hashing Standard.md, which is the same document that anchors the ARHS standard — see that page's note on the AAMHS/ARHS relationship.

SFDS Suite Model​

AAMHS.manifest.toml describes AAMHS as a standard suite. The templates in templates/ describe hash manifests and archive integrity records governed by AAMHS.

Scope​

AAMHS governs archive hash suites, manifest formats, detached signatures, validation procedures, and archival integrity records.

:::note Does Not Govern AAMHS does not govern UI design, project proposals, workspace root layout, or dataset licensing. :::

Required Archive Artifacts​

  • Hash manifest.
  • Archive integrity record.
  • Hash suite declaration.
  • Signature policy when signatures are used.
  • Validation procedure.
  • Preservation notes.

Relationship to ARHS​

ARHS defines the minimum hash requirements for release artifacts. AAMHS governs richer archive preservation records.

Use ARHS when publishing a release artifact. Use AAMHS when preserving archives, collections, datasets, evidence bundles, or release snapshots that need long-term verification, detached signatures, validation procedures, and preservation notes.

Hash Manifest Requirements​

AAMHS hash manifests should record:

  • Archive id and title.
  • Artifact filenames.
  • File sizes when known.
  • Hash suite used.
  • Hash values.
  • Hash generation date.
  • Tool names or commands.
  • Maintainer or operator.
  • Related release, dataset, or archive records.

Integrity Record Requirements​

An archive integrity record should answer:

  • What archive or collection is being preserved?
  • Which files are covered?
  • Which hash suite was used?
  • Were signatures used?
  • How can the archive be verified later?
  • What known gaps, missing files, or validation limits exist?

Signature Policy​

Detached signatures are optional unless required by the archive context. When signatures are used, the record must identify:

  • Signature file.
  • Signing tool.
  • Signing identity or key reference.
  • Verification procedure.
  • Trust limitations.

Validation Rules​

Validation must confirm:

  • Every listed file exists or is intentionally marked missing.
  • Every listed hash matches the file bytes.
  • The hash suite is declared.
  • Signature verification is documented when signatures are used.
  • Preservation notes identify known gaps or environmental assumptions.

Archive Blockers​

An archive is blocked from AAMHS-ready status when:

  • Hash manifest is missing.
  • Archive integrity record is missing.
  • Hash suite is not declared.
  • Listed files cannot be identified.
  • Any required hash mismatches.
  • Signature policy is unclear when signatures are claimed.
  • Preservation notes omit known gaps.