> For the complete documentation index, see [llms.txt](https://docs.learncard.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.learncard.com/understand.md). # Understand - [Credentials & Data](https://docs.learncard.com/understand/verifiable-credentials-vcs.md) - [Building Verifiable Credentials](https://docs.learncard.com/understand/verifiable-credentials-vcs/building-verifiable-credentials.md) - [Credential Templates (Boosts)](https://docs.learncard.com/understand/verifiable-credentials-vcs/boost-credentials.md): Understand Boosts as reusable credential templates: their structure, lifecycle, and permissions on the LearnCard Network. - [Credential Status & Revocation](https://docs.learncard.com/understand/verifiable-credentials-vcs/credential-status-and-bitstring-status-lists.md) - [Credential Refresh](https://docs.learncard.com/understand/verifiable-credentials-vcs/credential-refresh.md): How an issued credential can be updated in place, and what the network can and can't see while doing it. - [Display Hint Tags (lc: convention)](https://docs.learncard.com/understand/verifiable-credentials-vcs/display-hint-tags.md): A standards-pure convention for carrying display hints on Open Badges v3 credentials using the native \`tag\` field. - [Credential URIs](https://docs.learncard.com/understand/verifiable-credentials-vcs/uris.md): The \`lc:\` URIs that point at credentials, templates, and contracts — and how to resolve them. - [xAPI Data](https://docs.learncard.com/understand/verifiable-credentials-vcs/xapi-data.md): How learning-activity records (xAPI) relate to credentials in LearnCard, and how to name your activities. - [Identity & Trust](https://docs.learncard.com/understand/decentralized-identifiers-dids.md) - [Seed Phrases](https://docs.learncard.com/understand/decentralized-identifiers-dids/seed-phrases.md): The 64-character hex seed behind a server-side LearnCard identity — how to generate it, what it controls, and how to keep it. - [Key Management (SSS)](https://docs.learncard.com/understand/decentralized-identifiers-dids/key-management-sss.md): How LearnCard protects private keys using Shamir Secret Sharing - [Automatic Account Recovery](https://docs.learncard.com/understand/decentralized-identifiers-dids/automatic-account-recovery.md): How LearnCard protects and recovers accounts using hardware enclaves. - [Network Profiles](https://docs.learncard.com/understand/decentralized-identifiers-dids/network-profiles.md) - [Signing Authorities](https://docs.learncard.com/understand/decentralized-identifiers-dids/signing-authorities.md) - [Trust Registries](https://docs.learncard.com/understand/decentralized-identifiers-dids/trust-registries.md): Understanding Trust Registries: Who to Trust in the Digital Credential World - [Auth Grants and API Tokens](https://docs.learncard.com/understand/decentralized-identifiers-dids/auth-grants-and-api-tokens.md) - [Consent & Permissions](https://docs.learncard.com/understand/consentflow-overview.md) - [Brokered Referrals](https://docs.learncard.com/understand/consentflow-overview/brokered-referrals.md): Invite a learner to a partner, issue outcomes, and receive permissioned updates. - [Brokered Referral Lifecycle](https://docs.learncard.com/understand/consentflow-overview/brokered-referral-lifecycle.md): How referrals, consent, credential issuance and partner updates fit together. - [Reading & Writing Consented Data](https://docs.learncard.com/understand/consentflow-overview/writing-consented-data.md) - [Issue on Consent](https://docs.learncard.com/understand/consentflow-overview/auto-boosts.md): Give every user a credential the moment they connect — no call from your server. - [GameFlow](https://docs.learncard.com/understand/consentflow-overview/gameflow-overview.md): ConsentFlow for products used by children — a guardian approves the connection before anything is shared. - [Verifiable Data in ConsentFlow](https://docs.learncard.com/understand/consentflow-overview/verifiable-data-in-consentflow.md) - [How LearnCard Is Built](https://docs.learncard.com/understand/ecosystem-architecture.md): How LearnCard and LearnCloud fit together, and how they interoperate with the world. - [Interoperability](https://docs.learncard.com/understand/ecosystem-architecture/interoperability.md): Explanation: Interoperability, Open Standards, and LearnCard - [Universal Inbox](https://docs.learncard.com/understand/ecosystem-architecture/universal-inbox.md) - [Plugin System](https://docs.learncard.com/understand/ecosystem-architecture/plugins.md): What is a plugin? - [Holder Continuity & Portability](https://docs.learncard.com/understand/ecosystem-architecture/holder-continuity.md): How holders can export, verify, and move LearnCard wallet data --- # 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://docs.learncard.com/understand.md?ask=&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.