> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/contrats/declarer-un-contrat.md).

# Declare a Contract

You can declare a new contract by clicking on the "Create a Contract" button located on the main page of the Contracts module.

<figure><img src="/files/Wjj9ycmL2ct0LwgKQ3DO" alt=""><figcaption><p>Declare your first contract by clicking on create a contract</p></figcaption></figure>

You can choose to start from scratch or generate a contract from one of our[ dynamic contract templates](/en/features/contrats/modeles-de-contrats-dynamiques.md).

<figure><img src="/files/fTPlT5CjVvbz7Pd9HYoh" alt=""><figcaption><p>Creation options for a contract</p></figcaption></figure>

Starting from scratch, you just need to give your contract a name, upload your attachment (you can also choose to upload the attachment later once the contract is declared), and assign it to an organizational unit.

<figure><img src="/files/17BDR0CEtcnMAp2Y64NB" alt=""><figcaption><p>The form to create a new contract</p></figcaption></figure>


---

# 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://doc.dastra.eu/en/features/contrats/declarer-un-contrat.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.