Skip to Content
Adaptor Profiles

Adaptor Profiles

An adaptor profile binds the AHL Protocol to one class of transparency log. It states how a statement envelope becomes a leaf of that log, how checkpoints, inclusion and consistency proofs are shaped, what a witness cosigns, and which clauses of the protocol’s log contract (Protocol §3) the log class satisfies, meets only by deployment obligation, or does not meet.

A profile is identified by the pair { id, digest }. The digest is SHA-256 over the exact bytes of the released artifact, with no normalization of any kind. It is not written inside the artifact — it cannot be, since a digest embedded in a file would commit to the bytes that contain it — and lives in the corpus manifest (log.adaptor.hash) and in every Evidence Receipt (anchoring.adaptor.hash). A verifier recomputes it over the artifact it holds. Any change to a released profile, however small, is a different profile and MUST be published under a new id.

Released profiles

ahl-adaptor-atl-v1

Binds AHL to the Anchored Transparency Log (ATL) Protocol v2.0 . Revision 1, released 2026-09-06.

Verify the artifact you hold:

curl -sSO https://ahl-protocol.org/profiles/ahl-adaptor-atl-v1.md
shasum -a 256 ahl-adaptor-atl-v1.md
# 80a7defdd934242fb4986b2868f4553f0a245995c96ffe543baff59f6bb805aa

The same bytes ship inside ahl-core under test_data/profiles/, with a test that recomputes the digest, so a verifier built on the crate holds the artifact without fetching it.

The profile’s conformance statement (its §15) records, clause by clause, what ATL as published satisfies and what a deployment must add before claiming conformance: byte retrieval by entry id, authenticated enumeration, a checkpoint series, and an independent witness. The AHL reference stack serves those through ahl-mirror and ahl-witness.

Last updated on
Data StructuresOverview