> For the complete documentation index, see [llms.txt](https://sexytrees.savimbo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sexytrees.savimbo.com/methodology/fr/foundations.md).

# Fondements

Paradigmes logiques et théoriques qui servent de base à la méthodologie Sexy Trees.

Pour mesurer les écosystèmes pour les marchés financiers, nous devons d’abord négocier des paradigmes entre la Nature (mieux représentée dans [les sciences autochtones](https://sexytrees.savimbo.com/methodology/fr/trees/chagras.md)) et [les marchés financiers](https://sexytrees.savimbo.com/methodology/fr/foundations/emerging-markets.md) (l’une des sciences les plus optimisées du monde industriel).&#x20;

Voici des paradigmes multidisciplinaires que nous avons adoptés, qui ont pris des années à construire, afin de couvrir la science émergente dans la section suivante, mais nous encourageons les lecteurs à revoir séparément les cadres logiques dans lesquels nous travaillons.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-spiral" style="color:blue;">:spiral:</i></h3></td><td>La Nature est complexe et chaotique.</td><td><a href="https://sexytrees.savimbo.com/methodology/fr/foundations/complex-and-chaotic.md">Complex &amp; chaotic</a></td></tr><tr><td><h3><i class="fa-square-person-confined" style="color:$danger;">:square-person-confined:</i></h3></td><td>Les marchés pour la Nature émergent.</td><td><a href="https://sexytrees.savimbo.com/methodology/fr/foundations/emerging-markets.md">Emerging markets</a></td></tr><tr><td><h3><i class="fa-angle-90" style="color:yellow;">:angle-90:</i></h3></td><td>Les écosystèmes ont des dimensions orthogonales.</td><td><a href="https://sexytrees.savimbo.com/methodology/fr/foundations/orthogonal-stacking.md">Dimensions orthogonales</a></td></tr><tr><td><h3><i class="fa-reply-clock" style="color:$warning;">:reply-clock:</i></h3></td><td>La mesure ex post récompense les bonnes personnes.</td><td></td></tr><tr><td><h3><i class="fa-hands-asl-interpreting" style="color:cyan;">:hands-asl-interpreting:</i></h3></td><td>L’économie de terrain est plus concrète.</td><td><a href="https://sexytrees.savimbo.com/methodology/fr/foundations/economie-de-terrain.md">Grassroots econonomics</a></td></tr><tr><td><h3><i class="fa-hand-shaka" style="color:pink;">:hand-shaka:</i></h3></td><td>La co-conception postcoloniale mobilise plus d’intelligence.</td><td><a href="https://sexytrees.savimbo.com/methodology/fr/foundations/postcolonial-co-design.md">Postcolonial co-design</a></td></tr><tr><td><h3><i class="fa-trowel-bricks" style="color:orange;">:trowel-bricks:</i></h3></td><td>Le bricolage affine les solutions plus vite.</td><td><a href="https://sexytrees.savimbo.com/methodology/fr/foundations/bricolage.md">Bricolage &amp; more</a></td></tr></tbody></table>


---

# 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://sexytrees.savimbo.com/methodology/fr/foundations.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.
