> For the complete documentation index, see [llms.txt](https://standards.spdci.org/standards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://standards.spdci.org/standards/dci-standards/wip-social-registry-v1.0.0/resources/standards-committee-and-acknowledgments.md).

# Standards Committee & Acknowledgments

of the Social Registry and SP-MIS Interface

## Organisations

The Standards Committee consisted of 20 committed organisations.

<figure><img src="https://544205480-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbUVnrLEoih8bOGfpNjnB%2Fuploads%2FCnWDMVR8qiG4VmqJqQF4%2Fimage.png?alt=media&amp;token=647b8f40-1360-4d7a-8f33-89cb084c325a" alt=""><figcaption><p>Logos of the Standard Committee Members of the Social Registry and SP-MIS Standards Committee</p></figcaption></figure>

### Members

And 25 committed individuals.

<figure><img src="https://544205480-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbUVnrLEoih8bOGfpNjnB%2Fuploads%2FeJi6oS7lUdsQ1pkREiYt%2Fimage.png?alt=media&amp;token=b3f57887-1983-403e-bfb9-0ecd31b1200b" alt=""><figcaption></figcaption></figure>

Find more on our website.

{% embed url="<https://spdci.org/resource/integrated-beneficiary-registry/#committee>" %}
Standards Committee for the Interoperability of Integrated Beneficiary Registry with SP-MIS and Social Registry with SP-MIS
{% endembed %}

### Further Acknowledgments

Apart from the Standards Committee, we thank the following people for their contribution (in alphabetical order):

Andrea Martin, CORE-MIS powered by openIMIS

Dhananjay Chauhan, TNTRA

Jeries I. Shahin, World Bank

Peter Ndeda, Government of Uganda

Robert Worthington, Kwantu/OPM\
\
Stefanie Bitengo and Meme Shadrock, Government of Kenya


---

# 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://standards.spdci.org/standards/dci-standards/wip-social-registry-v1.0.0/resources/standards-committee-and-acknowledgments.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.