> For the complete documentation index, see [llms.txt](https://docs.borderless.art/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.borderless.art/team-structure/b.1ab/self-organising-communities-soc-dapp/value-propositions.md).

# Value Propositions

1. <mark style="color:purple;">**For Communities:**</mark> The prevailing approach to constructing a digital community relies heavily on Web2 tools, often leading to concerns regarding privacy and ownership rights over the community and its content. SOC represents a fusion of existing Web3 community management tools, seamlessly integrated with b0rder1ess products.
2. <mark style="color:purple;">**For Users:**</mark> SOC redefines user participation within communities, offering transparent terms and a guaranteed, tangible return on investment.
3. <mark style="color:purple;">**For Brands:**</mark> Discover a novel avenue for crafting, nurturing, and engaging communities within the brand ecosystem, facilitating inter-brand interactions and connections with other communities.


---

# 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.borderless.art/team-structure/b.1ab/self-organising-communities-soc-dapp/value-propositions.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.