> For the complete documentation index, see [llms.txt](https://token-engineering-commons.gitbook.io/tec-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://token-engineering-commons.gitbook.io/tec-handbook/tec-agreements-1/why-do-we-need-agreements.md).

# Introduction

Agreements are a key way to protect our common and ensure it’s professionalism, as well as mitigating legal risk. Make sure parties know what their obligations and responsibilities are. The purpose of this is just a little refresher on why agreements are so important because agreements are relevant to any type of relation. A clear, well-drafted social contract, makes it clear what is expected of someone or a DAO and what their position is. Knowing exactly where you stand is important, it allows better working relationships and if it does go wrong, you have a place to go that makes it clear what should have happened from the outset.


---

# 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://token-engineering-commons.gitbook.io/tec-handbook/tec-agreements-1/why-do-we-need-agreements.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.