Dekimu · anchored receipts docs
ALR — Anchored Lineage Receipts
Cryptographic proof of data lineage — derivation, fork, supersession, or disclosure of an artifact.
Purpose
An ALR records the provenance graph of a dataset or artifact: where it came from, what it spawned, whether it has been superseded, and to whom it has been disclosed. Receipts chain together to form a cryptographically verifiable directed acyclic graph (DAG) of data ancestry.
ALR is the first anchors family to deploy W3C Bitstring Status List 2021 (§4.5 reference implementation), allowing individual lineage receipts to be revoked without breaking the chain structure.
Event types
| Kind | Label | Description |
|---|---|---|
derived_from | Derived | New dataset created from source. |
forked_from | Forked | Independent copy created. |
superseded_by | Superseded | Newer version replaces this artifact. |
disclosed | Disclosed | Data shared with external recipient. |
Key fields
parents — array of parent artifact references, each with an artifact hash and optional claim ID. Forms the backward edge of the lineage DAG.
successor — reference to the artifact that supersedes this one (populated only on superseded_by events).
disclosure_recipients — structured list of recipients for disclosed events, including recipient identity, transfer mechanism, and timestamp.
Regulatory context
ALR receipts support the record-of-processing obligations under GDPR Art. 30, which requires controllers to maintain records of all data processing activities including transfers and disclosures. Art. 15(1)(c) grants data subjects the right to know the recipients or categories of recipients to whom their data has been disclosed — ALR's disclosed event type provides the cryptographic evidence for that response.