# Domain Model

The Domain Models are structured so that the build process can easily scoop up files and aggregate them to be used when bootstrapping or referencing at run-time. 

Our goal is to eliminate the need to manually add import/require statements for DDD artifacts all over the code. We believe import & require should be *application* focused and not *framework* focused. 

{% hint style="danger" %}
Our Domain Models are ever evolving and should be treated as so. \
We will do as much as we can to maintain backward compatibility where possible.
{% endhint %}

{% content-ref url="/pages/-M5FaINXMv\_Q4nCkQSrQ" %}
[Reactium Domain Model](/reactium/domain.md)
{% endcontent-ref %}

{% content-ref url="/pages/-M5Oa72Tk6kmzKIJrrNg" %}
[Actinium Domain Model](/actinium/actinium.md)
{% endcontent-ref %}


---

# 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.reactium.io/approach/domain-model.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.