> 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/bracketeer/why.md).
# Why?
On the one hand, Bracketeer qualifies as a kind of **light full-document automation**, because it requires very little preparation to be done within the documents (most templates can be used as-is), and can be learned in a few minutes.
On the other hand, Bracketeer **complements traditional full-document automation**, such as Clause9 and ClauseBuddy's [Smart Templates](https://help.clausebuddy.com/smart-templates/). It allows legal teams to limit traditional full-document automation modules to structural parts that require intensive editing, and leave the numerous detailed changes to Bracketeer.
For example, corporate transaction documentation and finance documentation often consist of more than 50 pages, with hundreds if not thousands of options. In a traditional full-document automation approach, template authors would have to create questions to cover all of those individual options.
* This easily leads to **questionnaire fatigue** with end-users.
* In addition, with traditional full-document automation, end-users may suffer from **question dissonance**, because a certain option may concern such a small detail that the associated question would be quite long or detailed.
When using Bracketeer, template authors can deliberately decide to leave square brackets and highlights within the document that is generated by the system. With the help of Bracketeer, end-users can easily implement hundreds detailed decisions, across the entire document, in a user-friendly way.
* This avoids questionnaire fatigue, because users don't have to answer a question for each and every detail.
* This also avoids question dissonance, because end-users can immediately decide which option to choose when seeing that option within the context of the document, instead of as a separate question.
### Example
By way of a concrete example, have a look at the 30 calendar days highlighted below:
This option does not represent a major drafting decision that will affect many different paragraphs at once. Instead, it concerns details, of which hundreds can be found in a long legal document.
If you would have to formulate a question for it, you would probably have to give a lot of context to the end-user (e.g., *"Number of days granted to the existing shareholders to submit a claim in case of misrepresentation or warranty breach that was notified by an investor?"*). Such question easily takes up half a paragraph, while many legal practitioners will be able to immediately decide whether to change the default number 30 when seeing the context.
---
# 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://help.clausebuddy.com/bracketeer/why.md?ask=&goal=
```
`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.