# Values

1. Respect > Intellect. Respect is the prerequisite to organic collaboration. Be humble with intellect and domain knowledge. Individual expertise is one piece of a larger puzzle.
2. Create > Consume. Seek to create value for others and society where and when you are able; a long-tail of benefits will surely follow for yourself and the community.
3. IRL > URL. As wonderful as the internet is, it will never replicate the shared memories, serendipity, and impact to society that only in-person interactions can provide. Be intentional with IRL engagement.
4. Complementary > Exclusionary. All of an individual's attributes and skill sets are complementary to other individual’s attributes in the build\_community. We cannot assess fish by their ability to climb trees.
5. Scarcity = Innovation. Resource constraints breed innovation. Groundbreaking work is often done by small teams with few resources.
6. Actions = Ideas. Ideas inspire action and action refines our ideas. Both are equal parts necessary to increase the velocity of feedback loops. Ship early and often.
7. Dignity + Opportunity. Dignity and opportunity are fundamental rights of all build\_members, we actively seek to amplify both for each other rather than impede.
8. Building Bridges > Climbing Ladders. Strong networks are built laterally, not vertically.
9. Contribute > Criticize: Constructive conversations are the path towards breakthrough ideas. Don't subtract without adding, especially when criticizing.


---

# Agent Instructions: 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:

```
GET https://build-republic.gitbook.io/build_docs/introduction/values.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.