> For the complete documentation index, see [llms.txt](https://operations.clausebase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://operations.clausebase.com/updates-july-2024/21-july-2024.md).

# 21 July 2024

## Deep Compare

<mark style="background-color:orange;">New feature</mark> In addition to the rule-based ("playbook") review function, ClauseBuddy now also features the possibility to intelligently compare a document against another document.&#x20;

Deep Compare will intelligently line up your active document with some other document that you upload. You can then immediately see the legal differences between various clauses, and even create merged versions of each clause.&#x20;

Typical use cases include:&#x20;

* Situations where you have to use the document of your counterparty, but you want to compare it against your own standard document to see what's missing.&#x20;
* Law firms that need to review their client's document, and want to compare it against one or more of their own "golden standard" templates.&#x20;
* Merging two different templates containing partially similar and partially different clauses.&#x20;

<figure><img src="https://1414353930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fc1g6bv00az2hAVxclF4w%2Fuploads%2FLdoOjA5SEXjrMs9pXbdY%2Fimage.png?alt=media&amp;token=526017ed-ccb9-4630-903a-e6847c83e366" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://operations.clausebase.com/updates-july-2024/21-july-2024.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.