ANCHORED DELEGATION RECEIPTS

Anchored Delegation Receipts

Records that a principal delegated a bounded authority to an agent — controller-to-processor instructions, AI deployer mandates, EUDI Wallet powers of representation, and DSA legal-representative chains. Scope-subset enforcement: each delegation verifies it is within the parent's scope.

ADR · Shipped6 wire typesApache-2.0 · CC0 spec
← All familiesVerify a receipt →

WIRE TYPES

ar.delegation.v1 (delegation.granted)

Records the grant of a bounded authority — the scope, conditions, expiry, and whether the delegation is itself delegable (sub-delegation tree). Chain head for the authority lifecycle.

ar.delegation.v1 (delegation.revoked)

Records revocation of a previously granted delegation. Cascading — revoking a parent grant revokes all descendants in the sub-delegation tree. Terminal event.

ar.delegation.v1 (delegation.suspended)

Records temporary suspension of a delegation. Reversible — the suspended_until field declares the expected resumption. No Status List flip (suspension is not revocation).

ar.delegation.v1 (delegation.reinstated)

Records reinstatement of a previously suspended delegation.

ar.delegation.v1 (delegation.scope_amended)

Records a narrowing of the delegation scope. The predecessor's Status List bit flips to revoked (the narrowed grant supersedes the original).

ar.delegation.v1 (delegation.expired)

Records natural expiry of a delegation. The verifier checks expiry against the original grant's validity window.

WHAT IT PROVES

  • — A delegation was granted before processing began (Merkle inclusion proof).
  • — The scope of authority — what the delegate is authorised to do (scope fields).
  • — Revocation cascades through the sub-delegation tree (tree walk).
  • — The complete delegation lifecycle — from grant through amendment, suspension, or revocation (chain walk).

WHAT IT DOESN'T PROVE

  • — The delegate actually respected the scope constraints.
  • — The principal had the authority to delegate in the first place.
  • — Sub-processors were properly audited.
  • — The delegation terms were fair or balanced.

COMPOSES WITH

ADR receipts reference other family members via body-level composition pointers — verifier-coordinated, not signature-mandated.

ATRAnchored Transfer Receipts

Processor-to-sub-processor transfers may reference an ADR grant for the upstream authority.

ANRAnchored Notice Receipts

Joint controller essence events may reference ADR grants for each controller in the arrangement.

Verify any
ADR receipt.

verify.dekimu.com ↗

Paste any claim ID to verify a receipt, check its anchor, and inspect the issuer signature.

REFERENCES

GDPR Art. 28 — Processor obligations (EUR-Lex) ↗
AI Act Art. 26 — Obligations of deployers (EUR-Lex) ↗
eIDAS 2 — Powers of representation in EUDI Wallet (EUR-Lex) ↗

Anchored Delegation 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.