In Simorg’s context, the term <<<Function>>> always carries connotations of <<<CPLs>>>.
Function reflects a classical view of software—a view in which Data is not a first-class citizen and processes and routines are given priority.
This view subtly encodes the presence of a “third party”: the developer who writes the code, whose perspective and control remain embedded in the final result. The same mindset appears in other classical constructs, such as the traditional <<<if>>> statement or expression.
As discussed under <<<Data>>>, when we attempt to transfer Consciousness into digital form and build a digital solution, our primary focus should be on Data, not Processes. Yes, Processes (which Simorg calls <<<Shells>>>) are still needed, but they should serve Data, not the other way around. Their purpose is to help Data become more conscious.
Based on this rule, Simorg removes the notion of Function as a fundamental construct, because relying on it tends to lead toward undesirable design destinations.
Continuing in a function-centric paradigm often leads to other side effects, such as the introduction of explicit Nothingness concepts and the need to throw Exceptions and Errors. These are at odds with Simorg’s foundational principles of creation, rooted in the idea—drawn from Abrahamic Religions—that a wise Creator does not create in vain.