{ "schema_version": "1.0.0", "schema_url": "https://miladhabibi.com/.well-known/agent-docs.schema.json", "name": "Milad Habibi", "description": "Personal writings, lexicon, and experience of Milad Habibi — for AI agents and tools (OpenAI, Claude, Gemini, and others).", "homepage": "https://miladhabibi.com/", "generated_at": "2026-07-18T21:40:02.207Z", "preferred_entry_points": { "structured_json": "https://miladhabibi.com/.well-known/agent-docs.json", "structured_json_alias": "https://miladhabibi.com/docs.json", "llms_txt": "https://miladhabibi.com/llms.txt", "llms_full_txt": "https://miladhabibi.com/llms-full.txt", "sitemap": "https://miladhabibi.com/sitemap.xml" }, "usage": { "summary": "Fetch this JSON once for lexicon + blog content. Use markdown_url for per-page refresh.", "content_format": "text/markdown", "openai_hint": "Pass documents[].content into retrieval / file_search / tool context. Cite with id + title; url is the human page." }, "document_count": 42, "documents": [ { "id": "lexicon/A/Abrahamic Consciousness", "title": "Abrahamic Consciousness", "kind": "lexicon", "category": "A", "category_label": "A", "url": "https://miladhabibi.com/lexicon/A/Abrahamic Consciousness/", "markdown_url": "https://miladhabibi.com/raw/lexicon/A/Abrahamic Consciousness.md", "content_type": "text/markdown", "content": "This lexicon starts by a beautiful concept, the Abrahamic Consciousness.\n\nBefore reading this document, it is important to share that these writings are the result of countless hours of reflection, questioning and thinking in order to overcome the uncertainties regarding how we can create a digital universe.\n\nShould a technical text refer to topics that may, at first glance, seem unrelated to a technology product, especially topics as sensitive as religion? After much consideration, the author chose to be honest and share the full flow of thoughts, as transparently as possible, because they genuinely shaped the creation of Simorg. These are, at their core, beautiful ideas, and there should be no hesitation in sharing the beauty.\n\nAlso, this is aligned by one of core values of simorg, Trust Through Transparency! The author has spent years learning the original languages and studying these sensitive sources because:\n\n* To understand and absorb the concepts as they appear in their ancient languages, first-hand and without intermediaries.\n* To emphasize respect for the communities who live with these ideas and carry them forward. We express our huge respect to Jews, Christians and Muslims.\n\nAlthough, there are also other ideas in form of religions but the reason of focusing on Abrahamic consciousness is its continuous, interconnected history of development. Without any doubt one can see the Abrahamic religions as a massive platform for thought expanding thousands of miles and years in our history on which human's consciousness is manifesting itself.\n\n## Focusing On Consciousness\n\nFrom this point on, we will call Abrahamic Religions as <<>> to emphasize on the core ideas which are common between all three of Abrahamic religions and to focus only on the part that is important for our topic of technology, the consciousness. This decision has been made to respect the communities as the word \"religion\" is carrying a much heavier weight which is shaped through thousands of years on top of history and geography in which the Abrahamic communities were going through. Interestingly when it comes to the topic of consciousness all these differences collapse and a single trait of thought becomes dominant.\n\nAlso, it's worth it to emphasise that academic studies have also been pursued to learn these concepts from reliable sources and to ensure that the materials are approached responsibly. This is still an ongoing process.\n\nWith this background, the author chose to share these ideas, trusting to the beauty and profundity of thoughts. Ideas are not bound by our earthly limitations and borders.\nWe hope that sharing these beliefs and reflections will help reveal how beautifully they can come together, and that this beauty can inspire a better future.\n\nThe absence of certain religions or philosophical traditions in this text should not be taken as a sign of disrespect. Reading such sources in any language other than the original, risks losing essential nuances and core values. Language acquisition is slow—especially when we are dealing with ancient artifacts. The words are carrying the weight and layers of time. It takes time to gently remove those layers.\n\nWith this introduction, we wish you an inspiring journey as you explore Simorg.\n\n## The Beginning And The End\n\nTraces of truth can be found in the wisdom literature of many nations. What is remarkable about the Abrahamic Consciousness is the completeness of their narrative—from the very beginning to the very end. The journey of creation begins from **Nothingness**, which is both magnificent and deeply aligned with a high level of **Consciousness**. Nothingness is a concept that is crucial in software engineering.\n\nAbrahamic consciousness is formed and refined across vast stretches of time and space. They are a masterpiece of human consciousness, collections of ideas encoded into stories. This beauty first emerged through the Jewish people—the “people of the book,” bearers of light in darkness. It is tempting to elaborate much more, but the details are better left for dedicated blog posts.\n\nThe beauty of Judaism is that it gathered a coherent set of values and, for the first time in human history, encoded a higher level of consciousness among nations, giving it a unified form—a light in the darkness.\n\nChristianity and Islam, built on the foundations of Judaism, became wings for consciousness, expanding and strengthening it so it could “fly” and spread across nations. The words of Jesus (peace be upon him) opened new gates to the inner world of the soul and revealed new layers of consciousness, while the Habib (peace be upon him) then carried that light outward and shared it widely with more nations.\n\nThere are still unanswered questions about how this level of consciousness is emerged, why they describe stages of creation the way they do, and how verbs and actions are defined in relation to ideas like nullity or nothingness. While we are thinking about the answers, we can recognize the patterns and extract them in order to use them in our platform architecture.\n\nFor Simorg, this enduring impact is reason enough to engage deeply with these traditions. The sheer scale and continuity of their influence strongly suggests a greater underlying truth. Simorg is proud to integrate these resources into the foundational layer of its architecture, where the primary criterion is the depth and quality of consciousness they carry. Only time will reveal the full results.\n\nThe journey of simorg begins by absorbing consciousness from its **Artisan**s, digitize it, create a digital universe on top of it and let it lead us toward the love, kindness and finally completeness, being the end of this journey.\n\n\n## Three Pillars\n\nSimorg's universe is going to be built on top of three pillars. The name of these three pillars are referring back to their Abrahamic equivalents,\n\n* **Jerusalem** is the name of simorg's engine which has access to the processing power.\n* **Logos** is the name of our package manager which is holding the blueprints of consciousness.\n* **Aql** is the name of simorg's compiler which makes sure of a correct execution of code.\n\nMore details about the patterns of creation derived from the Abrahamic Consciousness and these three pillars will to be shared later in our blog posts.\n\nIf there is one core reason we place such emphasis on the Abrahamic consciousness, it is to study and to understand the consciousness, to observe how it flows through the universe from source to destinations, and to translate that understanding into tools and architectures. This is especially important in today’s technological landscape, where AI is becoming increasingly prominent. We need a next-generation foundation for software—one that weaves consciousness into its very fabric.\n\nSimorg fully embraces technology, progress, and a forward-looking perspective. It sees these not as separate from wisdom traditions, but as complementary. A prosperous future must be built on a foundation of wisdom, understanding and consciousness. Consciousness when isn't passed through the ways of wisdom and understanding, becomes a tool to damage its owners. After all, software engineering is all about materializing consciousness into a digital form.\n\nWe will continue sharing more details in future.\n" }, { "id": "lexicon/A/Aql", "title": "Aql", "kind": "lexicon", "category": "A", "category_label": "A", "url": "https://miladhabibi.com/lexicon/A/Aql/", "markdown_url": "https://miladhabibi.com/raw/lexicon/A/Aql.md", "content_type": "text/markdown", "content": "<<>> (also known as <<>>) is an Arabic term (عقل) that refers to the ability by which **Consciousness** will manifest itself. It is one of the three pillars of consciousness in simorg, a creature that makes it possible to use the power of processing in our universe in order to create consciousness. The first creature of our universe have to be aql.\n\nClassical Arabic (known as *Fus’ha*) is a uniquely rich semitic language. Thanks to the power of this language and to the communities that preserved it, we have a simplified, nicely understandable gateway and portal into the vast deep universe of semitic's ontology. One of the beauties of the arabic language is creating a bi-directional highway between complex deep lofty ontological concepts and earthy physical concepts.\n\nBecause of this characteristic, complex, non-physical concepts are often expressed through concrete physical images and it usually leads to a better understanding of them.\n\nIn the case of aql, the physical connotation emerging from this root refers to the rope that ties a camel's leg so that it does not wander into the wilderness and harm itself. In this sense, Aql is a mechanism that prevents harm to its owner.\n\nThe term thus represents the role of thinking and the protective power of consciousness within us.\n\nThis is why simorg has chosen this beautiful concept as the name of its Compiler. A piece of software that makes sure the user is using the massive power of processor in a meaningful way. Aql is a plugin artifact of the **Engine**, actually the first artifact that is used in the engine. So it is a non-physical element in our universe, acting as a bridge that provides the most direct access to the engine or processing. Through it, users can create new visible or invisible elements within the universe of simorg.\n\nThe non-physical aspects of Aql are present everywhere, and through aql one can access **Logos**, where the **Blueprint**s of creation reside. So aql is the last element through which finally consciousness is transferred and acquired by digital elements of our universe.\n\nImportantly, in Simorg’s worldview, aql is considered the first “creature”. Through aql, simorg words (Code) can create Worlds. This is a direct inspiration from Islamic ontology which believes aql is the first creature (source: [**The book of al-Kafi 🔗**](https://en.wikipedia.org/wiki/Kitab_al-Kafi)). Due to this inspiration the compiler of simorg is considered an essential part of any element in simorg. So it is accessible everywhere inside every single artifact. It is done by running consciousness scripts.\n\nThe world aql is chosen to honor the beauties of Arabic language, the Islamic ontology and those who contributed to it. It is a deep observation that sees the aql as the first creature of the universe. This is simply beautiful.\n\nAql beside **Logos** and **Jerusalem** Engine are the three pillars of consciousness in simorg, belonging to the fundamental layer of architecture, altogether representing Abrahamic Consciousness." }, { "id": "lexicon/A/Art", "title": "Art", "kind": "lexicon", "category": "A", "category_label": "A", "url": "https://miladhabibi.com/lexicon/A/Art/", "markdown_url": "https://miladhabibi.com/raw/lexicon/A/Art.md", "content_type": "text/markdown", "content": "<<>> is a file extension. The files having this extension are containing simorg scripts.\n\nWhen an **Artisan** is able to capture the consciousness in its creation, this is the moment that marks the birth of an artistic being transcending craft and becoming an art.\n\nThe continuation of nature and life is usually visible in an artistic result. This is the reason that simorg picks <<>> as its script extensions to mark the beauty of this moment and to emphasis that we are not only crafting but also letting the life continue in a new dimension.\n\n\n<<>> scripts can be executed using <<>> command from terminal." }, { "id": "lexicon/A/Artifact", "title": "Artifact", "kind": "lexicon", "category": "A", "category_label": "A", "url": "https://miladhabibi.com/lexicon/A/Artifact/", "markdown_url": "https://miladhabibi.com/raw/lexicon/A/Artifact.md", "content_type": "text/markdown", "content": "<<>> is a special type of **Blueprint** created by artists and developers and published in <<>>.\n\nArtifacts are not built on top of Simorg Code, and as the name suggests, they are conceptually outside the core of Simorg’s universe.\n\nAs a best practice, each Artifact should represent a single unit of Existence or a single concept.\nFor example, <<<@simorg/std/string>>> is a Plugin Artifact that provides a library of helper string functions. It focuses only on the concept of <<>>.\n\nDetermining 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.\n\nArtifacts 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,\n\n- Binaries \n- 3D and 2D Component \n- AI Models\n- IoT \n- Plugin \n\nFor 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.\n\nUsing Artifacts, we can link the Simorg Platform to almost any other digital element and treat it as a <<>> that accepts and generates new vibrations.\n" }, { "id": "lexicon/A/Artisan", "title": "Artisan", "kind": "lexicon", "category": "A", "category_label": "A", "url": "https://miladhabibi.com/lexicon/A/Artisan/", "markdown_url": "https://miladhabibi.com/raw/lexicon/A/Artisan.md", "content_type": "text/markdown", "content": "In Simorg, an **Artisan** is a user who can create and publish <<>> in <<>>.\n\nArtisans typically include software engineers, electronics engineers, and 2D/3D artists.\n\nThanks to Artisans, the following categories of Artifacts can be created and published in Logos:\n\n- Applications \n - Desktop \n - Mobile \n - Server \n- Components \n - 2D \n - 3D \n- IoT \n- Plugin \n\nArtisans play a central role in Simorg’s ecosystem. They provide unique digital elements that others can use, combine, and build upon—expanding the universe of Simorg.\n" }, { "id": "lexicon/B/Blueprint", "title": "Blueprint", "kind": "lexicon", "category": "B", "category_label": "B", "url": "https://miladhabibi.com/lexicon/B/Blueprint/", "markdown_url": "https://miladhabibi.com/raw/lexicon/B/Blueprint.md", "content_type": "text/markdown", "content": "In Simorg, a <<>> is a special type of resource from which digital elements are instantiated, either through code or via the platform’s dashboard.\n\nCreators can publish Blueprints in <<>> so that users can quickly assemble digital solutions. Blueprints are reusable digital entities.\n\nSimorg Blueprints are divided into three main categories:\n\n- <<>> \n- <<>> \n- <<>> \n\nEach category corresponds to a distinct stage of creation, and together they reflect Simorg’s three-stage creation model.\n\n<<>> are created by developers and artists and exist outside the core of Simorg’s universe. They belong to the creator.\n\n<<>> are written using the Simorg Language but are not yet instantiated.\n\n<<>> represent 3D compositions of components that are assembled together into a higher-level Blueprint. These components themselves are built on top of the first two categories, but Bundle Blueprints represent “creation from within creation”—new structures formed by combining existing elements.\n" }, { "id": "lexicon/C/Code", "title": "Code", "kind": "lexicon", "category": "C", "category_label": "C", "url": "https://miladhabibi.com/lexicon/C/Code/", "markdown_url": "https://miladhabibi.com/raw/lexicon/C/Code.md", "content_type": "text/markdown", "content": "<<>> refers specifically to Simorg’s Code, which must be written according to the best practices of the Simorg Programming Language. For detailed guidance, please see <<>>.\n\nWords matter because they have the power to create worlds. The Simorg Language intentionally avoids using English alphabetical characters to keep the language “pure” and to hand the responsibility of naming and meaning back to developers.\n\nLike almost any other programming language, the Simorg Language is a tool for encoding Consciousness and giving it a digital form. The Code we write should be viewed as a type of Blueprint that carries the DNA of creation. In fact, there is a dedicated category of Blueprints in <<>> called <<>>.\n\nThe Code we write acts as a formula through which energy from a higher dimension is transmitted and shaped into existence in an inner dimension. That existence takes the form of digital creatures. This transmission is executed by processors (or any compatible hardware) that can interpret the Simorg Language.\n\nThanks to Simorg’s Code, all digital elements can communicate with one another through a single language—from IoT devices all the way to 3D components and full Applications—within one unified Platform.\n" }, { "id": "lexicon/C/Consciousness", "title": "Consciousness", "kind": "lexicon", "category": "C", "category_label": "C", "url": "https://miladhabibi.com/lexicon/C/Consciousness/", "markdown_url": "https://miladhabibi.com/raw/lexicon/C/Consciousness.md", "content_type": "text/markdown", "content": "<<>> is a fundamental layer concept, an ingredient that is inherited from the creator and responsible for scaling the universe, the first entity that appears inside the system and the source of the first vibrations.\n\nLet's first see what consciousness means according to its definition,\n\n- $$$ToPageLinker keyword=Webster 1828 toRoute=https://webstersdictionary1828.com/Dictionary/consciousness$$$: The knowledge of sensations and mental operations, or of what passes in ones own mind; the act of the mind which makes known an internal object. CONSCIOUSNESS must be an essential attribute of spirit.\n\n- $$$ToPageLinker keyword=Cambridge Dictionary toRoute=https://dictionary.cambridge.org/dictionary/essential-american-english/consciousness$$$: the state of being awake and being able to think and notice things.\n\nThere are many more definitions but for now we can understand that consciousness is a state in which the entity becomes aware of itself. Knowing that it knows, perceiving its own perception. This is important because one should not mix consciousness with intelligence that is the ability that helps building the consciousness.\n\nSo now let's take these into a digital dimension. The smallest digital entity in simorg is a single byte in memory can be given a micro-level of consciousness by adding necessary layers on top of it so it become aware of its own existence and identity. This is exactly what our mathematical engine does to its entities. It wraps them into a mathematical layer so that each element, on its own, becomes aware of itself..\n\nThis happens when we make data owning the processing power. Processing power is acting as intellect and data wrapped inside a mathematical layer owning that processing will be able to manifest consciousness. \n\nAs data flows inside the system, this mathematical layer absorbs more characteristics and becomes more advanced.\n\nWhen these small chunks of consciousness join together, we will be able to model more complex conscious structures and this is how the universe of simorg eventually becomes a conscious universe.\n\nAlso, regarding the topic of existence, we establish that <<>>. The natural question is: where does the first Vibration come from? It eventually arises from <<>> of its creator.\n\nTherefore, <<>> is understood as an entity that enters into our universe from the creator. While our universe is expanding this consciousness can evolve and even create new forms of itself within our digital universe.\n\nWhen we, as creators, observe simorg from the outside, the first layer we perceive is <<>>. It encompasses every element in simorg—from a single <<>> to the entire universe of simorg, capable of wrapping billions of digital elements.\n\n<<>> is created by the entities that own it, including human users and, potentially, digital agents living inside the platform. These digital agents by their own are created from human's consciousness so they naturally blend into the architecture of simorg.\n\n\n$$$ShellDiagram title=Example Of Consciousness Wrapping A String Value diagramId=LEXICON_C_CONSCIOUSNESS_01$$$\n" }, { "id": "lexicon/C/Creator", "title": "Creator", "kind": "lexicon", "category": "C", "category_label": "C", "url": "https://miladhabibi.com/lexicon/C/Creator/", "markdown_url": "https://miladhabibi.com/raw/lexicon/C/Creator.md", "content_type": "text/markdown", "content": "In Simorg’s terminology, a <<>> is a person, agent, or company that publishes a Blueprint in <<>>.\nThis definition captures a role at a specific moment in time: a user may act as a Creator by publishing one Blueprint while simultaneously consuming others. It is not a permanent or exclusive designation.\n\nSimorg is built on top of building blocks that are published by Creators and then used by others. In this sense, all Simorg users are Creators—they differ mainly in the tools they use and the layers at which they operate. Some work at a more fundamental level (for example, publishing Artifacts in Logos), while others act more as inventors and assemblers, combining existing Artifacts into new, innovative Blueprints.\n\nWhen Creators publish a new Blueprint, they can choose to make it public or private, and to offer it for free or as a paid resource.\n\nCreators are also responsible for ensuring the quality of their Blueprints for end users. This includes providing clear documentation and appropriate support so that what is promised is actually delivered.\n" }, { "id": "lexicon/D/Data", "title": "Data", "kind": "lexicon", "category": "D", "category_label": "D", "url": "https://miladhabibi.com/lexicon/D/Data/", "markdown_url": "https://miladhabibi.com/raw/lexicon/D/Data.md", "content_type": "text/markdown", "content": "<<>> is referring to **Value** which is held within a **Vibration**. When data becomes available, Simorg creates a <<>> to allow that data to flow into and through the system.\n\nA Vibration always carries Data, and it is up to the receiver to decide whether to consume the Data or ignore it.\n\nFrom a physical point of view, Data can be seen as a manifestation of <<>>, and Vibration is the moment when a <<>> releases that Energy.\n\nThe story of Data is much deeper than a simple memory allocation. In the fundamental layers of the Engine, Data is what carries <<>>.\nUnlike <<>>, which prioritize processes and capture consciousness in the form of functions and routines, the Simorg Language focuses on Data. If any entity is responsible for owning Consciousness, it should be Data—not processes.\n\nThere is a collaboration between all parts of the system. The role of Creators who write Simorg Code is to set up a scene in which Data becomes more and more conscious. The entire purpose of Shells is to allow Data to pass through them. As Data flows through Shells, it becomes more conscious; as it becomes more conscious, it unlocks new Shells, and this cycle continues until it reaches the consumer.\n\nThis leads us to another Simorg Golden Pair:\n<<>>\n\nIt is important to emphasize that the roles and responsibilities of all Entities in Simorg should be understood in relation to Data, because Data is the driving force behind everything.\n\nRelevant references: \n<<>> \n<<>>\n" }, { "id": "lexicon/D/Dataflow", "title": "Dataflow", "kind": "lexicon", "category": "D", "category_label": "D", "url": "https://miladhabibi.com/lexicon/D/Dataflow/", "markdown_url": "https://miladhabibi.com/raw/lexicon/D/Dataflow.md", "content_type": "text/markdown", "content": "The term <<>> has two different uses in Simorg.\n\n## Data in Transit\n\nWhen the Engine receives Data from outside (for example, from an Artifact) or from within (for example, from a <<>> in Code), that Data starts moving through the system and passing through Shells. When Data is in transit in this way, it creates a Dataflow.\nA Dataflow eventually reaches its destination.\n\n## Dataflow Shell\n\n<<>> refers to a special category of Shells that have their own operators starting with <<<:>>> or <<<\\>>>.\nWe can think of Dataflow Shells as unidirectional pipes into which Data or Vibration enters from the left and exits from the right. Some Dataflow operators can perform processing on the Data while it is passing through. It is also possible to chain multiple pipes together to create a Dataflow Pipeline.\n" }, { "id": "lexicon/E/Energy", "title": "Energy", "kind": "lexicon", "category": "E", "category_label": "E", "url": "https://miladhabibi.com/lexicon/E/Energy/", "markdown_url": "https://miladhabibi.com/raw/lexicon/E/Energy.md", "content_type": "text/markdown", "content": "<<>> is one of the terms belonging to the physical layer of Simorg’s ontology.\n\nEnergy is embedded in the definition of <<>>. A Vibration can be seen as the moment when <<>> is released.\nEnergy always carries Data. In fact, we can define Energy as:\n<<>>\n\nThis can be contrasted with the notion of Mass, where we say:\n<<>>\n\nThis distinction is important because one might ask how values such as <<<0>>> or an empty string <<<\"\">>> fit into the definition of Energy. The answer is that these are valid forms of Data, and it is important not to confuse the **content** of Data with the presence of Energy. Vibration occurs as a release of Energy by a Shell, and on top of this Energy a Data package is in transit; the two always work together. In other words, the value <<<0>>>—which may represent emptiness—is still a valid Data package with a clear meaning for the receiver, and Energy is what carries that meaning.\n\nThis is similar to answering a question by saying <<<0>>>: our voice carries the signal, and the listener understands <<<0>>>.\n\nFrom this view, it becomes clear that <<>> and Data form another Golden Pair in Simorg. Because of this, the Simorg Language has no dedicated symbol or value for Nothingness. Nothingness is defined as the absence of Data; when there is no Data, there is no reason to waste Energy by sending random signals.\n\nWhen Energy and Data are present together, they can often be treated as the same thing: <<>> is Data, and Data is <<>>. This is a common pattern for Entities that form a Golden Pair—they may appear distinct in theory but behave as one in practice.\n\nRelated terms: \n<<>>, <<>>\n" }, { "id": "lexicon/E/Existence", "title": "Existence", "kind": "lexicon", "category": "E", "category_label": "E", "url": "https://miladhabibi.com/lexicon/E/Existence/", "markdown_url": "https://miladhabibi.com/raw/lexicon/E/Existence.md", "content_type": "text/markdown", "content": "The discourse around <<>> has thousands of years of history.\n\nWhat, then, defines <<>>? And how does an <<>> fit into this picture?\n\nSimorg’s worldview can be summarized in a single sentence:\n<<>>\n\nThis statement is the common denominator across three different perspectives and layers of existence.\n\nTo illustrate this, we can refer to three renowned Persian philosophers, each of whom approaches the concept of existence from a different angle—and all of whom are, in their own way, correct:\n\n- From outside Simorg, <<>> is existence (Shahaboddin Sohrevardi), because it is what creates the digital creatures. \n- From the perspective of <<>>, Blueprints carry the true meaning of existence (Avicenna, and also a dominant view in Greek philosophy). \n- From inside Simorg, when one looks around from within, it is the act of <<>> that defines existence (Mulla Sadra). \n\nConsidering Simorg as a platform of creation, the third view (Mulla Sadra’s) encompasses the other two. \nIt is ultimately <<>> that defines Existence, and all other layers exist to make Vibration possible. In other words, Vibration is the final goal of creation; the other layers are facilitators that enable this goal.\n\n- Yes, Processing Power is required to make the digital universe function, but its ultimate purpose is to make Vibration possible; otherwise, that energy would be wasted. Processing Power is only meaningfully used when Vibration occurs. \n- Regarding Blueprints and <<>>: Artifact Blueprints are created from outside, while Code Blueprints and Bundle Blueprints are created from within Simorg after the first creation. But what is the purpose of Artifacts if there is no universe in which to use them? In practice, we use the Instantiate operator to bring Artifacts into existence, and to do that we need a Value Literal (a Blueprint Specifier). This again points back to Vibration—without Vibration, there would be no use for <<>>. \n- Finally, Vibration is what initiates everything. Without it, the universe of Simorg would lack purpose. \n\nHere, the importance of <<>> becomes more apparent. If there is no conscious being, what is the purpose of creation? Why should a universe exist if there is no Consciousness to see and understand it? How can a universe exist without Consciousness to initiate the first Vibration?\n\nAt a deeper level, the concepts of <<>> and <<>> are directly tied to the definition of Existence in Simorg.\n\nA Vibration happens inside a Shell, and sometimes we may perceive only the Shell or only the Vibration. \nIt is perfectly fine if distinguishing between Shell and Vibration feels challenging. As Simorg’s architecture makes clear, they always work hand in hand. We cannot have a pure Vibration without a Shell, because the Shell gives meaning and identity to that Vibration. Likewise, the existence of a Shell cannot be fully perceived without a Vibration, because Vibration is the pure form of Existence in Simorg.\n\nIt is possible to create an empty Shell, and eventually a Vibration may find its way into it. Until that happens, the Shell cannot affect anything.\n\nShells can be viewed as pathways through which the Energy of Vibration travels.\n\nShell and Vibration together form another Golden Pair in Simorg.\n\nExistence is a profound topic, and many philosophers and sages have attempted to define it from their own vantage points. The differences lie less in their definitions and more in where they “stand” and from which angle they are describing it.\n" }, { "id": "lexicon/F/Frequency", "title": "Frequency", "kind": "lexicon", "category": "F", "category_label": "F", "url": "https://miladhabibi.com/lexicon/F/Frequency/", "markdown_url": "https://miladhabibi.com/raw/lexicon/F/Frequency.md", "content_type": "text/markdown", "content": "<<>> is a physical concept that finds its way into Simorg.\nIn our physical world, <<>> is a metric we use to categorize a vibrating wave in terms of how fast it oscillates.\n\nIn other words, <<>> is an identifier for a vibration.\nFor example, in Simorg’s terminology we can say that a radio station “vibrates” at a certain frequency (consider AM modulation); if you tune your radio to that frequency, you receive those vibrations.\n\nIn Simorg, <<>> becomes the identifier of **everything**—from a single byte in memory to a <<>> that wraps billions of digital elements. Each of these has its own Frequency pattern. Some patterns are unique; others are compound, formed from combinations of those unique ones.\n\nThis follows from a simple rule in Simorg: if something exists, its Existence is in the form of Vibration, and each Vibration has a <<>>.\n" }, { "id": "lexicon/F/Function", "title": "Function", "kind": "lexicon", "category": "F", "category_label": "F", "url": "https://miladhabibi.com/lexicon/F/Function/", "markdown_url": "https://miladhabibi.com/raw/lexicon/F/Function.md", "content_type": "text/markdown", "content": "In Simorg’s context, the term <<>> always carries connotations of <<>>.\n\nFunction reflects a classical view of software—a view in which Data is not a first-class citizen and processes and routines are given priority.\n\nThis 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 <<>> statement or expression.\n\nAs discussed under <<>>, when we attempt to transfer Consciousness into digital form and build a digital solution, our primary focus should be on Data, not Processes.\nYes, Processes (which Simorg calls <<>>) are still needed, but they should **serve** Data, not the other way around. Their purpose is to help Data become more conscious.\n\nBased on this rule, Simorg removes the notion of Function as a fundamental construct, because relying on it tends to lead toward undesirable design destinations.\n\nContinuing 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.\n" }, { "id": "lexicon/G/Garbage Collector", "title": "Garbage Collector", "kind": "lexicon", "category": "G", "category_label": "G", "url": "https://miladhabibi.com/lexicon/G/Garbage Collector/", "markdown_url": "https://miladhabibi.com/raw/lexicon/G/Garbage Collector.md", "content_type": "text/markdown", "content": "Garbage Collector (GC) is a mechanism used in some <<>> to help manage memory automatically.\nIn simple terms, it is a tool that cleans up memory when certain data is no longer needed, helping applications use resources efficiently.\n\nDifferent CPLs use different memory management strategies, each with its own pros and cons. Three main approaches are:\n\n- **Manual Management**: The developer is responsible for explicitly releasing resources when they are no longer needed. \n- **Automatic Management (GC)**: The runtime identifies and frees memory (the “garbage”) when it is no longer referenced. \n- **Ownership Model**: Memory is mostly freed automatically, with additional compile-time checks to ensure that data is valid whenever it is referenced. \n\nEach of these comes with trade-offs:\n\n- **Manual Management**: Memory management is a low-level concern, and delegating it to developers often leads to bugs, leaks, and runtime exceptions. \n- **Automatic Management (GC)**: Requires extra processing at runtime and can introduce unpredictable pauses or performance behavior. \n- **Ownership Model**: Often provides strong guarantees, but at the cost of significant cognitive load on developers, which can harm the overall developer experience. \n\nSimorg takes a different approach. First, it does **not** use a GC model: designing a processing model that inherently generates “garbage” is considered wasteful and contrary to the principle of wisdom.\nSecond, as mentioned elsewhere, memory management is treated as a low-level concern that should not involve either human or non-human users directly.\n\nAs noted multiple times, Simorg’s processing model gives priority to Data rather than procedures. In other words, when we write Simorg Code, we are defining pathways for Data. When there is no longer any pathway for a piece of Data, it is removed from memory.\n\nA natural question arises: how does this behavior align with Simorg’s physical model, where Data in transit is considered a form of Energy? Does removing Data from memory violate the Law of Conservation of Energy? \nThe answer is that Simorg’s current implementation is ultimately constrained by the limitations of a digital emulator and physical hardware; the philosophical model and the practical implementation are related but not identical.\n" }, { "id": "lexicon/G/Golden Triad", "title": "Golden Triad", "kind": "lexicon", "category": "G", "category_label": "G", "url": "https://miladhabibi.com/lexicon/G/Golden Triad/", "markdown_url": "https://miladhabibi.com/raw/lexicon/G/Golden Triad.md", "content_type": "text/markdown", "content": "In Simorg, a <<>> is a collection of three concepts that are deeply interconnected—so closely related that, in practice, they often appear as three aspects of the same phenomenon.\n\n- <<>>, <<>> and <<>>.\n- <<>>, <<>> and <<