> 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 New feature 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. 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. 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.

The green buttons in the middle represent legal "features" that were automatically extracted by an LLM. Next, end-users can filter on those features.

## 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.

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 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/9-july-2024.md?ask=&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.