> For the complete documentation index, see [llms.txt](https://help.clause9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clause9.com/files/file-types.md). # File types


	documents	Contracts, policies, amendments, annexes, etc. that consist of a collection of different clauses. Documents can be exported to PDF or MS Word (.docx) files.
	binders	Collections of documents that together make up an entire transaction(e.g., a main contract with a pricing annex and several technical annexes). For more information, see: binders.
	folders	Folders – collections of other files and subfolders
	clauses	Clauses consist of paragraphs and subparagraphs of text, optionally preceded by a title. Clauses can be as short as a few words, but can also span several pages, although typically they will consist of one to four paragraphs. For more information, see clauses.
	concepts	Central actors for the automation of a document. Concepts are the legal terms that are defined inside a definition list and allow users to dynamically change clauses and reuse them through different contracts. For more information, see: concepts.
	definitions	Text files that qualify as the definition of a certain concept.
	proxies	Shortcuts to other files or folders in the file system
	images	Logos, graphics, PDF files, Word files and other images.
	memo	In-depth documentation to guide the end-user. See Comments, notes & documentation.

--- # 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.clause9.com/files/file-types.md?ask=&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.