Emerging Platform credential issuance

How the Emerging Platform turns an accepted claim into a verifiable credential, how verifiers check it, and when to revoke or reissue it.

This page covers credential issuance on the Emerging Platform: the reusable flow that turns an accepted claim into a verifiable credential issued to a subject's DID. Solutions built on the platform use it, including Emerging Household Energy. For the household energy flow that issues ITMO credentials, see Emerging Household Energy ITMO credentials.

An outcome certificate is a verifiable credential. Its holder can show it, and anyone they show it to can check it. For how credentials work across IXO, see IXO Credentials.

The issuance flow

  1. Create or receive a claim.
  2. Check that the claim is complete and that the issuer has authority to issue.
  3. Issue a verifiable credential linked to the subject DID.
  4. Publish status references so that verifiers can check the credential.

Claims are decided by a decision oracle and the IXO decision engine: the oracle checks the evidence and produces facts, and the engine applies the rules and signs the decision. What a decision proves, and what it does not, is set out in Trust boundaries.

The credential lifecycle

  1. Define the credential schema and the evidence it requires.
  2. Submit claims and evaluate them against the schema's rules.
  3. Issue the credential to the subject's DID.
  4. Verify the signature, the issuer's authority and the status.
  5. Revoke or supersede the credential when the underlying state changes.

Security and privacy baseline

  • Sign credentials with keys the issuer controls.
  • Store only the metadata you need in registry state.
  • Keep sensitive payloads in encrypted storage where needed.
  • Use capability-based permissions for issuance and revocation.

In Emerging Household Energy

Emerging Household Energy uses credentials for household, device and reporting evidence. Continue with:

What it depends on in IXO