# Lineage with any contract type

In this flow, **Data Mover is set up as a server in input and as a client in output**, as indicated by the empty arrow symbol on the left and the filled-up arrow symbol on the right.

<figure><img src="https://files.readme.io/04c020bdd4d5a44e7d15f899fe3ac46db15b7b8238be5e0f9be597052a7d2196-image.png" alt=""><figcaption></figcaption></figure>

The SFTP chip on the left (input) has an orange arrow in the output. Clicking on the SFTP output will take you to the most detailed level, where you can see the flow and its configuration.

<figure><img src="https://files.readme.io/e95b200d34f2de7976bb9ba5db4dbc9cdfa755c764273459c482c41c608ad32f-image.png" alt=""><figcaption></figcaption></figure>

In the figure above, the Lineage option shows the complete flow, whose configuration includes:

* a **source partner** that sends the files to Data Mover with a connection contract using the SFTP protocol
* a **mediation contract** with one action and a virtual path
* an **output contract**, with one action
* an **application** that receives the files from Data Mover using the SFTP protocol

By clicking the MEDIATION **upper part of the box**, the Contract type, Actor, Description, Last update, and Creation date, together with the action, are shown.

<figure><img src="https://files.readme.io/e545b6729553f57c3c70e7f2f4700f8a40d8d7248bd0800fd0d160b957b2f0ca-image.png" alt=""><figcaption></figcaption></figure>

By clicking mediation-vBoxBind in the **lower part of the box**, the Category, Template, Trigger, and links of the contract connection, with all the details, are shown.

<figure><img src="https://files.readme.io/61d913af82749865b7d5211bd887328262ae4b67733cdedadd6fe7d422f07c42-image.png" alt=""><figcaption></figcaption></figure>

You can click on the **Source virtual box** link to expand the panel and see the details of the Virtual Box together with its connection:

<figure><img src="https://files.readme.io/56e2799bc7ec41e95742034e6ef258aaca24f2a4d6ac28ce1dc5fbc9938360ee-image.png" alt=""><figcaption></figcaption></figure>

You can click on the **Destination virtual path** link to expand the panel and see the details of the virtual path:

<figure><img src="https://files.readme.io/424b30eface55731fd349b61a79a2338949c56d0ed7992bb2ea343e032140077-image.png" alt=""><figcaption></figcaption></figure>

The same logic applies to the OUTPUT box. By clicking the OUTPUT **upper part of the box**, the Contract type, Actor, Description, Last update, and Creation date, together with the action, are shown.

By clicking output-to-LngSFTPServer in the **lower part of the box**, the Category, Template, Trigger, and links of the output contract, with all the details, are shown.

<figure><img src="https://files.readme.io/66b2ef33b042ca006fc2bb5b6689793315a87cf68a2f40eae627db8e0e6bb176-image.png" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.primeur.com/data-mover-1.21/actors/actor-lineage/lineage-with-any-contract-type.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.