> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/national-learner-registry/digital-credentials.md).

# Digital Credentials

From certificate data to signed, wallet-held, verifiable proof — the full chain from registry record to presented credential.

A credential is never created for an unknown person, and it is never created from scratch. It is generated from data that already exists — and has already been approved — in an authoritative registry, then made portable so the learner can hold and present it independently.

{% hint style="success" %}
**Approved data → authoritative registry record → credential generation → cryptographic signing → credential offer → wallet receipt → presentation → verification**
{% endhint %}

The registry remains the complete, protected source of truth under defined access controls. A Verifiable Credential (VC) is a selective, portable representation of that data — a proof derived from the registry, which the learner controls independently once issued.

{% embed url="<https://www.youtube.com/watch?index=4&list=PLOj17GZ2k4ew&v=fydsjmEtQqQ>" %}

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-award" style="color:$primary;">:award:</i></h4></td><td><p><strong>Certificates, Diplomas and Credential Data</strong></p><p>What a digital certificate is, the two Verifiable Credential types, and how they relate to the registries.</p></td><td></td></tr><tr><td><h4><i class="fa-stamp" style="color:$primary;">:stamp:</i></h4></td><td><p><strong>Digital Signing and Issuance</strong></p><p>What makes a credential trusted, and how the signed credential is generated.</p></td><td></td></tr><tr><td><h4><i class="fa-wallet" style="color:$primary;">:wallet:</i></h4></td><td><p><strong>Wallets, Presentation and Verification</strong></p><p>How a learner receives, stores, and presents a credential — and how a verifier checks it.</p></td><td></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://experience-digital-transform.gitbook.io/experience-digital-transformation/national-learner-registry/digital-credentials.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.