TT Claude Memory

project_dade_unfinished_digital_estate_report

Properties1
descriptionPrimary DADE reference. Published 3 March 2026 by OpenID Foundation (Flanagan, Kiser, Saxe eds.) with contributions from Eve Maler, MOSIP, Venn Factory, Kleinbard LLC. 43-page analysis of digital-estate gap. Companion to the Lau Pa Sat Report — this is the real DADE work; Lau Pa Sat is Rich's scenario projection of it.

7 min read

What the report is

“The Unfinished Digital Estate: Culture, Law, and Technology after Death” — OpenID Foundation publication, 3 March 2026. Editors: Heather Flanagan, Mike Kiser, Dean H. Saxe. Contributors include Eve Maler (Venn Factory), Sasikumar Ganesan (MOSIP), George Fletcher (Practical Identity), Ramesh Narayanan (MOSIP), John Scullen (Australian Access Federation), Jennifer Zegel (Kleinbard LLC), plus OIDF’s Death and the Digital Estate Community Group.

Location: ~/off-github/library/The-Unfinished-Digital-Estate-Final.pdf (43 pages).

Why it matters for INHERIT foundation architecture

This is the authoritative DADE document — ground truth for what DADE thinks. The Lau Pa Sat Report is Rich’s scenario projection of the same group’s review of INHERIT; the DADE report is the actual published work. Where the two documents diverge, the DADE report takes precedence.

Headline salient points

1. The “digital estate lifecycle” gap is DADE’s problem statement

Section 5.3 — “no widely adopted framework currently ties identity delegation to estate events, such as death or incapacitation.” They identify three specific missing pieces:

  • Mechanisms to express delegated access rights and state change events (incapacitation notices, digital death certificates, executor assignment)
  • Consistent, trustworthy APIs for requesting and verifying death or incapacitation status, with revocation for errors
  • Delegation protocols that work across identity providers and platforms, contingent upon data owner’s death or incapacitation

Implication for INHERIT: These three pieces are the DADE layer; INHERIT provides the entities and state those protocols reference. Clean two-layer split.

2. OpenID Foundation is explicitly claiming delegation-protocol leadership

Section 5.3: “The OpenID Foundation is well-positioned to design such protocols, potentially by extending existing protocols, with the cooperation of service providers, governments, lawyers, and experts in identity systems.”

Section 8.2 names four bodies for coordinating delegation semantics: OpenID Foundation, W3C, IETF, Kantara Initiative. These are the standards-body coordination targets for INHERIT’s DADE-adjacent work.

3. New concepts DADE introduces that INHERIT must map

  • Legacy Manager — DADE term for the designated individual who holds credentials to access estate owner’s data at service providers after death/incapacitation. Analogous to but distinct from executor/attorney. INHERIT needs a clean mapping: probably a new role entity OR an extension of existing executor/proxy with a digital-estate scope.
  • Digital Estate Service — trusted intermediary that issues legacy-manager credentials upon verified death/incapacitation. Operates between service providers and fiduciaries. INHERIT needs to know which digital estate service applies to an estate (metadata field) and how to describe the delegation flow.
  • State change events — verifiable facts about the estate owner (death, incapacitation, executor assignment, revocation). First-class events that trigger protocol actions.

4. Specific technical anchors named

  • OAuth 2.0 Token Exchange (RFC 8693) — starting point for token-based delegation. Actor tokens indicate “identity A acting for B”; role transitions (caregiver → executor → fiduciary); scope/duration control; revocation/auditability.
  • Kantara UMA (User-Managed Access) — consent, delegation, relationship management. Supports multi-party delegation, bounded scopes, time-limited roles. Handles “family ambiguity” during divorce, estrangement, care transitions, contested estates.
  • Sovrin Guardianship framework — self-sovereign identity (SSI) with layered governance/define-time/run-time. Distinguishes dependent and guardian roles, jurisdictional anchoring, revocability, auditability.
  • OpenID Foundation’s Delegated Authority Specification for Digital Trust (DASDT) — from eKYC & IDA Working Group. Critically: explicitly encompasses humans AND AI agents acting on behalf of others. Spans online services, SaaS, healthcare, business process automation. This is directly relevant to InheritKit’s agent layer.

5. Delegation semantics — “on-behalf-of” not “impersonation”

Section 6.1 — DADE strongly advocates on-behalf-of delegation that preserves identity boundary between principal and agent, over credential-sharing impersonation. “Services must consider how to deploy on-behalf-of delegation models for legacy managers and deprecate impersonation-based processes.”

INHERIT architecture should assume on-behalf-of as default; current estate-planning practice (sharing passwords to a password manager) is explicitly the anti-pattern DADE wants to retire.

6. Threat models — first-class architectural criterion

Section 6.5 identifies four threat models INHERIT must anticipate:

  • Elder abuse / financial exploitation — caregivers coercing credential handover
  • Partner and domestic abuse — abusers weaponising shared-account access
  • Institutional overreach — schools, care homes, religious organisations claiming delegated authority
  • Inheritance without intent — default kinship access overriding deceased’s wishes

All four are reasons INHERIT needs revocability, audit trails, bounded scopes, multi-party delegation, and delayed/conditional triggers.

7. Posthumous AI is a substantial DADE concern

Section 7 — entire section on posthumous synthetic media, AI avatars, deepfakes. Consent/control after death. Cites NO FAKES Act (US), EU AI Act.

Implication for INHERIT: Testator wishes regarding post-mortem digital representation (AI avatars, synthetic media, posthumous public usage of likeness) should be first-class data. New entity or extension of existing wishes/directives.

8. Cultural diversity is load-bearing throughout

Section 2 (entire section) covers cultural variation: Western, Eastern (Hindu, Buddhist, Chinese ancestor worship, Japan’s multi-phase rituals), African (Madagascar famadihana, immediate-return societies), Indigenous (Kota, Hopi, Apache). Section 2.2 — implications for digital estate planning including:

  • Multiple delegate types (ceremonial steward vs financial executor vs trustee)
  • Language localization and culturally specific defaults
  • Ritualized content deletion, online memorialization, shared mourning spaces, ancestral record preservation
  • Shared/co-signing delegation vs single-designee
  • Community/religious validation methods carrying social legitimacy without formal documentation

Strongly validates v3.1’s internationalisation emphasis and argues for more than just English/Arabic SCR rendering in Phase 2.

9. MOSIP integration pattern

Section 5.2 sidebar — MOSIP (Modular Open Source Identity Platform) integrates death registration with civil registration. Service providers confirm death through legally accurate source. Pattern: national ID platform handles verified facts; service providers + nominees handle delegation and inheritance.

Implication: INHERIT should specify how it references civil-registration facts (death certificate issuance, ID number, date/place) cleanly — probably via verifiable credential reference rather than duplicating the facts.

10. Digital Estate Bill of Rights

Section 8.1 — four rights the report claims individuals should have:

  • Right to designate digital delegates
  • Right to revoke delegation before death/incapacitation
  • Right to privacy and dignity in post-mortem data handling
  • Right to audit who accessed one’s digital identity after death

Useful as a v4.0.0 architectural validation checklist: does INHERIT’s entity + event model support all four rights?

Relationship to Lau Pa Sat Report

The Lau Pa Sat Report (Rich’s scenario projection, 15 April 2026) includes a “DADE contingent” (Eve Maler, Mike Kiser, Dean Saxe, Heather Flanagan) whose recommendations map to this report’s findings. Rec 4 (formalise INHERIT + DADE two-layer architecture) is validated and enriched by this report’s specific protocol anchors (OAuth Token Exchange, UMA, Sovrin Guardianship, OIDF DASDT).

Where tension could arise: the Lau Pa Sat Report treats the DADE layer as a clean seam where INHERIT stops. This DADE report is more ambitious — it claims OIDF leadership over delegation-protocol development and expects INHERIT-adjacent work to align. v3.2 handoff prompt should reflect both: INHERIT as the data/state layer, DADE as the delegation-protocol layer, with explicit alignment points rather than just a “seam.”

Consequences for v3.2 foundation-architecture handoff prompt

  1. Add DADE report as primary source document alongside Lau Pa Sat
  2. Expand Lau Pa Sat Rec 4 (INHERIT+DADE two-layer) with specific DADE protocol anchors
  3. Add threat-model resistance as architectural evaluation criterion
  4. Add posthumous AI as Phase 2 SCR dimension
  5. Strengthen standards-body pathway with explicit OIDF + W3C + IETF + Kantara four-way coordination (per DADE §8.2)
  6. Map DADE concepts (Legacy Manager, Digital Estate Service, state change events) to INHERIT entity model
  7. Reinforce cultural framing — DADE §2 provides explicit evidence
  8. Add Digital Estate Bill of Rights as v4.0.0 validation checklist
  9. Add MOSIP / civil registration pattern to Phase 1 research subjects
  10. Flag “on-behalf-of not impersonation” as a default assumption across INHERIT+DADE

Graph View

Backlinks