Canon term · Identity & discovery

Decentralized Identifier

A URI that resolves to a document containing public keys, authentication methods and service endpoints, controlled by its subject rather than issued by a central registry, and designed to be verifiable and persistent across the platforms the subject uses.

  • StatusIndustry term
  • AdoptionDraft standard
  • LayerGovernance
  • Short formDID

Why it matters

The most mature published answer to the narrow part of agent identity: giving a non-human actor a durable, cryptographically verifiable identifier that survives the platform it was created on. It answers who, and only who. An identifier that carries no authority is still the prerequisite for granting any — you cannot issue a permission to something you cannot name.

Where it comes from

W3C Recommendation (DID Core). Adopted by several proposed agent networking protocols as the identity primitive.

Defining sources

What it is not

These are routinely confused with Decentralized Identifier. The distinctions have consequences for how a system is governed.

  • Agent Identity

    A DID is a technical identifier. Agent identity is the broader property that includes a recorded authority grant and an attributable action history. The DID is one component.

  • Authority Grant

    The DID says who. The grant says what they may commit. Conflating them is the same category error as reading a tool manifest as a permission.

  • Service Account

    A service account is issued by a platform and dies with it. A DID is controlled by its subject and is portable.

How it connects

What it needs

  • Decentralized Identifier depends on W3C-DID Standard

What relies on it

  • Decentralized Identifier is a precondition for Agent Identity Canon term

MARQUE questions it addresses

  • IdentityWhat is the agent, legally, and to whom does its output belong?

Connected through the MARQUE (a reference framework organized around eight questions) crosswalk, an editorial mapping. These objectives from the Financial Services AI Risk Management Framework are assigned to the same questions that this term addresses. The ones sharing most of this term's vocabulary are shown first, as a reading aid. The assignment is to the question, not to the term: the source does not map this term to any objective directly.

Question: Identity · 32 control objectives assigned

  • GV-1.6.2AI Inventory and Data IntegrationGovern
  • GV-1.6.5AI Inventory Risk AnalysisGovern
  • GV-6.2.1Third-Party AI Contingency PlansGovern
All 32 objectives assigned to Identity

Cite and reuse

Cite the identifier QIS-TERM-00023, not the URL: identifiers are stable, URLs may change. This entry is free to read, quote and index under the dual license. Corrections sent to editor@qisfund.com are published.

Technical details: identifier, graph relationships and record
QIS-TERM-00023: outbound relationships as published in api/graph.json and api/lexicon.json
PredicateTarget identifierTargetPredicate meaning
requiredByterm:agent-identityAgent IdentityRead the other way round: the object requires the subject. The subject imposes the object as a precondition.
addressesmarque:identityIdentityThe subject speaks to the object as a question or concern.
dependsOnstd:w3c-didW3C-DIDThe subject cannot function correctly without the object.
relatedToterm:identityIdentityAn association too weak or too general for a stronger verb.
Canonical identifier
QIS-TERM-00023
Tier
Canonical industry term
Domain · layer
Identity & discovery · Governance
Semantic aliases
None recorded
First published
2026-08-02
Last reviewed
2026-08-02 · 180-day cycle