> For the complete documentation index, see [llms.txt](https://docs.tabiya.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tabiya.org/tabiya-documentation/deutsch/unser-technologie-stack/compass/roadmap.md).

# Roadmap

Unsere Vision für den Kompass umfasst:

* ***Erweiterte geografische Reichweite:*** Weitverbreitete Nutzung des Kompasses in Schwellenmärkten
* ***Mehrsprachige Unterstützung:*** Sprachfunktionen ausbauen, um vielfältige Bevölkerungsgruppen zu erreichen
* ***Sprachintegration:*** Ermöglichen Sie unseren Nutzern, in ihren lokalen Dialekten mit dem Kompass zu sprechen
* ***Portables Skills-Wallet:*** Ergebnisse der Kompetenzerkundung des Kompasses, aktiviert in einem interoperablen Skills-Wallet
* ***Erweiterte Funktionen:*** Fortschrittlichere Empfehlungen für Karrierepfade und Kompetenzentwicklung entwickeln
* ***Integrationsmöglichkeiten:*** APIs und Tools für eine nahtlose Integration mit bestehenden Jobplattformen und Karrierediensten erstellen
* ***Wirkungsmessung:*** Eine mehrseitige randomisierte Kontrollstudie implementieren, um die Wirkung des Kompasses auf Karriereergebnisse zu schätzen


---

# 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.tabiya.org/tabiya-documentation/deutsch/unser-technologie-stack/compass/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.