> For the complete documentation index, see [llms.txt](https://gitbook.jur.io/jur-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.jur.io/jur-documentation/key-notions/web3-and-organizations.md).

# Web3 and Organizations

Understanding an infrastructure and a set of tools within Network States exposes you to complexities. In this Section, we will explain some concepts in a simple way to allow anyone to understand some reasons behind Jur's technical and non-technical choices.

In the [Architecture](broken://spaces/e0gh1TDq8xPigDfix7j0/pages/nYpoj5PoxuzqWpfhJmo8) Section you will find a more in-depth explanation that requires a minimum of exposure to be understood.

Web3 is a set of technologies, generally referable to the birth of Bitcoin in 2008, which enables trustless transactions and relationships: it is not necessary to trust third parties. Web3 has had a big impact on the financial aspect.

However, the future of Web3 is in supporting new mechanics of social organization. This is the true strength and opportunity of this technological phase.


---

# 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://gitbook.jur.io/jur-documentation/key-notions/web3-and-organizations.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.