# Dispute

The Dispute pallet provides all the information relevant to the dispute: plaintiff/defendant accounts, agreement hash, claim hash, resolution proof, resolution deadline, resolution method (e.g. arbitration) and other accessory fields.

This structure allows for a Court to provide different types of resolution according to the specific dispute’s needs. We don’t envision large claims in the beginning phase but this would allow the system to potentially handle larger disputes with an arbitration procedure that can be carried out, for example, through the Jur Arbitration Platform.

The aim is to keep things simple in order to iterate with real dispute’s data instead of over-engineering the infrastructure on day 1.

<figure><img src="https://lh4.googleusercontent.com/P_oErcsCAyQwLZKdrG9SM-oYjFfJrq23Fr5B4myLxx1YL0zVothrrPd-kbnrqVAWiVIPqfRnk8whA3UWjnam96MTOisvai6thii4zu4ucywdMF6rK_QtN4tmFwh-Y5PgIjQhJSiV6GvU6y2PrMCWNun1wqetFsyqnid3tWd9ugIy8PxY8CJ1wMIY8fQJpQ" alt=""><figcaption></figcaption></figure>


---

# 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/architecture/dispute-resolution-module/dispute.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.