> For the complete documentation index, see [llms.txt](https://tracer.gitbook.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tracer.gitbook.io/manual/master.md).

# Introduction

This ongoing and evolving user manual describes the implementation of the TRACER machine, a powerful and flexible suite of some 700 algorithms for the automatic detection of (historical) text reuse. TRACER is developed by Marco Büchler and is written in Java. It is the most comprehensive tool yet and it is continuously improved thanks to the feedback gathered by the numerous tutorials and workshops given by the eTRAP (Electronic Text Reuse Acquisition Project) team at international conferences and events. For more information about the eTRAP Research Group, please visit: <http://www.etrap.eu>

## Useful links

* TRACER developer: Marco Büchler
* TRACER homepage: <http://www.etrap.eu/research/tracer/>
* TRACER repository (to download TRACER): <http://vcs.etrap.eu/tracer-framework/tracer.git>
* Medusa repository: <http://vcs.etrap.eu/tracer-framework/medusa.git>
* Medusa javadoc: <http://www.etrap.eu/medusa/doc/javadoc/Medusa-2.0/>
* TRACER bug reports: <http://www.etrap.eu/redmine/projects/tracer/>

## Copyright

TRACER is released under an **Academic Free License 3.0 (AFL)**.


---

# 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://tracer.gitbook.io/manual/master.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.