# Redefining “Community-Powered”

We believe in the power of Hypothesis’ community to uphold and execute the core tenets of the platform. While such a notion is not uncommon among traditional social media models, open source communities and the increasingly popular philosophies behind blockchain-driven decentralization, Hypothesis sees community as something to be fostered within the context of accountability and transparency. In other words, the incentives and gamification structures outlined throughout this paper purposefully interweave the motivation of institution and individual to the extent that they rely on each other to meaningfully achieve their goals.&#x20;

Hypothesis’ methods of socialization, while straightforward, are structured in a way such that interacting with other users on the platform most likely begets a constructive, friendly and competitively-oriented experience; one that is non-polarizing and, within the context of the platform’s gamification strategies, encourages users to step outside of their information bubble.

Those methods revolve around Hypothesis’ two primary formats of user-generated content: questions and context—both of which can be produced individually or through the collaboration of a group. Combined with follower networks, Hypothesis’ social incentives encourage users to perform at higher levels in pursuit of a more meaningful in-app experience.


---

# 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://hypothesis.gitbook.io/hypothesis/building-a-platform-based-on-openness-and-transparency/redefining-community-powered.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.
