Entity Data Structure:
This is a data construct. It has a header which identifies the specific subvariables necessary for processing that particular entity. The design is meant to allow abstract comparison between a varied about of data constructs specific to each entity archetype. Each object in MACRO computational theory has various properties and attributes which are stored in memory or hard disk. It in essence has a handle in order to make these various data structure archetypes comparable. Even functions can be stored as entities. Everything is an entity and this is designed to make them all accessible on the same level of abstraction.
The Framework of Knowledge:
This is a handcrafted template for storing information. It is an extension of the entity data structure. In it are relational definitional that serve as a basis for entity comparisons based on their properties and what realms of existence they exist within. It is a directory system wherein the folders are general entity entries and their contents are the data pertaining to the specific instances of these entity. For example there will be an entry for human beings. First the general entry which describes what a human being is then listed under that are specific entries for each person that the machine comes into contact with or learns about.
Virtual Evaluation Environment:
This is the arena of processing in the MACRO construct. It is the framework which processes entities. It first loads all the entities in an environmental set. It then extrapolates the possible functions that can be applied to those entities, this includes resolution queries and hypothetical manipulations. The VEE assembles an abstract environment. A major component of VEE processing is abstracting it exploration of entity potentiality and the implications of this potentiality in potential problem solving. Multiple instances of the VEE can be run simultaneously and communicate with each other. The main program is an enhanced VEE that holds all entities and functions that pertain to the system.
This is a partially handcrafted but also live system. In it are stored task priorities and some basic guidelines about determining what ends the program is trying to reach. If there are the three laws of robotics this is where they would go. It is fundamental in establishing long term processing and existence of the AI. The default course of action is to wait for user input until the machine is given more complicated tasks to manage for itself.
This is the core of any VEE instance which decides what to do next based the motivational hierarchy, the journal system, and input to the system. Much of the program flow is built into this circuit. It starts as a list in the boot sequence establishing the primary VEE. Then gets fed by the journal system if there are previous entries, then the motivational hierarchy comes into play, and then there are returns from the VEE processes.