> For the complete documentation index, see [llms.txt](https://docs.flash.trade/flash-trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flash.trade/flash-trade/flash-trade-protocol/faf-token/faftarchy-governance/faftarchy-commandments.md).

# FAFtarchy Commandments

To ensure that all proposals uphold integrity, predictability, and alignment with the long-term value of the protocol’s native token, the core team commits to the following governance standards when drafting Futarchy proposals:

* **State Impact on Token Value** Clearly explain how the proposal benefits the protocol and token value, including the mechanism of impact, current relevance, and expected net-positive outcomes (especially for token supply increment and incentive changes). 
* **Define Measurable Metrics** Include specific KPIs or performance metrics that can be used to evaluate success post-implementation.
* **Include Opportunity Cost Analysis** Summarize resource requirements (e.g. dev hours, emissions, treasury spend) and potential trade-offs.
* **Align with Strategic Goals** Show how the proposal fits into the protocol’s broader mission — is it foundational, experimental, defensive, or opportunistic?
* **Add Post-Implementation Review** Describe how results will be evaluated, made public, and used to guide future decisions.

**How we handle proposals:**

1. Proposals can only be put up by Core Team.
2. Proposal Drafting occurs in the Flash Discord to arrive at reasonable parameters for the specifics.
3. In the case of a failed proposal, it can be revisited in 1 month only.
4. **Proposals Must Be Specific and Executable**
5. The token holders can suggest drafts of proposal which then can be improved and put up for voting by the team.

All proposals must define concrete, unambiguous implementation parameters (e.g. smart contract changes, allocation percentages, timelines) to ensure clarity and enforceability.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flash.trade/flash-trade/flash-trade-protocol/faf-token/faftarchy-governance/faftarchy-commandments.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.