Key ATRIA concepts

Explore the ATRIA the essential components constructors need to understand in order to build experiences with ATRIA AI-driven capabilities

ATRIA use cases constructors

Preset

The preset is the key entity for the configuration of ATRIA. It is like a recipe for your experience, that defines which ingredients to use and in what amounts.

Technically, the preset is a JSON file that defines a hierarchy of both required and optional configuration parameters for the use case configuration.

ATRIA preset

Once the constructors have defined a preset, it must be included in an application to be used by ATRIA.

Prompt

Within an ATRIA preset, a prompt is defined as an input instruction given to an AI model to generate a response. It guides the AI in the required kind of output we want as constructors.

Application

From the constructor’s point of view, an application can be defined as a container for ATRIA presets.

When developing a use case, constructors should use an existing application or create a new one in order to:

Define the specific ATRIA capabilities that can be used, currently Generative AI, RAG, NLP as a Service and Semantic Search.
Declare the presets that this application can use.

Highlights

Every preset and application is identified by both a name and an ID.
To be used and tested, a preset must be placed inside an application (folder).
Nested applications are not allowed. The hierarchy is: application → preset.
An application can contain one or more presets.
A single preset can belong to multiple applications. When you update the preset, it will be updated in all applications it is associated with.

Definition of presets in an application
Each environment can be considered as an independent container of applications and presets. Consequently, if you update a preset in one environment, another preset with the same ID will not be updated in a different environment.