> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rubicourt.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Dispute policies

> Write the rules Resolve applies, and set how much it may decide on its own.

Your policy is the rulebook for every decision. Resolve applies it as written, so clear, numbered rules produce clear, consistent decisions.

## Publish a version

`PUT /v1/policy` publishes a new version. Disputes keep the version they opened under, so changing your policy never changes a decision in flight.

| Field | Default | Meaning |
| - | - | - |
| `text` | required | Your rules in plain language, at least 50 characters |
| `auto_decide_max_cents` | `25000` | Decisions are final without review up to this amount |
| `evidence_window_hours` | `72` | How long each side has to respond (24 to 336) |
| `review_window_days` | `14` | How long either side has to ask for review or arbitration (3 to 60) |
| `arbitration_enabled` | `false` | Set `true` only if your terms let users escalate to Rubicourt arbitration |

## Writing a good policy

* **Number each rule** ("2. Item not as described"). Decisions cite rules by number.
* **Say what evidence each side should give.** For example: "Sellers disputing a damage claim should show listing or packing photos."
* **Say when partial refunds apply**, and how to size them.
* **List exclusions** plainly, such as buyer's remorse or damage after delivery.
* **Avoid "at our discretion."** A rule the AI cannot apply consistently routes disputes to your reviewers.

> [!TIP]
>
> Start with a low `auto_decide_max_cents`, read a few weeks of decisions in your review queue, then raise it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.