> 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/9-july-2024.md).

# 9 July 2024

## Automatic "legal feature" extraction

<mark style="background-color:orange;">New feature</mark> In the Quality Library, Truffle Hunt and Samples Hunt, you can now ask the LLM to automatically extract "legal features" from the currently visible clauses, and then filter on such features.&#x20;

Such legal features are interesting characteristics with legal value, e.g. for a duration clause, whether the term is defined or undefined, whether the term can be renewed, whether one party can(not) unilaterally renew or terminate, which deadlines need to be respected and so on.&#x20;

After the LLM has processed all the clauses (which usually takes only a few seconds for up to 50 clauses), end-users can then easily filter clauses on the available legal features.&#x20;

<figure><img src="/files/uywKcuuGT1BxecLVwjwA" alt=""><figcaption><p>The green buttons in the middle represent legal "features" that were automatically extracted by an LLM. Next, end-users can filter on those features. </p></figcaption></figure>

## Curators

### Indication of group(s) in the dropdown list

In the *Send to Curator* dialog box, you will now see the group(s) to which the curator belongs.&#x20;

<figure><img src="/files/14aVT518RutycfLbaqBq" alt="" width="375"><figcaption></figcaption></figure>

Also, by way of bug fix, curators whose account were disabled will no longer be shown in the list.


---

# 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://operations.clausebase.com/updates-july-2024/9-july-2024.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.
