Questions & Answers

Digital World is integrated because it defines how multiple digital capabilities work together rather than treating each capability as an isolated system.

Most digital platforms separately control identity, accounts, data, communication, payments, permissions, and applications.

Digital World establishes shared requirements across those capabilities, including:

• Member control
• Identity continuity
• Consent
• Privacy
• Portability
• Verification
• Interoperability
• Provider neutrality
• Recovery
• Long-term continuity

The purpose is not to create one platform that owns everything.

The purpose is to create one interoperable standard that many independent platforms and providers can implement.

The LIFE Protocol defines the common requirements and guarantees that compatible Digital World systems must follow.

The LIFE Stack organizes the Digital World into 12 connected layers.

In simple terms:

• LIFE Protocol: The shared rules
• LIFE Stack: The 12-layer system organized around those rules

Together, they define how Digital World works.

The LIFE Protocol includes principles such as member-controlled identity, explicit and revocable consent, contextual privacy, proof-based verification, portability, voluntary participation, and freedom from platform lock-in.

The LIFE Stack consists of:

1. Identity
2. Communication
3. Social
4. Intelligence
5. Storage
6. Finance
7. Agreements
8. Governance
9. Voting and Councils
10. Agents and Clerks
11. Browser
12. Builder

Each layer has a defined purpose and boundary.

The layers are designed to work together, but each layer can also support multiple independent implementations and providers.

No.

An implementation may use only the layers required for its purpose. For example:

• A digital identity deployment may use Identity, Governance, and selected Agreement capabilities.
• A communications service may use Identity and Communication.
• A payment service may use Identity, Finance, and Agreements.
• A complete regional LIFE application may integrate most or all layers.

Conformance should be identified by specification, capability, layer, profile, and version.

ClearID is the Digital World standard for:

• Identity
• Identifiers
• Cryptographic control
• Key rotation
• Recovery
• Delegated authority
• Verifiable credentials
• Credential lifecycle
• Issuer authority
• Presentation
• Verification
• Long-term identity continuity

ClearID provides the common identity foundation used across the LIFE Stack.

It is designed for individuals, organizations, devices, services, applications, and digital agents.

ClearID is a standard.

ClearCompanies and other organizations may produce ClearID-compatible:

• Wallets
• Issuer systems
• Verifiers
• SDKs
• APIs
• Recovery services
• Hosted infrastructure
• Applications

Those products implement ClearID. They do not make ClearID dependent upon one vendor or one software repository.

Member-controlled identity means that the individual or responsible organization retains meaningful control over:

• Identifiers
• Credentials
• Keys
• Authorizations
• Presentations
• Relationships
• Recovery
• Provider selection
• Data portability

A provider may assist with storage, recovery, verification, or operation without becoming the owner of the member's identity.

Digital World documentation describes identity as continuity over time rather than a platform account and requires key rotation and recovery without breaking identity.

ClearID uses cryptographically verifiable histories to establish and maintain control of an identifier.

Authorized keys can change without requiring the identifier itself to be replaced. This supports:

• Device replacement
• Lost-device recovery
• Compromised-key replacement
• Personnel changes
• Organizational succession
• Scheduled security rotation
• Long-term cryptographic modernization

The identifier maintains continuity while the authorized keys can change securely.

ClearID can support recovery through methods appropriate to the member, credential, and implementation profile. Recovery options may include:

• Pre-authorized recovery keys
• Multiple trusted devices
• Multi-party approval
• Threshold authorization
• Trusted recovery relationships
• Organizational recovery authorities
• Approved custodial assistance

A state or other implementation profile can define which recovery methods are permitted at each assurance level.

ClearID credentials are verifiable statements issued by an authorized individual or organization. Credentials may represent:

• Identity attributes
• State endorsement
• Residency
• Age
• Membership
• Education
• Professional licenses
• Employment
• Organizational authority
• Ownership
• Eligibility
• Permissions
• Delegated authority

A credential can be held and presented by the member without requiring every verifier to access the issuer's internal database.

A verifier can evaluate:

• Credential integrity
• Issuer identity
• Issuer authority
• Credential meaning
• Credential status
• Expiration
• Revocation
• Holder authorization
• Presentation integrity
• Applicable governance requirements

Verification should not require dependence upon a proprietary Digital World identity database.

Digital World's LIFE requirements emphasize proof-based verification without requiring applications to retain unnecessary identity material.

ClearID supports the full credential lifecycle. A credential may be:

• Issued
• Presented
• Updated
• Suspended
• Reactivated
• Expired
• Revoked
• Replaced
• Reissued

The applicable implementation profile determines:

• Who may issue or revoke a credential
• Which status mechanisms are required
• How quickly changes must become available
• How offline verification is handled
• What audit records must be retained
• When reissuance is required

Yes.

A member should disclose only the information required for a particular interaction. Examples include proving:

• The member is over a required age without disclosing a birth date
• The member is a resident without revealing a full home address
• The member holds a valid license without exposing unrelated credentials
• The member is authorized to act without revealing unnecessary organizational information

The LIFE specification describes privacy through contextual separation, derived identifiers, and consent-based disclosure rather than global exposure.

No.

Digital World does not require identity control, credential issuance, verification, communication, or every LIFE Stack layer to depend upon a blockchain.

A distributed ledger may be used where appropriate for a particular capability, but no ledger is the exclusive root of identity or trust.

Digital World is a broader integrated standard, not a blockchain-specific architecture.

Digital World includes these elements, but they serve different purposes.

• Digital World: The integrated open standard and governance framework
• LIFE Protocol: The shared requirements and guarantees
• LIFE Stack: The 12 connected layers
• ClearID: The identity and credential standard
• Implementation profiles: Jurisdictional or industry-specific requirements
• Reference implementations: Working software that implements the standards
• Applications and services: Optional capabilities built upon the standards

The standard is independent of every individual software implementation.

ClearCompanies provide the primary reference point and initial integrated reference implementations for many Digital World capabilities. Their work may include:

• ClearID implementations
• Wallets
• Issuer and verifier systems
• LIFE applications
• Communication systems
• Social systems
• Finance and payment systems
• Storage
• Agents and clerks
• SDKs
• APIs
• Gateways
• Deployment tools

ClearCompanies demonstrate how the integrated Digital World standard can operate as a working system. Digital World is not limited to ClearCompanies technology.

No.

The ClearCompanies implementation is a reference implementation. It helps to:

• Demonstrate the architecture
• Test interoperability
• Identify missing requirements
• Accelerate deployment
• Develop conformance tests
• Provide implementation and operational experience

Conformance is measured against the published Digital World specifications and applicable profiles, not against identical use of ClearCompanies source code.

Yes.

Another organization can independently build:

• A wallet
• An issuer
• A verifier
• A credential service
• A recovery service
• A gateway
• A communications service
• A storage service
• A finance service
• An application
• An agent system
• One or more complete LIFE Stack layers

Compatibility is based upon conformance with the applicable Digital World specifications and implementation profile. It is not based upon the use of ClearCompanies software.

No.

SDKs are optional tools. An organization may use:

• A Digital World SDK
• A ClearCompanies SDK
• Another compatible SDK
• Its own independently developed software
• A different programming language or framework

The specification defines the required behavior. The SDK is one tool for implementing it.

The ClearCompanies repositories currently represent the primary integrated reference implementation of the wider Digital World system.

Independent implementations exist for many underlying technical capabilities, but there is not yet a large collection of independently developed implementations covering all 12 LIFE Stack layers as one integrated environment.

Publishing the standard separately from the reference software allows additional compatible implementations to be developed, evaluated, and certified over time.

No foundational component requires a Digital World-hosted service.

Governments, companies, universities, nonprofit organizations, communities, and individuals may independently operate compatible infrastructure. This may include:

• Wallet infrastructure
• Issuers
• Verifiers
• Credential status services
• Recovery services
• Gateways
• Communication services
• Storage services
• Financial services
• Governance services
• Applications

Digital World and ClearCompanies may offer managed services, but those services are optional implementations rather than mandatory trust anchors.

Yes.

A government may operate:

• Its own issuer systems
• Its own verifier systems
• Its own credential status infrastructure
• Its own applications
• Its own gateways
• Its own recovery systems
• Its own governance services
• Its own approved-provider directories

A government may also approve multiple public and private providers.

Digital World supports a multi-provider model rather than requiring one exclusive operator.

The architecture is designed so that the ecosystem can continue operating if Digital World or ClearCompanies no longer maintains software or provides services.

Continuity is supported through:

• Published specifications
• Open protocols
• Open-source reference implementations
• Stable implementation profiles
• Portable identifiers
• Portable credentials
• Portable data
• Independent operators
• Replaceable providers
• No mandatory hosted endpoint
• Forkable software
• Independent conformance testing

LIFE conformance specifically requires participant exit, data return, long-term continuity, and freedom from platform lock-in.

Digital World prevents vendor lock-in through technical and governance requirements. A conformant implementation should support:

• Openly documented interfaces
• Portable identifiers
• Portable credentials
• Data export
• Wallet migration
• Independent verification
• Provider replacement
• Recovery
• Operational exit procedures
• No exclusive vendor-controlled trust dependency

A provider cannot make itself the permanent owner of a member's identity, credentials, or relationships.

Platform neutrality means:

• The standard is independent of the software.
• SDKs are optional.
• Wallets can be independently developed.
• Issuers and verifiers are interchangeable.
• Infrastructure providers can be replaced.
• Credentials and data remain portable.
• No proprietary central registry is mandatory.
• No Digital World service is an exclusive dependency.
• Conformance is measured against specifications.

Digital World creates a framework in which providers compete through service and implementation quality rather than through control of the standard.

Digital World maintains:

• The integrated Digital World standard
• LIFE Protocol
• LIFE Stack
• ClearID
• Component specifications
• Implementation profiles
• Interoperability requirements
• Conformance requirements
• Reference architecture
• Versioning and change procedures

Digital World may adopt, profile, and integrate compatible open standards where appropriate.

Where an adequate standard already exists, Digital World can use or profile it. Where an integration, privacy, portability, or governance requirement is missing, Digital World may publish an open specification to fill that gap.

Each specification should identify:

• Specification title
• Version
• Release date
• Stability status
• Normative status
• Compatibility status
• Change history
• Security considerations
• Privacy considerations
• Migration guidance
• Deprecation policy
• Conformance test version

Production implementations may lock to a stable release.

New changes should be reviewed, tested, approved, and deliberately adopted rather than automatically introduced.

Normative documentation defines requirements that a conformant implementation must satisfy. Normative documents may use terms such as:

• MUST
• MUST NOT
• REQUIRED
• SHOULD
• SHOULD NOT
• MAY
• OPTIONAL

Examples include:

• LIFE Protocol requirements
• ClearID specifications
• Message formats
• Interoperability specifications
• Conformance requirements
• Implementation profiles

Informative documentation explains:

• Purpose
• Architecture
• Design intent
• Examples
• Rationale
• Deployment models
• Implementation guidance

Informative documentation helps people understand the system but does not independently create a conformance requirement.

This FAQ is informative.

Conformance is measured against published specifications and implementation profiles. Testing may cover:

• Identity establishment
• Key rotation
• Recovery
• Delegated authority
• Credential issuance
• Credential presentation
• Credential status
• Revocation
• Wallet portability
• Issuer interoperability
• Verifier interoperability
• Data portability
• Privacy requirements
• Offline operation
• Provider exit
• Long-term verification

An implementation is not automatically conformant merely because it uses Digital World or ClearCompanies software.

An implementation profile defines how a particular state, country, industry, organization, or community adopts Digital World. A profile may define:

• Required specifications
• Optional capabilities
• Approved versions
• Credential types
• Privacy requirements
• Security requirements
• Assurance levels
• Issuer requirements
• Verifier requirements
• Provider requirements
• Governance rules
• Portability requirements
• Conformance testing

The profile applies the Digital World standard to a defined environment.

SEDI is the proposed State-Endorsed Digital Identity implementation profile for Utah. SEDI can define Utah's requirements for:

• Member-controlled identity
• State-endorsed credentials
• Approved issuers
• Approved verifiers
• Privacy
• Consent
• Minimal disclosure
• Wallet portability
• Credential portability
• Provider neutrality
• Recovery
• Credential lifecycle
• Long-term verification
• Conformance
• State governance

SEDI would be Utah's identity implementation profile within the broader Digital World standard.

The foundational SEDI scope can include:

• ClearID
• Member-controlled identifiers
• Key rotation
• Recovery
• Verifiable credentials
• Credential status
• Delegated authority
• Wallet portability
• Issuer interoperability
• Verifier interoperability
• Privacy-preserving disclosure
• Consent
• Open interfaces
• Provider neutrality
• Long-term verification
• Conformance testing

These capabilities establish Utah's identity, credential, privacy, and trust foundation.

The following capabilities may use SEDI identity but are not required for core SEDI participation:

• Communication
• Social
• Intelligence
• Storage
• Finance
• Agreements beyond the identity scope
• Voting and councils
• Agents and clerks
• Browser services
• Builder services
• Regional LIFE applications

These services may operate above the SEDI identity foundation without becoming prerequisites for issuing or verifying a SEDI credential.

No.

Utah could adopt Digital World as its standards framework while independently selecting:

• Wallet providers
• Issuers
• Verifiers
• Infrastructure operators
• Application providers
• Recovery providers
• Integration providers

ClearCompanies may provide the initial reference implementation and operational services without becoming Utah's exclusive operator or trust anchor.

Digital World allows Utah to establish SEDI within a broader neutral and reusable standards framework.

Utah would not merely be purchasing a proprietary identity application. Utah would be defining a state profile that:

• Preserves state policy authority
• Protects individual control
• Supports multiple providers
• Prevents vendor lock-in
• Requires interoperability
• Enables credential portability
• Enables wallet portability
• Supports cross-jurisdiction use
• Creates a competitive provider ecosystem
• Can be adopted by other states
• Continues beyond one administration or vendor
• Connects identity to additional services without making those services mandatory

Digital World's current Utah compliance materials also describe LIFE as neutral technical infrastructure rather than a governing or adjudicative body.

Yes.

Another state may adopt:

• Digital World
• LIFE Protocol
• LIFE Stack
• ClearID
• The SEDI profile
• A modified SEDI profile
• Its own independently named profile

Each state may preserve its own laws, credential policies, provider approval rules, privacy requirements, governance, and assurance levels while maintaining interoperability through shared Digital World standards.

Yes.

An application can use ClearID for:

• Login
• Authentication
• Credential verification
• Age verification
• Membership
• Authority
• Consent
• Account recovery
• Transaction authorization

The application is not required to implement every other LIFE Stack layer.

Governments, standards organizations, companies, universities, nonprofit organizations, communities, and independent developers may participate by:

• Reviewing specifications
• Proposing changes
• Building independent implementations
• Contributing reference implementations
• Creating interoperability tests
• Operating infrastructure
• Developing implementation profiles
• Participating in governance
• Reporting security issues
• Reporting privacy issues
• Reporting interoperability issues
• Conducting audits
• Sponsoring pilots