<<<Artifact>>> is a special type of Blueprint created by artists and developers and published in <<<Logos>>>.
Artifacts are not built on top of Simorg Code, and as the name suggests, they are conceptually outside the core of Simorg’s universe.
As a best practice, each Artifact should represent a single unit of Existence or a single concept. For example, <<<@simorg/std/string>>> is a Plugin Artifact that provides a library of helper string functions. It focuses only on the concept of <<<String>>>.
Determining the scope of an Artifact can sometimes be a complex decision. A useful rule of thumb is to think in terms of reusability: having more granular Artifacts makes it easier to later combine and reuse them across Code and Bundle Blueprints.
Artifacts come in different forms, which can cover all possible digital elements. This can happen thanks to simorg's modeling approach. Some artifacts that are today available in simorg are,
- Binaries
- 3D and 2D Component
- AI Models
- IoT
- Plugin
For example, a web component built using React.js, a 3D avatar created in Unreal Engine, a desktop application written in C++ with Qt, or an IoT device added to the platform using a Raspberry Pi are all considered Artifacts.
Using Artifacts, we can link the Simorg Platform to almost any other digital element and treat it as a <<<Shell>>> that accepts and generates new vibrations.