> 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/practice-guide/id/fpic/faq-bokashi.md).

# FAQ BOKASHI

Jawaban untuk pertanyaan bokashi yang paling umum.

<details>

<summary>Dari mana asal kata bokashi? </summary>

Jepang. Kata ini berasal dari bahasa Jepang (ぼかし, "pengaburan/gradasi" — merujuk pada proses fermentasi bertahap).&#x20;

</details>

<details>

<summary>Dari mana asal praktik bokashi?</summary>

Teknik ini disistematisasi oleh Dr. Teruo Higa di Universitas Ryukyus di Okinawa pada 1980-an, dipadukan dengan karya inokulan mikroorganisme efektif (EM) miliknya.\
\
Bokashi kemudian diadopsi secara luas di seluruh Amerika Latin pada 1990-an dan 2000-an. EMBRAPA, INTA Kosta Rika, dan pertanian petani kecil di Kolombia semuanya mengambilnya dan menyesuaikannya dengan input lokal: molases tebu, sekam padi, kotoran ayam, biochar, mikroba hutan asli alih-alih EM impor.&#x20;

Hingga saat ini,  *versi Amerika Latin* adalah praktik regional yang benar-benar berbeda — resep berbeda, substrat berbeda, sering kali anaerob lalu aerob alih-alih semata-mata anaerob.

</details>


---

# 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/practice-guide/id/fpic/faq-bokashi.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.
