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

# BOKASHI FAQ

Answers to the most common bokashi questions.

<details>

<summary>Where did the word bokashi come from? </summary>

Japan. The word is Japanese (ぼかし, "shading/gradation" — referring to the gradual fermentation process).&#x20;

</details>

<details>

<summary>Where did the practice of bokashi come from?</summary>

The technique was systematized by Dr. Teruo Higa at the University of the Ryukyus in Okinawa in the 1980s, packaged together with his effective microorganisms (EM) inoculant work.\
\
Bokashi got adopted hard across Latin America in the 90s and 2000s. EMBRAPA, INTA Costa Rica, and Colombian smallholder agriculture all picked it up and adapted it to local inputs: cane molasses, rice hulls, chicken manure, biochar, native forest microbes instead of imported EM.&#x20;

By now, the *Latin American version* is a genuinely distinct regional practice — different recipes, different substrates, often anaerobic-then-aerobic instead of strictly anaerobic.

</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/fpic/bokashi-faq.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.
