# Rationale

Creating an interoperable workflow system requires more than static configurations. The primary goal is to map and develop processes that can seamlessly connect to any integration or third-party Distributed Ledger Technology (DLT) system. To achieve this, the language must:

* **Be Readable:** Allow both technical and non-technical users to understand the process at a glance.
* **Be Flexible:** Adapt to diverse systems and evolving requirements.
* **Be Maintainable:** Serve as a bridge between workflows and integrations.

We drew inspiration from **Extensible Data Notation (EDN)**, a configuration format commonly used in Clojure. EDN’s lightweight and expressive structure makes it ideal for modeling workflows in a clear and concise manner. Unlike JSON or YAML, EDN excels at showing data flows and dependencies, making it a better fit for a modular and extensible workflow system.

This approach provides a unified interface between DOVU workflows and third-party integrations, enabling seamless connections and human-readable logic.

{% hint style="info" %}
This is a work in progress. Over time, the language will become even more intuitive, ensuring accessibility and ease of use for all stakeholders.
{% endhint %}


---

# 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.dovu.earth/template-language/rationale.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.