> For the complete documentation index, see [llms.txt](https://sign-language-center.gitbook.io/tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sign-language-center.gitbook.io/tech/roadmap.md).

# Roadmap

Legend: ✅ completed · ⏳ in progress

## Mission 1: Real-time Sign Language Translator (1 hand)

* Alphabet Translator ✅
* Basic words Translator (such as Hello, Thank you, I love you, etc.) ⏳

## Mission 2: Real-time Sign Language Translator Advanced (2 hands)

* Two-hand recognition model ✅
* Training the model for two-hand recognition words ⏳
* Add words using two-handed gestures to the library ⏳

## Mission 3: Learning Sign Language with AI Agent

* AI Agent detects errors and gives suggestions ✅
* Lesson 1: Alphabet ✅
* Lesson 2: Basic words ✅
* Lesson 3: Daily Communication ⏳
* Lesson 4: Advanced words
* Lesson 5: Family
* Lesson 6: Work
* Lesson 7: Animals
* Lesson 8: Fruits

## Mission 4: AI Voice Generation (The last)

* Combine AI Voice Generation with the Real-time Sign Language Translator Advanced (2 hands), so that sign language can be used to talk like anyone else. ⏳

## Sub-Mission: Donate for the disabled community

* The dev team will send 0.5% of total supply plus community-raised funds to a disabled people's charity. The charity will be decided together with the community.


---

# 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://sign-language-center.gitbook.io/tech/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.