> For the complete documentation index, see [llms.txt](https://handbook.proanimal.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.proanimal.org/overview/how-we-show-up.md).
# How We Show Up
The principles we agree to abide by in the course of our participation in Pro-Animal Future.
### 1. Power Politics
We win for animals by building real power and being willing to exercise it. Real power is us: voters, volunteers, and small donors acting as a unified bloc.
### 2. Courtesy Breeds Compassion
We strive to cultivate understanding and love for all beings, even our adversaries. But until we get there, we commit to treating ourselves, each other, the public, and our adversaries with utmost courtesy.
### 3. Driven by Research
We know that evidence comes in many forms and from unexpected places. We base our approach on the best of it and constantly look for ways to improve.
### 4. Power Through Stories
The research tells us that facts and righteousness don’t win hearts and minds. We create change through our ability to connect with others. We invite the world to emotionally engage with our cause through storytelling and honest personal disclosure.
### 5. [Do-Ocracy](https://communitywiki.org/wiki/DoOcracy)
Everyone is crew, and all crew members have the authority to appoint themselves Chief Problem Solver of whatever problem they see most urgently being neglected. Decisions are made by the people doing the work; staff positions exist to create and sustain this environment. We don't allow the collective to micromanage the doers, who can act freely within the limits of certain finite resources regardless of whether or not they are staff.
### 6. Frugal
We fund us, and we all deserve to know that our money is used with care. We use creativity to stay frugal so that we can build an independent movement powered by small donations.
### 7. Power Positive
We bring power to the surface and celebrate leadership in all forms, believing that power held wisely—and transparently—by one is power for all. When the power we hold results in harm, we do our best to act with accountability.
### 8. Right to be Raggedy
We dare to work towards a brighter future despite overwhelming odds. We do our best work and celebrate failure as a necessary step on the way, holding ourselves and each other with love and understanding when things blow up in our faces.
{% content-ref url="/pages/-MWV-ZJ\_4\_Ae2T8fID7a" %}
[How We Do Leadership](/overview/how-we-show-up/how-we-do-leadership.md)
{% endcontent-ref %}
{% content-ref url="/pages/-MWV-nfJBzMIsRV6YyRV" %}
[How We Do Power](/overview/how-we-show-up/how-we-do-power.md)
{% endcontent-ref %}
{% content-ref url="/pages/-MWV-pcnOd9DUeL9hfis" %}
[How We Do Culture](/overview/how-we-show-up/how-we-do-culture.md)
{% endcontent-ref %}
---
# 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://handbook.proanimal.org/overview/how-we-show-up.md?ask=&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.