> 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/how-we-do-culture.md).

# How We Do Culture

### Life and Death

We understand our work to be of grave importance. We ask ourselves and each other to live up to a quality of work and conduct that reflects that.

### Ritual Rich

We design our culture on purpose. We create rituals to vary the flow of our lives, to protect different kinds of engagement, and to mark important transitions.

### Take Your Vacation Time

We know that taking care of ourselves will determine how well we show up. We encourage each other to sleep, eat well, exercise, and literally take vacation time. 

### Warm, Not Cool

We are not too cool for school. We make an effort to be earnest and inclusive while holding each other to high standards.

### Respect the Clock

We show up punctually and prepared, and start right on time to honor everyone’s time. We communicate as soon we know any commitment won’t be kept. Upholding small agreements helps us uphold larger ones.

### Relational Space

We protect time *for* fun, not *from* fun.

### Pro Conflict

Conflict is a rich opportunity for growth and change, and a vital skill for everyone to master. 

### Explicit Expectations

You have no right to your assumptions. When you discover that expectations are misaligned, renegotiate and move on. 

### Ensemble, Not Soloists

We function as a team first and as individuals second. We are at our best when moving as a single organism. 

### Brave Curiosity

Don’t get attached to your ideas. Responsibility for ensuring an open and graceful flow of feedback lives on both giver and receiver. Be gentle and compassionate when critiquing the ideas or actions of others; be open and forgiving while receiving feedback.<br>


---

# 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/how-we-do-culture.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.