> For the complete documentation index, see [llms.txt](https://help.clausebuddy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clausebuddy.com/truffle-hunt/faq/what-happens-when-i-upload-a-duplicate-clause-or-duplicate-document-to-truffle-hunt.md).

# What happens when I upload a duplicate clause or duplicate document to Truffle Hunt?

As in other ClauseBuddy tools, the Truffle Hunt takes into account file duplication.

In the Truffle hunt result list, de-duplication is done as follows:

* All clauses are converted to lowercase (so that differences in capitalisation are ignored)
* Punctuation is removed (so that differences in that respect are ignored)
* Stop words are removed (so that differences in words like "and", "the", "will", etc. are ignored)

In the end, what it boils down to is that if you were to upload the same document, it would also end up in the basket (which should not be an issue. After all, Truffle Hunt is an inspiration module)

But, an identical clause will **not** be displayed twice in the results.

So for example, let's say you would upload the exact same document 8 times in a basket. Then a clause from the document is not going to appear 8 times in the results, only once.


---

# 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://help.clausebuddy.com/truffle-hunt/faq/what-happens-when-i-upload-a-duplicate-clause-or-duplicate-document-to-truffle-hunt.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.