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

# Landasan

Paradigma logis dan teoretis yang menjadi dasar metodologi Sexy Trees.

Untuk mengukur ekosistem bagi pasar keuangan, kita harus terlebih dahulu menegosiasikan paradigma antara Alam (yang paling baik diwakili dalam [ilmu Masyarakat Adat](https://sexytrees.savimbo.com/methodology/id/trees/chagras.md)) dan [pasar keuangan](https://sexytrees.savimbo.com/methodology/id/foundations/emerging-markets.md) (salah satu dari ilmu dunia industri kita yang paling dioptimalkan).&#x20;

Berikut adalah paradigma lintas disiplin yang telah kami adopsi, yang butuh bertahun-tahun untuk dibangun, agar mencakup ilmu yang sedang muncul di bagian berikutnya, namun mendorong pembaca untuk meninjau kerangka logis tempat kami bekerja secara mandiri.

<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>Alam itu kompleks dan kacau.</td><td><a href="https://sexytrees.savimbo.com/methodology/id/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>Pasar untuk Alam sedang muncul.</td><td><a href="https://sexytrees.savimbo.com/methodology/id/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>Ekosistem memiliki dimensi yang saling tegak lurus.</td><td><a href="https://sexytrees.savimbo.com/methodology/id/foundations/orthogonal-stacking.md">Dimensi ortogonal</a></td></tr><tr><td><h3><i class="fa-reply-clock" style="color:$warning;">:reply-clock:</i></h3></td><td>Pengukuran ex-post memberi penghargaan kepada orang yang tepat.</td><td></td></tr><tr><td><h3><i class="fa-hands-asl-interpreting" style="color:cyan;">:hands-asl-interpreting:</i></h3></td><td>Ekonomi akar rumput lebih nyata.</td><td><a href="https://sexytrees.savimbo.com/methodology/id/foundations/ekonomi-akar-rumput.md">Grassroots econonomics</a></td></tr><tr><td><h3><i class="fa-hand-shaka" style="color:pink;">:hand-shaka:</i></h3></td><td>Co-design pascakolonial melibatkan lebih banyak kecerdasan.</td><td><a href="https://sexytrees.savimbo.com/methodology/id/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>Bricolage menyempurnakan solusi lebih cepat.</td><td><a href="https://sexytrees.savimbo.com/methodology/id/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/id/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.
