ANCHORED LINEAGE RECEIPTS
Records derivation lineage — input hashes, transformation, output hash, and disclosure chain. The first family to deploy W3C Bitstring Status List 2021 for revocation. Anchors GPAI training-data provenance obligations under the EU AI Act.
WIRE TYPES
ar.lineage.v1 (derived_from)
Records that an artifact was derived from one or more parent artifacts. Each parent is identified by content hash and optionally by its APR or ALR receipt ID — building a verifiable DAG of data provenance.
ar.lineage.v1 (forked_from)
Records a new independent fork of an existing artifact. Starts a fresh chain head — the fork's history diverges from the parent while maintaining a verifiable link to its origin.
ar.lineage.v1 (superseded_by)
Records that an artifact has been replaced by a newer version. Flips the predecessor's Status List bit to revoked — linear supersession chain per artifact.
ar.lineage.v1 (disclosed)
Records a disclosure event in the artifact's lifecycle. Continues the per-artifact chain when disclosure is logged after creation or supersession — the cryptographic record of who received what, when.
WHAT IT PROVES
WHAT IT DOESN'T PROVE
COMPOSES WITH
ALR receipts reference other family members via body-level composition pointers — verifier-coordinated, not signature-mandated.
Lineage receipts can reference an APR as the origin anchor for a parent artifact — rooting derivation at an APR-anchored creation event.
ANR translation events may reference an ALR receipt for translation provenance — cross-checking that the ALR artifact_hash matches the ANR policy_hash.
DPIA receipts cite ALR receipts for data-flow lineage in scope of the impact assessment.
Verify any
ALR receipt.
Paste any claim ID to verify a receipt, check its anchor, and inspect the issuer signature.
REFERENCES
Anchored Lineage Receipts are cryptographic provenance and privacy-lifecycle protocols. verify.dekimu.com is a reference implementation, not a qualified trust service under Regulation (EU) No 910/2014 (eIDAS) or successor.