# Design Philosophy and Project Pillars

## Design Philosophy

$MOCA token is:

* An **inclusive** token accessible to all&#x20;
* An **interoperable** means of participation
* A tool for amplifying a **shared network effect**
* A way to forge **new frontiers** in foundational protocol infrastructure
* A method of facilitating **mass onboarding** into web3

## Project Pillars

The $MOCA token and Moca Network embody the three pillars of **Growth, Culture, and Governance**.

### **Growth**

* Partnerships with culturally significant web3 projects and web2 brands to bring them into a single, interconnected, and interoperable growth network powered by the $MOCA token.
* Incentivize participation in the network through digital and IRL engagements, and social connections.
* Grow via network interoperability and multi-party cross-pollination (powered by $MOCA).

### **Culture**

* Foster and enrich the broader verticals of culture within the ecosystem (music, sports, gaming, IP, education, etc.).
* Onboard IP and brands into the network, utilized across the network.
* Reinforce cultural representation through social gamification, aligning digital tribes with $MOCA-powered social products, services, and tools.

### **Governance**

* Push governance as an important and necessary component of web3 culture and digital identity.
* Gather delegated voting power from DAOs across the web3 space to become a “DAO of DAOs” to grow positive influence and synergies across prominent DAOs.
* Incorporate checks and balances into the governance process so that culture and financialization hold each other accountable.


---

# 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://mocacoin.gitbook.io/litepaper/goals-and-objectives/design-philosophy-and-project-pillars.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.
