ARHS Schema Reference
Standard Manifest
ARHS.manifest.toml declares ARHS as an active, candidate-maturity standard suite, its governance relationships, and the artifacts that make up the suite.
[standard]
id = "aptlantis-release-hashing-standard"
title = "APTlantis Release Hashing Standard"
abbreviation = "ARHS"
status = "active"
maturity = "candidate"
version = "0.2.1"
description = "Governs the required cryptographic hashes (SHA256, BLAKE3, KangarooTwelve) for all APTlantis release artifacts to ensure long-term integrity and cryptographic diversity."
[governance]
meta_standard = "SFDS"
workspace_standard = "WGS"
scope = "Required cryptographic hashes and verification records for APTlantis release artifacts."
non_goals = ["Archive preservation manifests", "project proposal creation", "release packaging procedure", "cryptographic signatures beyond future direction notes"]
[artifacts]
specification = "APTlantis Release Hashing Standard.md"
schema = "ReleaseHashRecord.schema.toml"
templates = "templates"
examples = "examples"
adoption_guide = "Adoption-Guide.md"
validation_checklist = "Validation-Checklist.md"
changelog = "CHANGELOG.md"
validators = []
governance_notes = []
reference_examples = ["examples/sample-hashes.txt", "examples/Example-Release-Hash-Record.md"]
[adopter_artifacts]
schemas = ["ReleaseHashRecord.schema.toml"]
manifest_templates = []
document_templates = ["templates/Release-Hash-Record.md"]
[lifecycle]
created = "2026-06-10"
last_updated = "2026-06-11"
maintainer = "Herb"
[agent]
read_first = ["APTlantis Release Hashing Standard.md", "ARHS.manifest.toml"]
notes = "Use ARHS for minimum release artifact hash requirements. Use AAMHS for archive preservation integrity records."
[standard]— identity, status, and version of ARHS.[governance]— relationship to SFDS and WGS, and explicit non-goals (notably, archive preservation manifests, which belong to AAMHS).[artifacts]— canonical suite files: specification, schema, templates, examples, adoption guide, checklist, and changelog.[adopter_artifacts]— what an adopting release pipeline actually uses: the schema and a document template.[lifecycle]— creation/update dates and maintainer.[agent]— read-order hint and a note distinguishing ARHS from AAMHS scope.
Release Hash Record Schema
ReleaseHashRecord.schema.toml defines the required shape of a release hash record.
title = "ARHS Release Hash Record Schema"
type = "object"
required = ["artifact", "governing_standards", "hashes", "verification"]
[properties.artifact]
required = ["name", "version", "size_bytes", "generated"]
[properties.governing_standards]
required = ["release_hashing"]
[properties.hashes]
required = ["sha256", "blake3", "kangaroo_twelve"]
[properties.commands]
type = "array"
[properties.verification]
required = ["verified_by", "verified_on", "result"]
artifact— identifies the release artifact: name, version, size in bytes, and generation date.governing_standards— names which standard governs release hashing for this record (ARHS), and optionally which govern packaging or archival.hashes— the three required hash values: SHA256, BLAKE3, and KangarooTwelve.commands— an array recording the exact commands used to generate or verify the hashes.verification— who verified the record, when, and the result.