When you turn on C.ORE™ EntityScript™ files can be read at determined intervals. These intervals can be 'packed' with added functionality.
The following steps are executed on behalf of the operator upon startup and can be modified as needed. These steps provide 1 stateful machine for use. You can continue to startup new machines until a systems resources are exhausted, meaning more than one machine-state can be running at any time. You can also limit the amount allowed at run-time to 1. C.ORE™ itself doesn't launch async processes, but it can provide an async sub-system at any of the steps below. Each step is a significant software process that drives specific machine outcomes utilizing additional EntityScript™ templates.
These are the following documented steps in the startup process:
*Section 9 is deprecated as of 2023/05/28 and has been replaced by an entirely new build phase for draft 1.3. The updated and official runtime build-steps will be published along with version 1.3. The reason for deprecating section 9 from Draft 1.0-1.2 was because the build steps have been modified significantly in the current version. These include expanded processes, and altered routines.
With graphics 1 C.ORE™ instance utilizing EntityScript™ runs under 1GB of ram and provides most functions required to operate a personal computer without any programs besides a window-manager and kernel, plus the implementation language and what's required to run it (Python). Learn more about what happens once EntityScript™ virtualizes your instance by learning about airEP™ HERE