> For the complete documentation index, see [llms.txt](https://docs.demos.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.demos.global/onlymeid/roadmap.md).

# Roadmap

**Multi-Provider Landscape**

Originally, OnlyMeID authentication is supported through the biometrics provider Persona. As Demos matures, the platform is designed in a way that can support additional biometrics providers. This will better decentralized and secure the offerings, as users and projects alike can choose across various providers and assess privacy, security, and compliance practices themselves.

**Attestation Extensions**

OnlyMeID reflects a lightweight implementation of Biometrics Proof of Personhood. As the Social Identity layer matures over time, the OnlyMeID enrollment could encompass other pieces of on-chain activity to establish a mure comprehensive user profile. This could refer to a process like interfacing with on-chain reputation systems or otherwise further integrate OnlyMeID into a user's "Social Graph".

**Demos App Layer**

Demos may explore first-party applications that are built on top of and enablyed enabled by OnlyMeID itself. This will give users more intrinsic value when they enroll in OnlyMeID and take advantage of our miscellaneous offerings.

**First-Party AI**

Ultimately, Demos intends to develop its first-party biomtric AI alongside the third-party providers. The benefit of a first-party AI is the ability to design it specifically around Sybil Resistance, and adhering to policies surrounding local attestation and open-source code that could qualify Demos as the first truly Zero Knowledge Biometric Proof of Personhood Protocol.


---

# 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.demos.global/onlymeid/roadmap.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.
