Let's now talk about the platform side of the Simorg. The language creates pathways for events and the platform creates an ecosystem on top of it. Language defines how events flow. Artifacts expand what those events can do.
<<<Logos>>> is the collaboration layer: a repository where Artifacts are published and shared.
Artifacts come in different forms and shapes.
A <<<Machine>>> is the device that runs Simorg applications — hardware that provides processing power. At a higher level it is still a Shell because it wraps your events.
An <<<Application>>> is a program written in Simorg. Applications run on the engine, can be published to <<<Logos>>>, and can include agents for higher-level behavior. You can run multiple applications in a machine.
Other artifacts may include <<<Plugins>>>, <<<Binaries>>>, <<<AI Agents>>>, <<<Web>>> or <<<3D>>> components...any digital element that can talk to the engine can become an Artifact.
Artifacts are wrapped in a mathematical shell to join the engine's event flow naturally. Reusability is the key! Ship complex capability once, plug it into many Applications.
For example,
"@simorg/time0.1.0" #delay
"Waiting for 3 Seconds..." ? 3 delay.sec "Done!" ?
Browse published Artifacts on $$$ToPageLinker keyword=Logos toRoute=https://logos.simorg.art$$$.
Simorg also ships a Standard Library of basic plugin Artifacts — start there for everyday utilities.
Agentic Runtime
Instantiate a runtime manager, then create Artifacts from natural language:
"@runtime/openai-runtime-manager0.1.0" #openAi
"your-openai-token" openAi.initialize
"Create a web application and serve it on port 3000" #myApp
The runtime manager builds the Artifact; your code continues to treat it as a Shell in the pipeline.