It is amazing that you made it so far! Congratulations!
Now it's time for joy, using our simorg knowledge to unlock the real power behind simorg, to use blueprints, on top of which we all can join together, collaborate, digitalize the innovation, and build the universe of simorg.
Simorg is not only a programming language but also a platform to build and execute. Imagine an ecosystem of building blocks that can be tied together using simorg language and share vibrations between themselves.
So far, all we did was understand simorg's processing mechanism and how we can use the language. From this point onward we will focus on how we can expand the universe of simorg by getting to know its worldview and its ecosystem. This is the moment that the language can have a chance to unleash its real potential by letting billions of digital elements communicate with each other in order to fulfill higher-level business solutions, e.g. Smart Cities, next-generation video games, AI-powered universes, etc.
Actually, this is the first step toward building the universe of simorg: a digital universe which promises a new, unique digital experience. This is only possible if we join together and build it together. To make it happen we need a platform for collaboration. As we briefly touched upon, the platform side of simorg is called logos, the repository of blueprints of creation. More on this in future releases, for now, let's just focus on basic building blocks of this platform and get to know some of them.
Let's quickly define a few important keywords.
Machine
We can define a <<<machine>>> as a device that is running simorg's applications. So a machine is hardware that provides processing power for the engine to execute.
It's worth mentioning that you can definitely consider a machine as an implicit shell because it still is wrapping your vibrations at a higher level. We call it implicit because unlike other types of shells it doesn't have an explicit representation inside our code.
Application
The program that you create using simorg code is called an <<<application>>>. Powered on top of simorg engine, applications are quite powerful entities, they can be published in logos and they can include agents making them able to demonstrate higher levels of consciousness.
Artifact
An <<<artifact>>> is the most basic external building block that we can use inside our simorg application. These building blocks include all possible digital elements from 3D and web components to AI agents, binaries and plugins, and simply every digital element that can communicate with simorg engine.
As you remember, delay was a plugin artifact we used in order to access more advanced capabilities.
Now, solving real problems and implementing complex digital solutions should be done in a timely manner. This is an important reason behind artifacts. An artifact shell is a pre-built piece of software that can be used directly inside our code to help us build our complex solutions faster and more maintainably.
It's nice to share that an artifact is actually a digital element and by instantiating it we wrap it into a mathematical representation so it can naturally embed into the engine's workflows. So this is a mechanism that unifies many different types of digital elements through a mathematical representation.
To have a look at available artifacts, please visit $$$ToPageLinker keyword=Logos toRoute=https://logos.simorg.art$$$.
$$$AlertBox type=HINT title=Simorg's Standard Library message=Simorg is providing a series of basic plugin artifacts that are quite useful. Make sure to visit our Standard Library documentation to know more about them.$$$
Bundles
Using bundles we can package the artifacts and applications together and publish them in logos as a solution. Bundles are created using Simorg Programming Language.
In future releases of simorg, more platform-related tools and documents will be available.
The next section is about creating a famous version of a guessing game but this time, using simorg.