> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/1.3/social-registry.md). # Social Registry Social Registry (SR) is an independent module offered by OpenG2P to enable the creation of **registries** of individuals and groups of people with demographic data with advanced features that make the SR interoperable and easily fit into the digital public infrastructure (DPI) infrastructure of a country. The registry can host demographic data of both individuals and groups (family/household) and this data is privacy protected. SR offers the unique feature of issuing digitally signed credentials - Verifiable Credentials - to the beneficiaries. ## Functional architecture {% embed url="" %} Social Registry Functional Architecture {% endembed %} ## Salient features The salient features of OpenG2P Social Registry are the following: * Holds individual and household records with relationships * Share data with other systems via standard interfaces * Privacy controls on the data * Packaged for rapid deployment * Multiple update mechanisms * Automatic computation of scores like PMT * Easy user interface for administration * Deduplication tools including fuzzy deduplication * Registration in areas with no connectivity * Issue unique ID to individuals * Issue Verifiable Credentials --- # 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.openg2p.org/1.3/social-registry.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.