> 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/es/foundations.md).

# Fundamentos

Paradigmas lógicos y teóricos que forman la base de la metodología Sexy Trees.

Para medir los ecosistemas para los mercados financieros, primero debemos negociar paradigmas entre la Naturaleza (mejor representada en [las ciencias indígenas](https://sexytrees.savimbo.com/methodology/es/trees/chagras.md)) y [los mercados financieros](https://sexytrees.savimbo.com/methodology/es/foundations/emerging-markets.md) (una de nuestras ciencias más optimizadas del mundo industrial).&#x20;

Aquí hay paradigmas multidisciplinarios que hemos adoptado, y que tardaron años en construirse, para abarcar la ciencia emergente en la siguiente sección, pero animamos a los lectores a revisar de forma independiente los marcos lógicos en los que operamos.

<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 naturaleza es compleja y caótica.</td><td><a href="https://sexytrees.savimbo.com/methodology/es/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>Están surgiendo mercados para la Naturaleza.</td><td><a href="https://sexytrees.savimbo.com/methodology/es/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>Los ecosistemas tienen dimensiones ortogonales.</td><td><a href="https://sexytrees.savimbo.com/methodology/es/foundations/orthogonal-stacking.md">Dimensiones ortogonales</a></td></tr><tr><td><h3><i class="fa-reply-clock" style="color:$warning;">:reply-clock:</i></h3></td><td>La medición ex post recompensa a las personas adecuadas.</td><td></td></tr><tr><td><h3><i class="fa-hands-asl-interpreting" style="color:cyan;">:hands-asl-interpreting:</i></h3></td><td>Las economías de base comunitaria son más tangibles.</td><td><a href="https://sexytrees.savimbo.com/methodology/es/foundations/economia-de-base.md">Grassroots econonomics</a></td></tr><tr><td><h3><i class="fa-hand-shaka" style="color:pink;">:hand-shaka:</i></h3></td><td>El codiseño poscolonial recluta más inteligencia.</td><td><a href="https://sexytrees.savimbo.com/methodology/es/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>El bricolaje refina las soluciones más rápido.</td><td><a href="https://sexytrees.savimbo.com/methodology/es/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/es/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.
