> 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/03-the-resource-protocol/3.1-introduction.md).

# 3.1 Introduction

The purpose of the ReSource Protocol is to address and answer the basic economic questions for DLT- based mutual credit systems, while providing a flexible framework within which different kinds of mutual credit systems, serving a multitude of diverse use cases, can be established.

While mutual credit systems built on top of ReSource may differ significantly in terms of purpose, scope, monetary dynamics, and loan policy, they all share core elements such as 1) endogenously created stable credits, 2) overdraft-enabled current accounts, 3) distributed underwriting and risk management, and 4) distributed debt collection and obligation enforcement.

Participants may engage with the ReSource Protocol in one or more of the following four roles:

![](https://lh6.googleusercontent.com/beytWzkDUwIqdIWF2BJdgEbWzXzr6Jdpf5rocSFpw3YmUqeooWxda2EO2220sEUN0uqALEywgM0KmP1nAW6jwYB4OJRUxzim1cQ0Ehdn0vU_m-XqY3C9Jpeobw6FG9uU_vDZnprl)

The nature of these roles and their contribution to the ReSource Protocol will be elaborated on in the following chapters.

Naturally, as stated above, distributed risk management and debt collection are the most sensitive and novel aspects of the Protocol. The general logic driving these aspects will be introduced in the following chapters. The exact mechanics facilitating these processes, the required token economics, and their implications will be elaborated on thereafter.


---

# 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/03-the-resource-protocol/3.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.