> 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/iteration/principles-outperform-rules.md).

# Principles outperform rules

Rules tell you what to do. Principles help you decide what’s right for your land.

For this practice guide, we consulted academic experts with real field experience in the tropics, people who work with smallholder farmers and respect what they know.

Again and again we heard the same advice: “*adapted to the zone*,” “*what local farmers think*,” “*it depends on what’s already working there*.” The experts worth listening to described principles, not rules. So let’s agree on the difference.&#x20;

Again and again, we heard the same advice. "...*adapted for the zone*..", "...*what local farmers think*..", "...*depends on what's already working there*...". The experts we thought were worth listening to would describe principles, not rules. So let's make sure we all agree on the difference.&#x20;

<figure><img src="https://4194359947-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUBWP4JDLn07D1d4y0DKE%2Fuploads%2FhoZVV2h4Odq3PYumJA0B%2Fsmallfarmer-citizen-scientist-tree-seedlings-inga-agroforestry.png?alt=media&amp;token=3b774037-03c1-4e4e-83c3-6c8b8861accb" alt=" Local knowledge guides every agroforestry decision. Smiling smallfarmer in a blue cap and light shirt, holding a walking stick, standing beside a crate of young tree seedlings at a forest-edge nursery, with women working at a wooden table behind him." width="329"><figcaption><p>A smallfarmer and citizen scientist with young tree seedlings ready for planting.</p></figcaption></figure>

### An example: cacao spacing

The literature gives a range of 3 to 5 meters between cacao trees. Colombian agencies most often recommend 3 meters, with wider spacing for wetter, more fertile sites.

### What is a rule?&#x20;

A rule tells farmers: “Plant cacao at 3 meters.” We could hand over a neat diagram. It’s well researched and probably the option most likely to succeed, based on what’s documented.

But is it the best choice for this farm?

### What is a principle?&#x20;

A principle explains *why*. Cacao spacing is a balance of sun and air.&#x20;

Too close, and the canopy closes, humidity builds and fungal disease spreads. Too far apart, and you lose land that could be producing. Rainfall, soil and the cacao variety all shift where that balance falls.

### Why principles outperform rules.&#x20;

“Plant at 3 meters” is good advice. We did our homework, and it’s a solid starting point. But it leaves no room for local intelligence. What if farmers here have already tested this? What if they know this valley is too wet? A lot of work goes into planting a plot, and the rule could grow a fungus.

When we share the principle and the acceptable range, we transfer knowledge and respect farmers’ autonomy. Different farmers may choose different spacing, and that’s fine. The decision is informed, and it’s theirs. We’ve made sure it’s an educated choice, but we don’t take that choice away from them.

In our experience, farmers who make their own decisions, based on evidence, do better over time.


---

# 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/iteration/principles-outperform-rules.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.
