EATSv5 PHP Framework
EATSv5.2020 (PHP 7+) is based on the v1.08, PHP 5.2, version of the EATS code which was then migrated to form the Java code defining core EATS v4.6 behavior and processing attributes, and now re-merged as a PHP framework. The v1.08 version was evolved from the original PHP 4 framing of EATS, which was developed in conjunction with the establishment of Architected Futures in 2005 as an organizational scheme for development and stewardship of the conceptual framework. The concepts embedded in the work are based on a consistent thread of activity along a singular axis of pursuit and investigation that include 35 years of software engineering for Bank of America involving both Capital Markets and Bank Investment Portfolio Management, and geographically distributed retail banking that closely matched the path of automation of the financial industry. Direction, intention and motivation can be traced to the 1950’s, and futures-oriented visions inspired by Sputnik and Willy Ley. It is based on a relational framing of the association between person (me) and machine (an evolving series), as it relates to computers and automation and possibilities, which was partially formed in 1964/65 related to a Litton Monrobot XI 1K magnetic drum memory computer. Remaining inspiration came from Tom Swift, The Hardy Boys, Issac Asimov, Arthur C. Clarke, Galt MacDermot and Gene Roddenberry before George Lucas. Lessons learned from the Monrobot XI:
- A slide rule was much faster to compute a quadratic, but a slide rule didn’t have a facility to remember intermediate results that were not part of a continuous stream of calculations. A slide rule was also easier to manipulate the parts to perform the calculation than it was to use the TTY console on the computer.
- Garbage In, Garbage Out. Broken Hardware, Garbage Out. Garbage Logic, Garbage Out. Instructions need to be exact and precise and single step serialized.
- Algebra and Geometry can be easy and fun when using delegating to the Monrobot for the Trig, angle degree calculation, and detail measures to necessary degrees of significance for useful engineering purposes.
Programming an HP-97 was a huge improvement on the Monrobot and it could function as a user programmed calculating machine to determine financial arbitrage on foreign currency transactions and interest rate swaps. Before the IBM PC, there was the S/100’s and CP/M. Before the blur that came from chip optimization there were distinct classes of computing based on hardware and physical characteristics, and each realm had its own functional space: mainframe, mini and micro computers that roughly correlated to big business, smaller business and personal computing. The IBM PC moved personal to “individual” and made the microprocessor into business computing too. Peripheral devices used to be things business bought for users and customers to interact with big business, for the benefit of, and toward to objectives of, the business owning the computer behind the devices. It started with credit card embossing machines as “cash out” vehicles for transactions, book-keeping in the cloud as a replacement for cash.
The objective of EATSv5 is to form a merged stream of consolidated code which includes both Java and PHP components interacting as a single unit where all perspectives are aligned from the same observational and operational point of view. Either unit should be useful in its own space, and the two together should form a tightly-integrated arrangement:
- PHP forms the base of the adaptive user interface, user-friendly, user-code space, outer shell of the EATSv5 Borg framework, prototype introduction to an automated “Robo-Alternate-Self”; what human life will drift toward as we process forward in time.
- The Eclipse bus-based ecosystem shell provides the core technology that provides technical structure to the arrangement, and provides the scheme for evolutionary technical superstructure for continual infrastructure refinement1Duration is a function of both need and capability. To be effective, capability needs to outlast need. If need is beyond the reach of capability, a substitution technology is required to sustain need..
Binding between the two comes in part from a loose cohesion inherited from Eclipse as an adopted umbrella ecosystem for the system’s technical architecture. The Eclipse IDE is a plug-in ready open source platform that executes on most computing architectures and platforms and has been adopted by NASA as a standard component for remote space-based technology, such as Mars Rovers. (See also ECLIPSE.)
Communication in EATS is via messages. Logic units, algorithms, are based on an asynchronous, message passing, framework in which conscious processing of units of an algorithm are suspended and resumed by a benevolent superstructure.
All business logic algorithms in EATS are programmed as event notifications, via messages, where every algorithms has a defined context of application relative data requirements, triggers, and notification transaction consequences.
Control over relational logic in EATS is implemented at the super-system level, not by the individual components which have the relationships. All interaction between business logic components and the environment is capable of being achieved through infrastructure API resources, which in turn provide full management, audit and analysis frameworks over the related capabilities and functionality.
The original PHP code was developed using O-O concepts under PHP 4 and constructed as an extension to the Tiki-Wiki CMS. That code was used to boot-strap a standalone, generic, table driven LAMP/WAMP server instance. v1.08 of the code included a revision of the OO structure to include Classes provided by PHP 5. It was then used to construct the original core AIR knowledge-base still used by the various iterations of the system.
v1.08 defines the most recent PHP code set conversant with the AIR information structures. Subsequent PHP developments were focused on “community-oriented” aspects of information sets and capabilities sharing between involved parties. Thus the focus on Drupal and WordPress as tailor-able information sharing ecosystems where end-users can be, and are, developers of content and practices for reuse by others. Drupal and WP are built for sharing, similar to the original WWW, and HTTP. Both tools have been used to move EATS documentation online. EATSv5 is intended to be used in three Use Case Scenarios:
- Use as a Standalone PHP Tool
- As a web-based resource
- As a desktop resource
- Use as a WordPress Plugin
- Use as a Drupal Module
EATSv5 is based on the concept of an integrative feedback loop, which unfolds in a Fibonacci pattern for the management and use of automated systems to assist humans with collaboration and knowledge sharing. Knowledge sharing is an expansive human aspect and shares aspects with experience sharing.
EATSv5 is a set of software algorithms and digital information. The digital information includes the algorithms. As such it forms a conceptual unit which can loosely be terms a computer application, following a technical architecture. Architecture, like other terms used in EATS, is an abstract concept that is used as a harness to encapsulate an idea that exists individually in some peoples heads. Some is a logical term meaning more than zero, and less than all.
People don’t normally think this way, but to properly program a system, that is how it is done. You break big things down into chunks that are smaller and smaller until they become manageable to grasp and handle. Deductive analysis and division is how we physically solve problems involving physical substances. We separate conflicting parties. We smash atoms. You break things down to parts you’ve seen before and know how to deal with bigger things that are not understood, or you just ask some “other” to tell you how you should think. Then you follow tried and proven methods which we’ve refined to nano-engineering: smooth out rough planes, keep passageways free of foreign objects. Establish control ranges and corridors, differentiate between fast, low-hanging and near-term versus other that can be postponed. Resolve pain and solve problems by performing work which exchanges the concern or problem for a set of smaller concerns. As humans we have learned to perfect triage and becoming the ultimate predators, such that we only have ourselves to fight with. For pride of superiority? It’s not for societal, social, physical, economic advantage anymore, not really. We’re pretty exchangeable and interdependent as humans relative to economics, except for who gets to be called owner, and the definition of roles and responsibilities around stewardship.
Enterprise architecture struggles to gain traction as a cohesive function within organizations because people have not been fully incorporated into the recursive architecture of which they are a part. John Zachman’s framework is an excellent tool, but it focuses on conceptual development in the absence of actual physical operation and defines a static form of what is a dynamic process. Nature never grows the same tree twice, and all human experience is unique. Institutional order fails, in part, when it thinks people and enterprises are different things, and it ignores the fact the both are systems, and people can not, and should not, be be treated as mechanical devices, machines. Nor will machines ever fully function as holistic, competent humans.
The EATS PHP Framework is limited in capability by virtue of its position in the overall processing framework. PHP, by design, is a web server request-response scripting facility. The web is by design, when using HTTP, a request-response machine without session memory. PHP allows the response to the request to be determined through an interpreted scripting language, rather than a compiled program. The difference is a function of how trade-offs are made in automation processes to optimize either the human-interaction or the machine performance aspects of any functional, computer data processing application system. Personal utility needs and wants to make the machine interactions as rich as possible to fit within the life experience and focus of the human user. Industrial utility wants to optimize performance and efficiency. Industrialized efficiency singularly optimizes for time, regardless of production unit. It makes no distinction between raw materials and means of production as cost elements, and no distinction between machines, animals or humans as means of production. People operate on circadian cycles. The technical challenge for the EATS framework is to construct, within a virtual machine, a concept of how to respond to any particular web process request which is directed at the framework within the processing capabilities of an active web server by and for the intent of the person using, interacting with, the system.
Most software is developed from a two-point perspective. There is a front and back to the glass, and the software facility; and an inside and outside to the system which are designed as walled-off separate spaces. This evolves from what was once a Glass House view of computers and automation from an institutional basis; but ignores the home brew industry which created the IEEE S100 birthplace for the IBM PC, which is the personal automation progenitor of the smartphone owned by most members of Planet Earth’s human population. Usenet was personal, informative and productive for the users; the internet is impersonal, invasive, and beyond the control of its users. The suppliers have permeated the space with push advertising to the point of ruination. Spell check is now the job of the human, to correct the correction made by a program, designed to sell advertising, that changes perfectly spelled words to different words with other meaning which do not resemble what was intended to be written. Catch it when you can, you can’t catch them all!
The two point perspective is valid and needs to be dealt with in an engineered world, but engineers should not be totalitarian dictators when dealing with humans as customers. And, the totalitarian dictator concept doesn’t work well with Mother Nature, either. Gassing methane to cheapen the short-term price of oil because you can is not the proper approach to sustained enjoyment of the human experience. And doing things faster, isn’t always better; nor is producing more, if your just going to trash things for which demand did not exist to meet your hopes and desires. Supply side is not natural. Overproduction isn’t the path to rolled-through yield. TAKT time and pacing matching supply to demand flows generates more effective processes.
EATS is based on a three point perspective which adds the ongoing developer innovation perspective and frames the engineering with a dynamic, recursively regenerated architecture. It also changes the priorities of the viewpoints. In the two point perspective, the user of tech is the object of targeting by a totalitarian engineered effort bought and paid for, typically, by an institution entity (the supplier of the tech). Supply side, supplier controls technology provided to (user) consumer. Supplier has position of power and priority of needs and wants accomplishment. In the three point, home brew, perspective, suppliers priority to consumers. Pioneers are people capable of self-support. Kit Carson. Daniel Boone. The third perspective is EATS is created by supporting a primary perspective that is malleable can can be morphed onto either side of the old Glass Wall by stepping through the glass to fine tune whichever side makes the most sense toward the most effective utility. Just like with cars before we loaded them with transistors, when basic mechanics of engines and knowledge of how to change a tire were more than useful things to know when driving; learning how to train systems, automated and otherwise, do what is desired, rather than the training they get from their suppliers, is something future individual persons are going to want to learn early, and do often.
The primary difference between the EATS PHP and Java frameworks is packaging and the mechanisms available for handling of conversational threading. The EATS Java framework is built inside an Eclipse instance inside a JVM. The EATS PHP framework either runs directly inside a PHP “front-end” web server, or is embedded as part of a WordPress web site. The Eclipse ecosystem implements a more formal back-end server. The PHP ecosystem implements a front-end processor configuration. Back-end servers tend to focus on information as object. Front-end processors tend to focus on information as transactional exchange.
- AF WP Plugin Modules
- EATSv5 PHP
- MDA Code Generation
- WordPress Hooks