> For the complete documentation index, see [llms.txt](https://docs.rierino.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rierino.com/installation/artifacts/deployment-assets.md).

# Deployment Assets

Deployment assets are JSON files specifying configuration and data sets that are used during initialization of Rierino platform and deployment of new modules.

These data artifacts are accessible through the following repositories, based on modules to be deployed, given that you have the access rights granted.&#x20;

{% embed url="<https://github.com/rierino-open/deployment-assets-core>" %}
Core Platform
{% endembed %}

{% embed url="<https://github.com/rierino-open/deployment-assets-train>" %}
Training Assets
{% endembed %}

{% embed url="<https://github.com/rierino-open/deployment-assets-cms>" %}
CMS Module
{% endembed %}

{% embed url="<https://github.com/rierino-open/deployment-assets-pim>" %}
PIM Module
{% endembed %}

{% embed url="<https://github.com/rierino-open/deployment-assets-cim>" %}
CIM Module
{% endembed %}

{% embed url="<https://github.com/rierino-open/deployment-assets-bas>" %}
BAS Module
{% endembed %}

{% embed url="<https://github.com/rierino-open/deployment-assets-per>" %}
PER Module
{% endembed %}


---

# 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://docs.rierino.com/installation/artifacts/deployment-assets.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.
