# 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.&#x20;

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.&#x20;

{% 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="../reactium/domain" %}
[domain](https://docs.reactium.io/reactium/domain)
{% endcontent-ref %}

{% content-ref url="../actinium/actinium" %}
[actinium](https://docs.reactium.io/actinium/actinium)
{% endcontent-ref %}
