Building the Enactment Engagement Language Stored Program: Leemapper.

. This is about the necessary requirements needed to build an application of Lee class structures. The requirements look at the parameters needed to have a functional logic system. This is on Leemapper application and details of execution as outputs are also shown.


Introduction
Leelus [6] is a typed language theory for interpretable artificial intelligence method for multi-agent perspective. This is based on the Object-Oriented C++ [1,2,3,4,5] language. In describing, readers will be looking at application constructs as instance classes. There are only three variables in the language argumentation. The argumentatives includes action, location and temporal with a variant type still including three arguments-rank, interest 1 and interest 2.
The action, location, rank and two interests are of character type dimensioned in array. It is programmed as a pointer definition. I will now described programmed actions with four values in namespace: action a="buy", a1="sell", a2="sold", a3="trade"; The first programmed action declared as a is an equalisation of "buy" action. This action is both a business and economics term. A buy action is used to describe a process of buying a good or service or both (good and service). The second programmed action is declared as a1 and it is an equalisation of "sell" action. Sell action is used to describe a process of selling a good or service or both. The third programmed action value is sold and it is declared as a2. It is used to indicate whether a good or service is sold or not. The possibility of both (good and service) can be also be evaluated to sold action. Sold is the past tense of sell.
Sold places a past action on something that sell as goods or services. Sold goods are less current and likely of a future condition of never getting a sell action again. Sold can be reversed unless the item or good is returned. It will create an unsold action in protecting terms. Validity of return is a warranty on a sold good or service. Validity is specified in temporal means and I will attend to it later. Validation of warranty is required to be in the specified time between the sold date and warrant date. After the warrant date makes the validity of return invalid and guarantee notice removed from the period. This policy of warranty is a temporal nature of sold goods/services. Invalid return of goods create a programmed unsold action to change to "invalid_return" action. The final programmed action is an equalisation of trade value declared as a3 variable. The value of trade is normally pursued as tradepaper by the author's experience. Here, an author or writer trades a book made of Papers to an organisation to sell on their behalf. Mostly, on split percentage of buy value in currency specified during the agreed price.
The next set of programmed interests are described in terms of their value in the program.
The code for declaration is as follows : interest ia="sell_pc", ia1="buy_pc"; Two values of interest are used in the program namely : sell_pc or buy_pc.
This means that an agent has value if the entity sells pc or either buys pc. Buy is the anti-sell and vice versa.
On the business side, interest is a return value on investment denoted by a principal value period in some year(s) at a certain percentage limited to 100%. Again in such ways, what is the interest of an agent in business? This is a means to evaluate the interest of an action to another. What is interesting in doing such business with you? Agent asks an organisation.
In this present situation, the equalisation of interest value, "sell_pc" is declared as ia. The value of interest is having to be used to describe an agent that has interest in selling PCs at their entity. With this interest, an agent believes to generate some return of investment in the entity just by selling personal computers(pc). The second interest value is "buy_pc". It is declared as ia1. An agent has interest in buying a PC and will stay in business if the entity continues to do so.
An agent can do both buying and selling PCs. There are three terminologies in describing this. These are business, economics and commerce. I will leave you to find it out. The focuses are in E-business, E-agent and E-commerce. Doing business over electronic domain will place focus on E-business (Business-2-Business and more). EEE-CAB or E^3-cab is the abbreviation used in describing all the focuses of an agent doing buying or selling and both selling and buying.
Businesses cannot stay relevant at all times. It is important to rank them to store the value of their rank in such a process. The value of rank for an agent to stay relevant to an organisation interested in delivering always or sometimes quality of service is required.
Quality of service is required in doing business at the highest level and as such it is catered for by the rank value. The declaration of rank is coded as follows : rank r="rank_9"; A single rank is declared in this program. It is declared as r. The rank is a numeric value but here the number is used after an underscore. A business which scores 9 is better off than another which scores 12. Hence, a lower rank value is better off in terms of doing quality of service than a higher rank entity. Given a table of ranks in a period of annual competitions : Location is required to have any action done. Without location, directions can be made in any physical universe. A building in even a physical universe can give direction to a location of situational action.
We are looking at two locations in this coded program. It is programmed that declared loc is valued at Tottenham for an agent to do business. This is the first location value.
The code of location in stored program is as follows : location loc="tottenham", loc1="London"; The second declared variable is loc1. It has a value of "London". This again situated action Doing business cannot be a permanent activity. Holding to do business with an agent in an agency is temporary in some sense. After a certain period of time limits an organisation in doing business with the agent company. That requirement demands a stored temporal value to hold business going until otherwise. On elapse, business stops to other matters until further agreement is signed. Contract by agreement between agent and entity is required to complete in a closed location before opening another business day. The expected commissions necessary on demand by both parties is of importance. The declared variable in temporal dimension is temp and it is coded as: temporal temp="Sat 12/09/2019 12:00pm"; The temp value is Saturday 12/09/2019 12:00pm. The agent can begin to do a buying action or selling action before or after the declared day of doing business. Entity might cease to work if the declared temporal value is elapsed. Again might start to do business with agents after the elapsed. Always or sometimes or never calculi on temporal value might be a requirement on the specification of logic programs.

Setting Variables in Coded Program
In order to run the program, it is required to set the variables above in section 1 to the object classes. The 6 classes are Enact, Enactage, Isimplies, enactEL, locationact, interestact and temporalrank. The methodized setLEEValues is algorithmitized as:

Conclusion
This is about building an application by Lee classes. In this work, I did describe the variable declarations needed as requirements in successfully creating an application. The details of Lee values are thoroughly discussed on its relevance in starting a functional logic program. This is a stored program in the sense that the program has all its functionality initially valued at default. No further changes to the program during execution unless it is changed and recompiled. The 12 logic program details are omitted for now but the exact functional name along the functional method are enumerated in simple format. The source code can be accessed at [9]. The screenshots of output are shown.
Further Reading