# Judiciary

Jur is building a composable protocol to orchestrate a dispute resolution on-chain. The vision is to create flexible modules to allow organizations to easily build the most appropriate dispute resolution or judiciary system for their particular needs.

A Society focused on gaming will have different needs from a society that has a physical presence and needs a machine to resolve disputes relating to real estate.

Jur's judicial stack includes a modular protocol of dispute resolution mechanisms.

As in the original scope of the project, the stack will offer different types of solutions, potentially linked together. That is, for a case one tool can be used initially, and if a solution is not reached or one party appeals, another tool may be used. Each level of appeal exposes parties to higher costs but higher resolution quality and value. Parties can agree to waive appeal rights to reduce costs.

\
There are two main categories of dispute resolution:

* **Legally binding:** means that they are enforceable in one or more physical jurisdictions
* **On-chain (not legally binding):** They are enforceable on-chain but have no legal validity in an existing physical jurisdiction.

<figure><img src="https://lh4.googleusercontent.com/QG1fDc1tD9XumOmLK91a-HU75O1lZXjGlnVOn2_UvlN3a-TYLwwUZw0mLqVsJyaL-g6e6FGeB_L_kXruGN4W9U6oukDzDvVskRZBUENhHk4Hrj7beOSjBhMHToY4X0Zn33EaWm3MTcSGjHXvvyL4JzDRalCRk29Vq3JUgSLbIoLd7t5c4WBgy84Eaat9vQ" alt=""><figcaption></figcaption></figure>

With a Sovereign Network State a decision can technically be said to be legally binding.\
\
The dispute resolution levels are:

* **AI-driven:** dispute resolution solutions where software and AI produce a form of dispute evaluation.
* **Mediation:** a qualified third party invites the two parties to reach an amicable agreement
* **Adjudication:** A simplified form of adjudication by a third party, usually not legally binding.
* **Arbitration:** A legally binding form in which a private judge (arbitrator) makes a legally binding judgment.

They are preceded by techniques and solutions aimed at preventing disputes.


---

# 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://gitbook.jur.io/jur-documentation/lean-network-state-components/judiciary.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.