> For the complete documentation index, see [llms.txt](https://tutorials.clause9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tutorials.clause9.com/clause9-campus-exercises/module-4-document-assemble-intermediate.md).

# Module 4: Document Assemble Intermediate

**Only complete the following exercises when you have completed the Intermediate Clause Author Tutorial.**

## 4.1 Optional clauses

Add a new "non-solicitation" clause to the Consultancy Agreement.

Make the clause optional, similar to what you did with the "non-compete" clause.

{% hint style="info" %}
Make sure to **reuse** the same condition you used for the non-compete clause, but this time for "non-solicitation" instead of for "non-compete".

For a reminder on how to make clauses optional, check out [this article on the help site](https://help.clause9.com/clauses/enabled).
{% endhint %}

Add the non-solicitation clause to the list of optional clauses in Q\&A mode.

{% hint style="info" %}
For a reminder on how to do this, [check out this article](https://help.clause9.com/qna/how-to-qna/create-predefined-answers-to-a-question).
{% endhint %}

> **Non-solicitation**
>
> Neither Party shall, for the term of this Agreement and for a period of \[non-solicitation-duration] after its termination or expiry, employ or contract the services of any person who is or was employed or otherwise engaged by the other Party at any time in relation to this Agreement.

## 4.2 Numbered list of text

Create a new clause in **the exercise document** with the title and body set out below.

> **Confidentiality**
>
> 1. Either Party may disclose any Confidential Information to:

Create a **list of texts datafield** where the end-user can fill out any parties to which Confidential Information may be disclosed. The information set out below should be included as predefines for that datafield.

The list of disclosure parties should have subparagraph numbering instead of bullets.

> **Confidentiality**
>
> 1\. Either Party may disclose any Confidential Information to:\
> *1.1. the Project manager*\
> *1.2. any employee or officer of that Party*\
> *1.3. any governmental or other authority or regulatory body*

{% hint style="info" %}
Check out this question on our discussion forum to find out how you can create a list of text datafields with continuous subparagraph numbering: <https://discuss.clausebase.com/t/continuous-subparagraph-numbering-for-list-of-texts/334>
{% endhint %}


---

# 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://tutorials.clause9.com/clause9-campus-exercises/module-4-document-assemble-intermediate.md?ask=<question>&goal=<user_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.