> 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/fr/notre-stack-technique.md).

# Notre Stack Technique

- [Taxonomie inclusive des modes de subsistence](https://docs.tabiya.org/tabiya-documentation/fr/notre-stack-technique/inclusive-livelihoods-taxonomy.md): Nous visons à rendre visible et utilisable le capital humain de tous. Cette page introduit les enjeux de ce projet.
- [Methodologie](https://docs.tabiya.org/tabiya-documentation/fr/notre-stack-technique/inclusive-livelihoods-taxonomy/methodologie.md): Creating an inclusive livelihoods taxonomy involves assigning human capital and skills to activities that are usually unseen, which comes with challenges.
- [Pourquoi ESCO?](https://docs.tabiya.org/tabiya-documentation/fr/notre-stack-technique/inclusive-livelihoods-taxonomy/pourquoi-esco.md): The European Skills, Competences, Qualifications, and Occupations taxonomy provides a comprehensive - albeit improvable - taxonomy of skills and occupations, on which our work builds.
- [Enseignements](https://docs.tabiya.org/tabiya-documentation/fr/notre-stack-technique/inclusive-livelihoods-taxonomy/enseignements.md): Extending the ESCO taxonomy by including the unseen economy while adapting our methodology to the challenges met gave us valuable lessons.
- [Taxonomy en open source](https://docs.tabiya.org/tabiya-documentation/fr/notre-stack-technique/inclusive-livelihoods-taxonomy/open-taxonomy-platform.md): Labor markets are diverse and fast changing, so a useful taxonomy must be localizable and adaptable in a transparent way. Our open taxonomy platform empower partners to do this.


---

# 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/fr/notre-stack-technique.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.