> For the complete documentation index, see [llms.txt](https://resource-network.gitbook.io/resource-technical/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resource-network.gitbook.io/resource-technical/05-protocol-and-network-governance/5.1-introduction.md).

# 5.1 Introduction

The development of the ReSource Protocol is guided by a Swiss association, bylaws of which can be found in appendix A to this paper. This Swiss Association, named “**The ReSource Protocol DAO**” is mainly concerned with the furthering of the protocol’s code-base and the open-source community developing it, however it may also represent the different networks built on top of the protocol layer while directly governing the ReSource Network itself.

Other mutual credit networks, built on ReSource, will be directed by DAOs representing the network’s stakeholders. The exact terms and scopes of DAO governance may vary from network to network; the terms below\[1] describe the ones set for the ReSource Network by the ReSource Protocol DAO.

Decisions concerning the operations of the ReSource Network, such as interest rates, Underwriter whitelists, member acquisition, and reserve policies, will be subject to public votes. Voting rights will be assigned to participants in proportion to 1) SOURCE staked in one of the network’s underwriting pools, and 2) a reputation score.

Staked SOURCE grant their owners asymptotically diminishing voting rights. This means that the first staked SOURCE is counted as one vote, while the second staked SOURCE is counted as 0.90 votes, the third 0.85, and so on. Reputation scores, on the other hand, grant their owners voting rights in direct proportion to their scores.

Since Reputation is a direct, sybil-resilient, and non-transferable result of productive network activity, this hybrid model ensures that the ReSource Network remains governed by its stakeholders and can’t easily be subjected to hostile takeovers.


---

# 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://resource-network.gitbook.io/resource-technical/05-protocol-and-network-governance/5.1-introduction.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.