> For the complete documentation index, see [llms.txt](https://knowlg.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowlg.sunbird.org/learn/capabilities/phygital-discovery.md). # Phygital Discovery Phygital bridges the gap between the physical and digital world. The objective is to bring the best of the physical experience into the digital realm and vice versa. Sunbird Knowlg uses the [DIAL spec](https://github.com/sunbird-specs/DIAL-specs/blob/main/README.md) to power the phygital discovery of assets. This capability is already massively used across India with billions of DIAL QR codes already in circulation. **Key Capabilities:** 1. Flexible codification for easy printing by publishers 2. Ability to use an online code/ID registry with resource descriptor metadata 3. Ability to codify any physical learning resource 4. Ability for any app to scan, obtain metadata, and provide personalized learning experience to users More details can be found in the below video: {% embed url="" %} --- # 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://knowlg.sunbird.org/learn/capabilities/phygital-discovery.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.