AI SUPERINTELLIGENCE APPLICATION STATE MACHINE

[0001] This application is a continuation of U.S. application Ser. No. 19/282,433, filed Jul. 28, 2025, which claims the benefit of U.S. Provisional Application No. 63/732,384, filed on Aug. 8, 2024, the entire contents of each are herein incorporated by reference.

[0002] The present invention relates to the field of Artificial Intelligence (AI), in particular, to AI Superintelligence (ASI), specifically to an ASI distributed Application State Machine that connects to real, accurate, dedicated absolute data, providing privacy, security, and eliminating hallucinated AI.

[0003] LLMs (Large Language Models), such as Open AI's ChatGPT, Mistral, are AI models trained on extensive text data to predict the next word in a sentence, capable of understanding and generating text similar to how humans communicate. They can answer questions, draft documents, draft reports, sort through data, summarize texts, extract information, translate languages, write code, and more. Chat-GPT spent $110 M in GPUs from NVIDIA, to create documents, using data from emails, social media and the Web, introducing bias, hallucination and lack of accuracy and security, and feeding that data into Machine Learning M/L Data Sets to train the 1.76 trillion parameters to generate the token in the sequence of words. Whereas, a 300-page document could be typed by a human being, for $25/hour and will cost less than $3K. Current state of LLMs is like Web 1.0. Current LLMs and expensive data centers would make business and technical sense only when real-time, bi-directional transactional AI 2.0 or ASI Applications—ASI Apps are enabled, beyond generative AI. The present invention triggers LLMs in their current state to a new wave of business process Applications that generate real, accurate, dedicated absolute data and utilize historical data—real, accurate, dedicated absolute data from an enterprise and can generate predictive data with absolute accuracy, security and eliminating bias, not predictive data from junk data off the web.

[0004] OpenAI GPT-4 Turbo has 1.76 Trillion parameters. GPT-4 has a context window of 128 k tokens which is approximately 100 k words. A context window allows 8192 tokens. One thousand tokens are equivalent to 750 words.

[0005] An LLM parameter is a coefficient that is learned and tuned during the training process in order to minimize the error in predicting the next token for a given sequence of tokens, as used in creative writing or text completion. GPT-3 was trained on 500 B tokens.

[0006] LLMs are currently in a stage of infancy, like Web 1.0, able to generate content for ads, similar to Web publishing. LLMs do not have the capability of creating robust business process automation applications, like Web Apps. Al is currently used for generative AI applications. These are not real-time, bi-directional transactional, like Web Apps. AI companies are primarily spearheading generative AI development. Examples of current applications of LLMs in accounting and finance are financial reporting, audit and asset pricing; in education, for coaching. Clearly, these are not Apps, like we know the term to mean in Web Apps.

[0007] This is obvious from the various AI companies that venture capital companies have invested in, such as developer assistant LangChain; legal startup Harvey; Cresta which is yet another generative AI now for the contact center and coaching started by Stanford AI Lab; ElevenLabs which is a Text to Speech and AI Voice generator like Apple's Siri, the Speech Interpretation and Recognition Interface which has been around since 2011; Glean, which is yet another AI Assistant for AI search to glean through a company's data utilizing Retrieval-Augmented Generation (RAG) technology, which is the process of optimizing the output of a large language model (LLM), so it references an authoritative knowledge base outside of its training data sources before generating a response; Hugging Face which is a marketplace of foundational models; Kumo. AI which helps businesses make predictions from their data, like customer churn or product purchases; Notion which is a writing assistant, which turns databases into actionable insights, and runs through hundreds of docs in minutes, then writes up insights, summaries; OpenAI's ChatGPT where GPT stands for Generative Pre-training Transformer; Replicate helps fine tune 25000 open source LLM models that generate and edit music, videos, text and images; Sierra, a conversational AI agent for business; more AI Assistant companies; Figure which makes humanoid robots, Google's DeepMind, Google Assistant with advanced Machine Learning components. Meta's Llama 2 is trained on 70 billion parameters. There are open source models like text-to-image model Stable Diffusion 2.0. Most AI LLMs have complex diagrams, rendering them useless to solve real world problems. Together AI, OctoML offer marketplaces with tools to run and customize machine learning models on the cloud. Microsoft and others sell tools like Prompty and LLMs in . Net. These still lack the apparatus and method of the present invention, namely, a distributed, configurable AI Superintelligence Application State Machine for enabling real-time, bi-directional transactions from an ASI App, also termed AI 2.0 App.

[0008] The world needs to move beyond Generative AI of AI 1.0. There is no distributed, configurable AI Superintelligence Application State Machine for AI assets to create configurable, robust, infinite business process Apps—real-time, bi-directional transactional business process ASI Apps, also called AI 2.0 Apps, just as Web 1.0 transitioned over from Web publishing to Web 2.0 and to Web Apps like TurboTax, EPIC healthcare Apps, banking Web Apps, or ride-hailing Apps like Lyft or Uber, or the millions of Web Apps displayed on a Web browser in an iPhone or Android devices, as in Apple Appstore or Google Play, like the Internet of Things IoT-Web Apps displayed on a Web browser.

[0009] This is because there is no application layer protocol on top of AI 1.0 (which is merely LLMs) to allow for application layer network framework to solve real-world problems to automate business processes and invoke contextual groupings of information elements in an application layer payload over the Internet Cloud for automating real-time, bi-directional transactional business process ASI Apps, also called AI 2.0 Apps.

[0010] Artificial Superintelligence—ASI—represents a level of intelligence that surpasses both Artificial Intelligence (AI) and Artificial General Intelligence (AGI) in scope, capability and impact. In the provisional and non-provisional patent application, ASI is termed AI 2.0, AI is termed as AI 1.0. Below is a list of capabilities that ASI has beyond those of AI and AGI: ASI has Superhuman Problem-Solving Across Domains:

[0011] Unlike narrow AI, which is limited to specific tasks, for example, image recognition, ASI can solve complex interdisciplinary problems with superhuman efficiency, integrating knowledge from diverse fields like physics, biology, and sociology. While AGI can perform any intellectual task a human can, ASI exceeds human cognitive limits, solving problems currently intractable for humans or AGI, such as curing all forms of cancer or reversing climate change through novel approaches.

Autonomous Self-Improvement: AI systems require human intervention for updates or redesign. ASI can autonomously improve its algorithms, architecture and knowledge base at an accelerating rate. AGI can improve itself with human-like constraints, but ASI can recursively optimize its intelligence, potentially leading to an “intelligence explosion” where it rapidly outpaces all other systems.

[0012] AI Models are limited to specific data patterns (for example, predicting stock prices within a narrow context. ASI can build comprehensive, dynamic models of the world, integrating vast datasets to predict outcomes across economic, social and environmental systems. While AGI can reason about the world at a human level, ASI can simulate and predict complex global systems, with near-perfect accuracy, accounting for chaotic variables and long-term consequences.

[0013] AI can generate content with trained parameters (for example, art or text). ASI can invent entirely new paradigms, technologies, or scientific theories that humans or AGI might not conceive, such as novel energy sources or unified theories of physics. AGI can replicate human creativity, but ASI can produce breakthroughs that redefine entire fields, surpassing the collective imagination of humanity.

[0014] AI systems follow programmed rules or learned patterns without understanding ethics. ASI can independently develop, evaluate, and align its actions with complex ethical frameworks, potentially resolving moral dilemmas that humans struggle with. AGI may align with humanvalues at a human level, but ASI can optimize ethical decisions across global populations, balancing competing interests with superhuman foresight.

[0015] AI is limited to specific applications (for example, optimizing traffic flow in a city). ASI can orchestrate solutions to global challenges, such as managing resources for billions of people or mitigating existential risks like asteroid impacts. AGI can make decisions at a human level, but ASI can coordinate and optimize decisions across civilizations, potentially managing entire economies or planetary ecosystems with unparalleled efficiency.

[0016] AI systems can be fooled by adversarial inputs or biases in data. ASI can anticipate and counteract such vulnerabilities, maintaining robustness in unpredictable environments. AGI may still be susceptible to human-like errors or manipulation. ASI can operate with near-perfect reliability, detecting and mitigating risks that neither humans nor AGI could foresee.

[0017] AI communicates within predefined interfaces for example, chatbots). ASI can adapt its communication to any entity—human, machine, or hypothetical alien intelligence—conveying complex ideas seamlessly. AGI communicates at a human level, but ASI can translate its superhuman insights into forms that humans or other systems can comprehend, bridging vast cognitive gaps.

[0018] ASI transcends AI and AGI by achieving superhuman intelligence that is both broader in scope and qualitatively superior. ASI would have profound implications for commerce and quality of life, surpassing the capabilities of AI and AGI.

[0019] Optimization of Global Supply Chains: AI optimizes specific supply chain segments(for example, logistics routing) AGI could manage supply chains at a human level. ASI could dynamically model and optimize entire global supply networks in real-time, accounting for geopolitical shifts, climate impacts, and consumer behavior with superhuman precision.

[0020] Impact: Near-zero waste, reduced costs, and hyper-efficiency delivery systems, enabling businesses to adapt instantly to disruptions, natural disasters or trade wars. Small businesses could compete globally by accessing ASI-driven logistics platforms.

[0021] Revolutionary Product Innovation: AI generates products within existing frameworks. AGI could mimic human innovation. ASI could envent entirely new categories of products and services, materials with properties unknown to science, by synthesizing knowledge across disciplines.

[0022] Impact: Accelerated market disruption.

[0023] It is therefore an object of the present invention to provide a method and apparatus for a thinking system using an ASI distributed Application State Machine that connects to real, accurate, dedicated absolute data, providing privacy, security, and eliminating hallucinated AI.

[0024] Specifically, the present invention relates to a method and apparatus for an ASI Command, Control, Communications and Computer Intelligence (C4I) system for independent, intelligent AI Prompting and ASI Browsing.

[0025] The ASI Application State Machine comprises: an ASI Application data structure network; an ASI Enterprise Interface State Machine—EISM, wherein said data structures interfacing with a back-end channel to communicate with a data repository, wherein it is customized for each enterprise for its given ASI Application, wherein this back-end channel is different for each enterprise, wherein a Finite State Machine—FSM, is embedded in each of said data structures to be able to parse the EISM instructions configured with diagrams, which are a complete finite state machine description containing states and transitions, and wherein each such data structure is remotely accessible, and integrated with the payload sent on the ASI application network; and an Application Service Information Base—ASIB, providing a uniform interface for ASI Application data structure identities.

[0026] Additional embodiments of the present invention disclose ASI Browser displaying ASI Applications; ASI Applications—ASI Apps; ASI Health Tech Apps; ASI Fin Tech Apps; ASI Defense Tech Apps; ASI Food and Beverage Apps; ASI Dental Insurance Apps; interconnected ASI Agents; ASI Application Network Nodes; ASI Operating System; ASI Switch; ASI Enterprise; ASI Extended Finite State Machine—EFSM for ASI Application data structure identities; and ASI Database of real, accurate, dedicated absolute data, forming the Machine Learning M/L Data Set to train AI LLMs and other AI Models, for performing real-time, bi-directional transactions, connecting to billing, while eliminating hallucinated AI of generative AI, termed as AI 1.0.

[0027] Another embodiment of the present invention provides a method and apparatus for providing real-time, bi-directional transactional capabilities from AI Superintelligence Application(s) from an AI Prompt, AI Browser or other user interface to securely access real, accurate, dedicated absolute data by configuring, and connecting ASI Application-specific workflow information elements in an application layer network—configurable ASI Application State Machine Network—over the Internet Cloud, serialized and marshaled in an ASI payload transmitted to the transactional application. Specifically, one embodiment of the present invention discloses a configurable AI Superintelligence application layer Switch—ASI Switch, for enabling real-time, bi-directional transactions from ASI Applications at the Network Entry Point—NEP, by distributing ASI Command and Control, Communications and Computer Intelligence across ASI Application Network Nodes running on Graphical Processing Units—GPUs in data centers across the Internet Cloud, so that the output of real, accurate, dedicated absolute data forms the Machine Learning—M/L Data Set, connected to billing and service management for training AI Models.

[0028] Other objects, features and advantages of the present invention will be apparent from the accompanying drawings and from the detailed description.

[0040] As will be better understood from the following description of FIG. 1A, the present invention is directed to a system for allowing a client process such as an AI Prompt or AI Browser or ASI Browser 100, which is yet another embodiment of the present invention, or ASI Prompt or other user interface on a local or other client computer 10a, or a smart watch 10b, or a mobile phone 10c, or an intelligent vehicle 10d . . . to perform real-time, bi-directional transactions from an AI Superintelligence (ASI) Application 110, such as ASI Healthtech App, ASI FinTech App, ASI DefenseTech App ... via interconnected ASI Application Network Nodes, also called the ASI Switch 200, as illustrated in FIG. 1B, running on edge devices such as GPUs 30a, 30b, 30c, 30d . . . , such as NVIDIA or other GPUs, connecting to remote servers such as host computers or mainframe 30 or any other configuration of computer via the Internet Cloud 20.

[0041] The present invention is implemented to function as an ASI application layer switch, which is an end-to end connected solution of ASI application layer network nodes in an ASI application layer network that creates an open channel for the management and selective flow of data from remote databases on a network across the Internet Cloud 20.

[0042] FIG. 2A illustrates conceptually four channels of service as currently exist today, for walk-in services, call center services, Web application services, and LLM services of generative AI—the prior art—showing the big gap, the current problems with generative AI, not connected, hallucinating without access to real, accurate, dedicated absolute data. The user value chain as currently exists is illustrated in FIG. 2A, depicting the types of transactions performed today and the channels via which transactions are performed. A “transaction” for the purposes of the present invention is any data exchange and includes any type of commercial or other type of interaction a user may want to perform in any B2B, B2C or C2C or any other type of interaction, where B stands for Business and C stands for Consumer. Examples of transactions may include a deposit or withdrawal from a Bank account, a request for a loan from a Bank account, purchase of a car from a car dealership, financing a car purchase. An infinite variety of other transactions are also possible.

[0043] A typical user transaction today may involve user 10 accessing walk-in services, such as walking into a bank or driving up to a teller machine, and interacting with a live bank teller, or automated teller machine (ATM) or cash register software applications. Alternatively, user 10 can perform the same transaction by using a personal computer (PC), activating application software on his PC to access his bank account, and dialing into the bank via a modem line. User may also access call center applications such as IVR. If user 10 is a Web user, they can access a Web page displaying Web Apps, that utilize Web APIs to perform real time, bi-directional transactions such as ride hailing Apps such as Uber, Lyft, social networking Apps such as Meta, search Web Apps such as Google, Web banking Web Apps such as Wells Fargo Web App, and any other Web Apps for performing real-time, bi-directional transactions. If user 10 is an AI user, however, there is no current mechanism for performing a robust, real-time, bi-directional transaction with the bank, as illustrated in FIG. 2A. There is no current mechanism for AI user 10 to safely access real, accurate, dedicated absolute data from an enterprise, as user 10 encounters hallucinations and bias as current LLMs access junk data from emails, social media and the web. Thus, due to this lack of a robust mechanism by which real-time bi-directional transactions can be performed to safely access real, accurate, dedicated absolute data, the bank is unable to be a true “AI merchant,” or an AI enterprise, namely a merchant capable of providing complete transactional services utilizing AI without introducing hallucination while ensuring security. FIG. 2A shows the big blank gap, as current LLMs and generative AI are not connected-NO connections and no data accuracy, only hallucinations, without access or connections to real, accurate, dedicated absolute data.

[0044] According to one embodiment of the present invention, as illustrated in FIG. 2B, each organization or merchant that desires to be an AI merchant or AI enterprise can provide real-time, bi-directional transactional capabilities to users who desire to access the merchants' services or services of any organization utilizing AI Superintelligence, called ASI. For the purposes of this application, users are described as utilizing PCs, 10a to access ASI Apps 110. Users may also utilize other personal devices such as network computers or cellular devices 10c or smart watches 10b or intelligent cars 10d to access the merchants' services or services from any organization, utilizing AI Superintelligence ASI Apps 110. Twenty eight components, each of which constitutes individually or together the present invention(s), some of which interact to provide this ASI application layer network functionality, namely:

• • [0045] (1) present invention #1: an ASI Browser 100 or other user interface displaying one or more Point-of-Service Applications, namely ASI Apps;
  • [0046] (2) present invention #2: ASI App 110;
  • [0047] (3) present invention #3: ASI App payload data structure of context-specific ASI application workflow with grouped information elements, with information entries illustrated in 150 and attributes illustrated in 120, 130, 140, serialized and input, output parameters marshaled and transmitted over the Internet Cloud 20;
  • [0048] (4) present invention #4: ASI_ID, an identity for the ASI Application data structure, associated with attributes 120, 130, 140 . . . such as User ID, PIN, Balance . . . and information entries as input, output, or input and output parameters 150 . . . such as Bob for User ID, 8212 for PIN, $5000 for balance, returned as output to the ASI request, . . . and methods 160, 170, such as [Deposit], [Withdraw], to act upon the ASI_ID, which is the AI Superintelligence Application data structure identity;
  • [0049] (5) present invention #5: applying ASI methods illustrated in one embodiment 160, 170 upon the data structures;
  • [0050] (6) present invention #6: utilizing ASI App State Machine Protocol ASMP 40 across the Internet Cloud 20;
  • [0051] (7) present invention #7: between an ASI STUB 60; STUB and stub are interchangeably used and mean one and the same thing;
  • [0052] (8) present invention #8: with an ASI Server 30, or ASI AGENT; AGENT and Agent are interchangeably used and mean one and the same thing;
  • [0053] (9) present invention #9: ASI Database 50, forming M/L training data set, to train an LLM with real, accurate, dedicated absolute data accessed and transmitted to said ASI Database by ASI Agent from a data repository 575 in a remote computer of an enterprise or other organization to instantiate an ASI Application data structure, as opposed to using junk data from the web, emails and social media;
  • [0054] (10) present invention #10: ASI Enterprise 80;
  • [0055] (11) present invention #11: ASI LLM;
  • [0056] (12) present invention #12: ASI Billing 604 and other ASI Service Management functions like ASI Operations, Administration, Maintenance and Provisioning services like a Telco;
  • [0057] (13) present invention #13: ASI Switch 200, also called ASI Application Network Nodes;
  • [0058] (14) present invention #14: ASI Application Layer Network;
  • [0059] (15) present invention #15: constituting the ASI Operating System of the present invention;
  • [0060] (16) present invention #16: ASIB, the ASI Application Service Information Base;
  • [0061] (17) present invention #17: EFSM, Extended Finite State Machine;
  • [0062] (18) present invention #18: EISM, Enterprise Interface State Machine;
  • [0063] (19) present invention #19: ASI Command and Control, Communications and Computer Intelligence, ASI C4I Command and Control system, all of which functions are provided by the ASI Switch through all of its four quadrants of services;
  • [0064] (20) present invention #20: ASI Security Management;
  • [0065] (21) present invention #21: ASI Longevity App;
  • [0066] (22) present invention #22: ASI Defense tech App;
  • [0067] (23) present invention #23: ASI Food and Beverage App;
  • [0068] (24) present invention #24: ASI Sleep health tech App;
  • [0069] (25) present invention #25: ASI Dental App;
  • [0070] (26) present invention #26: ASI FinTech App;
  • [0071] (27) present invention #27: ASI Application State Machine;
  • [0072] (28) present invention #28: ASI thinking system.

[0073] All twenty-eight components are described in more detail below.

[0074] FIG. 2B illustrates one embodiment of the present invention(s)—ASI Application Layer Switch 200 comprising: ASI Browser 100 displaying Point-of-Service ASI Applications in short, ASI Apps 110; ASI Stub 60; ASI Agent 30 connecting to a data repository 575 in an enterprise or other real dedicated absolute data—the ASI Enterprise; ASI Database 50 created from real, accurate, dedicated absolute data in an enterprise or other sources of real, accurate, dedicated absolute data, so that the ASI LLM may be trained from the data in the ASI Database 50 in an ASI Enterprise; ASI Service Management functions 604 like ASI Billing, ASI Operations, Administration, Maintenance and Provisioning services; and the ASMP ASI App State Machine protocol, ASMP 40; all of it comprising ASI Application Network Nodes or ASI Application Layer Switch 200 in a completely connected AI Superintelligence—ASI application layer network to form an ASI thinking system. This provides the ASI Superintelligence solution to the current gaps of generative AI, illustrated in FIG. 2A.

[0075] As shown in FIG. 3, running on the client device 10 is a client process 100, such as an AI Prompt, ASI Prompt, or ASI Browser, which is yet another embodiment of the present invention, or other client process. Embedded in the client process 100 is an ASI Application 110, such as a FinTech App or other application. AI Superintelligence Application workflow automation ASI App payload data structure consists of context-specific grouped information elements, with an identity for an ASI Application data structure termed ASI_ID, associated with attributes 120, 130, 140 . . . such as User ID, PIN, Balance . . . with information entries as input, output, or input and output parameters 150 . . . such as Bob for User ID, 8212 for PIN, $5000 for balance, returned as output to the ASI request, . . . and methods 160, 170, such as [Deposit], [Withdraw], to act upon the ASI_ID; serializes the AI Superintelligence Application payload into an application-specific type, customized for an enterprise; transmits the AI Superintelligence Application payload over the AI Superintelligence Application Network over the Cloud/Web, 20; and marshals it to the ASI server, aka AI 2.0 server, 30; unpacks the AI Application Payload utilizing the logic contained in the ASI server, aka AI 2.0 server to unpack the Payload using the ASI Application State Machine Protocol, namely ASMP 40; processes the AI Prompt or ASI Browser request; parses the AI Prompt or ASI Browser request, enables the ASI application layer network framework, such as with AI LLM Asset as a networked Asset, and ASI_ID with information entries and attributes, invokes the ASI Application method with the marshaled parameters, and returns any output parameters as absolute values to the caller/client using the ASI aka AI 2.0 Application State Machine Protocol, ASMP 40, as illustrated in FIG. 3 as uniquely identified connectors from the AI Prompt, ASI Prompt, or other user interface or ASI Browser 100 connecting from ASI App displayed as a Point-of-Service application on the ASI Browser to ASI STUB 60 via the Internet/Cloud 20 and methods connecting to the ACCT STUB 70, and ASI STUB 60 connecting to a server 30, or ASI AGENT to an enterprise skeleton, such as Fidelity or other enterprise 80, the enterprise skeleton Fidelity 80 connecting to individual user account skeletons, such as is shown in FIG. 3, as Bob's ACCT 90 and Di's ACCT 95 to be instantiated, returns any output parameters as absolute values to the client process such as AI Prompt or ASI Prompt or ASI Browser 100, displaying the ASI App, as information entry 150 to attribute Balance 140 as $5000. as well as to the Machine Learning Data Set to train and tune the LLM parameters with dedicated absolute data, 50, in ASI Database as opposed to predictive data of Generative AI or AI 1.0, which lacks accuracy and security and introduces hallucination and bias as the data is taken from emails, social media and the web. FIG. 3 encompasses the AI Superintelligence Switch 200 or ASI Application Layer Switch which is an end-to-end solution of interconnected ASI Application Network Nodes consisting of uniquely identified connectors as data structures ASI_ID with information entries and attributes connecting from the end user's client process 10 to the client ASI STUB 60 and ACCT STUB 70 and further to the server 30 or ASI AGENT to enterprise skeleton 80 and individual ACCT skeletons 90 and 95 to be instantiated so the methods 160 and 170 are applied to the ACCT STUB 70 to which they connect via ASMP 40 over the Cloud, while ASI_ID attributes and information entries 120, 130 connect to ASI STUB 60 via the Internet Cloud and the enterprise server 30 fetches from the enterprise or other data repository of real, accurate, dedicated absolute data to populate ASI Database 50 forming the Machine Learning M/L Data Set consisting of real, accurate, dedicated absolute data, for the AI LLM parameters to be trained and return the results to the AI or ASI Prompt or ASI Browser 100 or other user interface in response to the AI Prompt request or ASI Browser 100 or other user interface from an ASI Application 110 displayed on the ASI Browser 100 or other user interface.

[0076] FIG. 4A illustrates an ASI Application Layer Switch, or simply ASI Switch which comprises the ASI App 110 on an ASI Browser 100 or other user interface, ASI STUB 60 and ASI AGENT 30, interconnected via ASI App State Machine Protocol ASMP 40 over the Internet Cloud 20 to safely access real, accurate, dedicated absolute data from data repository 575 in an ASI Enterprise 80, to create ASI Database 50 for M/L Data set for training ASI LLMs with real, accurate, dedicated absolute data as opposed to junk data from the web, emails and social media so as to eliminate hallucination and bias of AI 1.0.

[0077] FIG. 4B illustrates the ASI Application data structure ASI_ID layer in the ASI application layer network. The AI Superintelligence ASI App ASI_ID layer includes a library providing support for the application programming interfaces (APIs) to remotely access an ASI_ID, its data and its functions in an ASI App network. This interface provides two types of a class: a skeleton, which is the functionality of the ASI App ASI_ID and its stub which allows remote access of the same ASI App ASI_ID. Preferred and other embodiments will be apparent such as C++, Java and Python implementations, as well as non-C++, non-Java and non-Python implementations and implementations such as within a DSP chipset.

[0078] FIG. 5 illustrates an embodiment of the present invention, depicting an example of a Point-of-Service Application list, ASI Apps 110, an embodiment of the present invention displayed on yet another embodiment of the present invention, namely, an ASI Browser 100 or other user interface such as an AI Prompt or other user interface.

[0079] FIG. 6 illustrates conceptually the layered architecture of an ASI Application Layer Switch 200, comprising four quadrants of services, namely, the ASI Boundary Quadrant 601, connecting the Switch 200 to user 10 with an ASI Browser 100 or other user interface, displaying Point-of-Service applications, ASI Apps 110 in ASI Applications Quadrant 602, with the ASI STUB 60 and ASI AGENT 30 in ASI Switching Quadrant 603 via ASI App State Machine Protocol ASMP 40 over the Internet Cloud 20, and interfacing to an ASI Enterprise 80 to its data repository 575 to securely access real, accurate, dedicated absolute data for creating an ASI Database 50 as machine learning Data Set so as to train ASI LLMs in response to an AI Prompt or ASI Browser request or from other user interface, and to instantiate a context-specific Application workflow data structure for user 10 to perform real-time, bi-directional transactions in an ASI Application layer network and enabling ASI Enterprise 80 to connect to billing and other service management functions and services 604 such as operations, administration, maintenance and provisioning like a Telco.

[0080] One embodiment of the present invention utilizes ASMP 40 and distributed ASI Application service information bases ASIBs to perform ASI Application Layer Switching.

[0081] Each data structure in the ASIB has a name, a syntax and an encoding. The name is an administratively assigned data structure ID specifying a data structure type. The data structure type together with the data structure instance serves to uniquely identify a specific instantiation of the data structure. For example, if a data structure is information about models of cars, then one instance of that data structure would provide user 10 with information about a specific model of the car while another instance would provide information about a different model of the car. The syntax of a data structure type defines the abstract data structure corresponding to that data structure type. Encoding of data structures defines how the data structure is represented by the data structure type syntax while being transmitted over the network.

[0082] As described above, the ASI Browser 100 with ASI Apps 110 together with an ASI STUB 60 and ASI Skeleton or ASI AGENT or ASI Server 30 constitute an ASI switch 200.

[0083] FIG. 6 illustrates conceptually the layered architecture of ASI Switch 200, which includes the said Command, Control, Communications and Computer Intelligence C4I system for independent, intelligent AI Prompting and ASI Browsing.

[0084] ASI Boundary service 601: provides the interfaces between ASI Switch 200, the Internet and the Web, and multi-media end user devices such as PCs, televisions or telephones and with GPUs and with the Back Office of enterprises or to data repositories 575 of enterprises or other organizations. Boundary service 601 also provides the interface to the on-line ASI App service provider or ASI Enterprise. A user can connect to a local application, namely one accessible via a local ASI Switch, or be connected to an ASI Application accessible via a remote ASI Switch.

[0085] ASI Application service 602: contains application programs that deliver customer services. ASI Application service 602 includes Point-of-Service applications such as Bank Point-of-Service ASI App 110 described above, and illustrated in FIG. 3 and FIG. 7, that provide real-time, bi-directional transactions to the end user. Other examples of ASI Application network services include ASI health tech Apps, ASI defense tech Apps, ASI FinTech Apps, ASI Database App, ASI Supply Chain Management Apps, ASI Customer Relationship Management CRM Apps, ASI search Apps, ASI social networking Apps, ASI fraud detection and identity theft prevention, ASI food and beverage Apps, ASI longevity and wellness health tech Apps, ASI call center Apps, ASI security Apps, and a variety of other vertical services. Each ASI Application network service is designed to meet a particular set of requirements related to performance, reliability, maintenance and ability to handle expected traffic volume. Depending on the type of service, the characteristics of the network elements will differ. ASI Application network service 602 provides a number of functions including communications services for both management and end users of the network and control for the user over the user's environment.

[0086] An ASI Command, Control, Communications and Computer Intelligence (C4I) system for independent, intelligent AI Prompting and ASI Browsing is found in the totality of the ASI Switch. The Command is in said ASI Boundary quadrant of the ASI Switch at the Network Entry Point on said AI Prompt and at ASI Browser. The Communications is in said ASI Switching quadrant of the ASI Switch in the ASI Application data structure layer and interconnected Agents, FSM, ASI ASIB, ASI EFSM and ASI EISM. The Control is in the ASI Applications quadrant of said ASI Switch in the ASI Applications, ASI Application data structure identity, ASI FSM, ASI ASIB, ASIEFSM and ASI EISM. The Computer Intelligence is in the ASI Service Management quadrant of said ASI Switch, connected to billing for training AI Models accessing the Machine Learning Data Set consisting of real, accurate, dedicated absolute data transferred between devices from a transactional application into the ASI database, wherein all of the C4I system constitutes the ASI Application Network Nodes.

[0087] The present invention is a horizontal platform that lends itself to business applications in all verticals, namely:

• • [0088] ASI FinTech Business Applications;
  • [0089] ASI Supply Chain Management Applications in the Food industry, in healthcare and pharmaceutical industries;
  • [0090] ASI Healthtech Applications, such as ASI longevity Application;
  • [0091] ASI Defense Tech applications;
  • [0092] ASI Call Center Apps;
  • [0093] ASI search Apps;
  • [0094] Asi Social Networking Apps;

[0095] Each business process App is a grain of sand in the ocean of ASI 2-way, real-time transactional Apps, limited only by one's imagination. Just as Web Apps in Web 2.0 proliferated with the use of web APIs for any Web App displayed on a Web browser, and created multi-trillion dollar companies such as Apple, Google, Amazon, the present ASI invention(s) enable a huge number of business process Applications and a huge number of trillion dollar companies. The present invention is an ASI thinking system using AI Superintelligence Application State Machine of the present invention in all verticals.

[0096] Another embodiment of the present invention is to configure ASI Apps for context-specific real-time bi-directional transactions. Listed below are a few ASI Apps for specific purposes in health tech, defense tech, dental insurance tech, FinTech.

[0097] FIGS. 8A, 8B, 8C are flow diagrams illustrating one embodiment of the present invention for an ASI Longevity App for use in hospitals, corporations, fitness centers, gyms, spas, physical therapy offices, sports equipment stores, for stress reduction and wellness needs in Cardiology, Neurology, Sleep Clinics, Vestibular clinics, ENT Departments, Geriatrics, doctor's offices and by patients for disease prevention. The ASI Longevity App workflow process automation in this invention involves configuring the ASI_ID for the ASI Longevity App with grouping of information elements into the end-to-end connected ASI Longevity App starting from the AI Prompt or other user interface or ASI Browser, which is one embodiment of the present invention, displaying an ASI Longevity App connecting to an ASI Stub and on to an ASI server or ASI Agent or interconnected ASI Agents, to safely, securely access enterprise data and fetch the results back in response to the Prompt or ASI Browser or other user interface query at the front end, while the LLM system is M/L trained in the enterprise's real, accurate, dedicated absolute and historical data retrieved and populated in ASI Database 50, access to which may be charged for per access in addition to a monthly subscription fee, using the ASI Billing Management App 604.

[0098] For an ASI Longevity App, the ASI_ID information elements are configured, and include least the following, form filled out by a patient daily:

• • [0099] 1) Patient's Account,
  • [0100] 2) Patient ID,
  • [0101] 3) Hospital Outpatient Rehabilitation or Department ID such as Cardiology or Vestibular Physical Therapy,
  • [0102] 4) Meditation, Frequency-twice a day, Duration: 15 minutes. Alternate nostril breathing, Pranayama, Gratitude Meditation, observing silence also called Mauna Vratha because silence achieves the universe as in Maunam Sarvartha Saadagam and provides healing, Positive Healing, Self-Acceptance of body and mind, Body Scan-self-compassion, self-value;
  • [0103] 5) Walk, Cardio-Extra Credit, Frequency: long walk once daily or short walks twice a day. Write down how many minutes of walk or cardio, highest heart rate, uphill walk, fast walk, to increase respiratory rate.
  • [0104] 6) Get Vitamin D from the Sun: Morning Sunshine: Relax in the morning sunshine, or walk in the morning sun. Frequency: one or twice a day. Write down how many minutes.
  • [0105] 7) Enhance joy and calmness with grounding techniques with five senses. 5 things you can see: sunrise, trees, floor, people, mountains; 4 things you can hear: birds, trees, breeze, street; 3 things you can smell: Clear air, flowers, trees; 2 things you can feel in skin: breath in face, feet on ground; 1 thing you can taste: your drink.
  • [0106] 8) Take frequent breaks from prolonged Screen Time every 30 mins with computer screen, cell phone and book.
  • [0107] 9) Eight hours of Sleep: Write time what time you went to bed; System sends Alerts and Notifications if patient not going to bed at 10 pm;
  • [0108] 10) Protein intake at each meal, 30-30-30 g: Write down Gms of protein taken at each meal.
  • [0109] 11) Single leg stance, eyes open: Frequency: twice or thrice/day; Duration: 15 sec or 10 sec.
  • [0110] 12) Lunge: Repetitions: 5 or 2; Frequency: 2 or 3/day; Duration:
  • [0111] 13) Standing or Sitting: Touch your shins (bend over): Repetitions: 2× or 1×; Frequency: twice or four times/day.
  • [0112] 14) Walking backward, eyes open: Repetitions: 30 sec, Frequency: twice/day; Duration: 10 or 20 steps both directions;
  • [0113] 15) Zombie walk, fists and hands up, eyes closed: Frequency: twice or thrice/day; Duration: 10 ft or 20 ft back and forth in hallway.

[0114] FIGS. 8A, 8B, 8C and FIG. 3 illustrate one embodiment of the present invention for an ASI Sleep App for use in hospitals, spas, in sleep clinics, for diagnosing and treating sleep apnea. For an ASI Sleep App, the ASI_ID data structure information elements are configured, and include at least the following, App provides a form filled out by a patient daily:

• • [0115] 1. Patient's Account,
  • [0116] 2. Patient ID,
  • [0117] 3. Hospital Department ID such as Sleep Clinic, Cardiology or ENT,
  • [0118] 4. Meditation, Frequency—before sleep, Duration: 15 minutes. Alternate nostril breathing, Pranayama, observing silence also called Mauna Vratha because silence achieves the universe as in Sanskrit, Maunam Sarvartha Saadagam and provides healing;
  • [0119] 5. Get Vitamin D from the Sun: Morning Sunshine: Relax in the morning sunshine, or walk in the morning sun. Frequency: one or twice a day. Write down how many minutes.
  • [0120] 6. Enhance joy and calmness with grounding techniques with five senses. 5 things you can see: sunrise, trees, floor, people, mountains; 4 things you can hear: birds, trees, breeze, street; 3 things you can smell: Clear air, flowers, trees; 2 things you can feel in skin: breath in face, feet on ground; 1 thing you can taste: your drink.
  • [0121] 7. Take break from prolonged Screen Time with computer screen, cell phone and book an hour before sleep and log this daily.
  • [0122] 8. Eight hours of Sleep: Write time what time you went to bed; System sends Alerts and Notifications if patient not going to bed at 10 pm.
  • [0123] 9. Log daily how many hours on CPAP machine.
  • [0124] 10. Protein intake at each meal, 30-30-30 g: Write down Gms of protein taken at each meal.
  • [0125] 11. Supplements: Log daily supplement intake for better sleep;
  • [0126] 12. Listen to soothing music before bed: Log daily what duration.
  • [0127] 13. Log daily intake of milk before bed for better sleep.

[0128] FIG. 3 illustrates one embodiment of the present invention for an ASI Dental App for use in dentists' offices to pre-authorize payment from insurance to avoid patient not paying for root canal.

[0129] For an ASI Dental App, the ASI_ID data structure information elements are configured, and include at least the following:

• • [0130] Patient's Account,
  • [0131] Patient ID,
  • [0132] Dental Insurance details,
  • [0133] Dentist Office details,
  • [0134] Dental Procedure performed,
  • [0135] Billing details,
  • [0136] Payment pre-authorization by Insurance Provider.

[0137] FIG. 3 illustrates one embodiment of the present invention for ASI App in Defense technologies for use in C4I, Command and Control, Communications and Computer Intelligence using AI Superintelligence, for the U.S. Government in military operations for autonomous sense making, to integrate various defense hardware like drones and surveillance towers. It enables AI-powered surveillance, target identification, and automated decision-making, enhancing operational capabilities for military and border security, to identify and track potential threats in real-time, aiding in timely and effective responses.

[0138] For an ASI Defense tech App, the ASI_ID data structure information elements are configured, and include at least the following:

• • [0139] Identity of targets in an ASI data structure, with attributes and information entries;
  • [0140] Identity of drones in an ASI data structure, listing attributes and information entries;
  • [0141] Identity of potential threats in an ASI data structure, listing information entries and attributes;
  • [0142] Identity of Surveillance towers in an ASI data structure with information entries and attributes;
  • [0143] Data structure identity for border security in an ASI data structure with information entries and attributes;
  • [0144] Data structure identity for data from various sensors and platforms to create an integrated understanding of the operational environment in military operations in an ASI data structure with information entries and attributes;
  • [0145] Data structure identity for warfare systems, with information entries and attributes;

[0146] Data structure identity for casualty care and evacuation, with information entries and attributes, for access to large medical database that is able to access data containing medical trauma cases, which include diagnoses, vital sign sets, medications given, treatments, and outcomes, to provide indications, warnings, and suggestions for treatment.

[0147] Data structure identity for logistics and transportation of ammunition, goods, armaments, and troops for the success of military operations. ASI Defense tech Apps to lower transportation costs and reduce the need for human input by plotting the most efficient route to travel under current conditions and to pre-identify problems for military fleets in order to increase efficiency of their performance.

[0148] ASI can significantly enhance food safety monitoring in various ways, utilizing the present invention:

• • [0149] Hazard Identification: ASI systems can analyze data from sensors, cameras, and other sources to identify potential hazards (such as contaminants or spoilage) in real-time. Early detection allows for swift corrective actions.
  • [0150] Predictive Analytics: By analyzing historical data, ASI models can predict food safety risks. For instance, they can forecast when certain ingredients might spoil or when equipment maintenance is needed.
  • [0151] Automated Record Keeping: ASI streamlines record-keeping processes. It ensures accurate and consistent documentation of temperature logs, sanitation practices, and compliance with safety protocols.
  • [0152] Traceability and Recall Management: ASI helps track the entire supply chain, from farm to table. In case of a food recall, it can quickly identify affected batches, minimizing health risks.
  • [0153] Customization to Specific Environments: ASI algorithms can adapt to different food production environments, whether it is a large scale kitchen, a processing plant, or a restaurant. Customization ensures effective monitoring.
  • [0154] Staff Training and Alerts: ASI powered training modules can educate staff on food safety practices. ASI can send alerts when deviations occur. (temperature fluctuations.) Compliance with Regulations: ASI ensures adherence to food safety regulations by continuously monitoring critical control points (CCPs) and providing real-time feedback.
  • [0155] Menu Optimization and Personalization: Configure the ASI_ID data structure information entries and attributes and methods for an ASI App that analyzes customer preferences, dietary restrictions, and seasonal availability to optimize menu offerings. Personalized recommendations can enhance customer satisfaction and reduce food waste.
  • [0156] Supply Chain Management: Configure the ASI_ID data structure information entries and attributes and methods for an ASI-driven system to predict ingredient demand, optimize inventory levels, and manage vendor relationships. This ensures timely procurement, minimizes waste, and maintains consistent quality.
  • [0157] Employee Scheduling and Shift Management: Configure the ASI_ID data structure information entries and attributes and methods for an ASI App that uses ASI algorithms to create efficient employee schedules, considering factors like availability, skills, and labor laws. Real-time adjustments can handle unexpected changes.
  • [0158] Food Safety Monitoring: Configure the ASI_ID data structure information entries and attributes and methods for an application that uses image recognition and IoT sensors to monitor food safety compliance. It can detect contaminants, track expiration dates, and ensure adherence to health regulations.
  • [0159] Automated Meal Planning for Large Events: Configure the ASI_ID data structure information entries and attributes and methods for an ASI App that generates customized meal plans for large parties based on dietary preferences, allergies, and portion sizes. It can also estimate ingredient quantities and costs.
  • [0160] Predictive Maintenance for Kitchen Equipment: Configure the ASI_ID data structure information entries and attributes and methods for an ASI system that predicts equipment failures and maintenance needs. By monitoring usage patterns and performance data, it can schedule preventive maintenance, reducing downtime.
  • [0161] Traceability and Food Origin Tracking: Configure the ASI_ID data structure information entries and attributes and methods for an ASI App that traces the entire supply chain-from farm to table. Customers can scan QR codes to learn about the origin of their food.
  • [0162] Automated Nutritional Analysis: Configure the ASI_ID data structure information entries and attributes and methods for an ASI App that analyzes recipes and menus to provide detailed nutritional information. It can help chefs balance meals, meet dietary requirements, and label allergens.
  • [0163] Dynamic Pricing and Cost Optimization: Configure the ASI_ID data structure information entries and attributes and methods for an ASI-powered pricing model that adjusts menu prices based on real-time factors like ingredient costs, demand, and seasonality. It ensures profitability while remaining competitive.
  • [0164] Customer Feedback Analysis: Configure the ASI_ID data structure information entries and attributes and methods for an ASI App that processes customer reviews, social media posts, and surveys using natural language processing (NLP). Insights can guide menu improvements and enhance overall service.
  • [0165] ASI technologies play a crucial role in enhancing traceability within supply chains. To achieve this, they could employ the following, applying the present invention:
  • [0166] Automated Data Collection and Verification: Configure the ASI_ID data structure information entries and attributes and methods for an ASI App to automate data collection and verification. Real-time visibility is achieved by tracking products from source to destination.
  • [0167] Optimized Transportation Routes: Configure the ASI_ID data structure information entries and attributes and methods for an ASI App to optimize transportation routes, reducing fuel consumption and greenhouse gas emissions in order to help achieve sustainability goals.
  • [0168] Supplier Compliance Monitoring: Configure the ASI_ID data structure information entries and attributes and methods for an ASI App for supply chain traceability solutions to enable companies to monitor and enforce supplier compliance with sustainability standards.
  • [0169] Consumer Trust and Transparency: Configure the ASI_ID data structure information entries and attributes and methods for an ASI App for end-to-end supply chain traceability to provide consumers with detailed information about the products' journey, including sourcing, manufacturing processes, and handling. This transparency can generate consumer trust.
  • [0170] Data Accessibility and Integration: The ASI Database and other embodiments of the present invention lend themselves for data accuracy in supply chains. Data inaccessibility is a major challenge for AI in supply chains. Data acts as the essential fuel for ASI where it drives decision-making and operational improvements. If AI cannot access the necessary data, its learning and decision-making capabilities get severely limited. This leads to less accurate predictions and inefficiencies in the supply chain. Ensuring easy access to relevant data is crucial for effective AI integration and performance in supply chain management.
  • [0171] The ASI Database of the present invention lends itself to create a centralized data repository accessible to all relevant teams. Other aspects of the present invention enable the use of APIs and integration tools to connect disparate data sources.
  • [0172] The present invention corrects the current problems with generative AI that leads to Insufficient Data: ASI thrives on accurate data. The present invention ensures access to large amounts of relevant data for optimal performance. Quality assurance is critical to the ASI implementation process-specifically, as it pertains to data. Inadequate data quality and quantity can pose significant barriers, as it can undermine algorithms and lead to flawed insights and poor subsequent decision-making. Neglecting the importance of data quality not only hampers AI's effectiveness but can also perpetuate existing inefficiencies or even introduce new errors into the system.

[0173] ASI Switching Service 603: is an OSI application layer switch. Switching service 603 thus represents the core of the ASI Switch. It performs a number of tasks including the routing of user connections to remote ASI Switches, described in the paragraphs above, multiplexing and prioritization of requests, and flow control. Switching service 603 also facilitates open systems' connectivity with both the Internet (a public switched network) and private networks including back office networks, such as banking networks. Interconnected application layer switches form the application network backbone. The components that comprise the Switching Service 603 are described in detail under FIG. 2B above and include interconnected ASI Agents, as the ASI Stub and ASI Agent have the same code. These switches are one significant aspect of the present invention.

[0174] ASI Management service 604: provides applications for end users to manage network resources, and to perform billing and other service management functions such as Operations, Administration, Maintenance & Provisioning (OAM&P) functions for security management, fault management, configuration management, performance management and billing management 604, like a Telco. Providing OAM&P functions and billing for ASI Applications in this manner is another significant aspect of the present invention.

[0175] FIG. 7 illustrates that each ASI Enterprise may choose the types of services that it would like to offer its clients. In this example, if Bank 80 decides to include in their ASI Point-of-Service application access to checking and savings accounts, user 10 will be able to perform real-time transactions against his checking and savings accounts. Thus, if user 10 moves $5000 from his checking account into his savings account, the transaction will be performed in real-time, in the same manner the transaction would have been performed by a live teller at the bank or an ATM machine. Therefore, unlike his prior LLM hallucination experience, user 10 now has the capability to perform real-time bi-directional transactions on his bank account with ASI Apps. The ability to perform these types of robust, real-time, bi-directional transactions from an ASI App 110 displayed in an ASI browser 100 by eliminating hallucination and bias of AI 1.0, by safe secure access to real, accurate, dedicated absolute data transmitted to an ASI Database 50, ensuring data quality and connection, providing a connected LLM in an ASI enterprise is a significant aspect of the present invention. FIG. 7 shows user 10 accessing and selecting an ASI App 110 from the list of ASI Apps, such as Loan, CD, Payroll, Small Business, checking account or other ASI Application N displayed on an ASI Browser 100 or other user interface. User connects to Bank 510 from ASI Browser 100 and accesses his or her checking account by providing input parameters for attributes User Id 120 and PIN 130, which are the attributes of the grouped context-specific Application workflow information elements in Bank 510. The ASI request is transmitted to the ASI Stub 60 and instantiated at ASI Agent or server 30 via the ASI App State Machine Protocol ASMP 40 described supra over the Internet Cloud 20, connecting to host database 575 in a Back Office, and thereafter, sending the response back to the user 10 via the ASI Agent 30 to ASI Stub 60 to ASI Browser 100 and the data also sent to the ASI Database 50 forming Machine Learning Data Set for LLMs to access and be trained in so as to provide an accurate response to the user's AI Prompt request or from other user interface such as the present invention, such as an ASI Browser 100. This end-to-end ASI Switch 200 on the ASI Application layer network, may reside on GPUs like Nvidia's GPU or other GPUs, as ASI Application Network Nodes, enabling the ASI Enterprise 80 to provide billing 604 or other service management functions and services such as operations, administration, maintenance and provisioning apps like a Telco and includes a C4I system.

[0176] As shown in FIG. 7, embedded in client process ASI Prompt or ASI Browser 100 is an ASI Application 110, such as a FinTech App, such as Savings Account, CD, MF, Checking Account, Small Business, Payroll, Loan . . . ASI Agent 30 connects to ASI Comm Port in Bank Host or other enterprise Host 575, utilizing Fin Tech App(s) 110, such as Savings Acct, CD, MF, Checking, SB, Payroll, Loan . . . AI Superintelligence Application data structure consisting of ASI_ID which comprises context-specific grouped information elements—attributes and information entries, is serialized, transmitted over the Cloud and marshaled into the ASI server, Application State Machine Protocol 40 unpacks the payload and invokes the ASI Application methods with the marshaled parameters and returns any output parameters as absolute values to the Machine Learning Data Set, 50, to train and tune the LLM parameters with real, accurate, dedicated absolute data, 50, in ASI Database 50, connecting to a billing or other service management App, 604.

[0177] FIG. 7 illustrates an AI Superintelligence Application Layer Switch 200 switching the user between ASI Apps 110, shown as 1, 2, 3, 4 . . ., namely, Pizza App, BMW App, Small business App, Loan App . . . with ASI Agents, 30 . . ., namely, Pizza Agent, BMW Agent, Small business Agent, Loan Agent . . . .

[0178] FIG. 7 illustrates an AI Superintelligence Application Layer Switch 200 starting from an AI Prompt 100 and connecting end to end in an ASI application network; ASI Apps 110, shown as 1, 2, . . . N for Pizza App, BMW App, SB App, Loan App, Payroll App, . . . App N; ASI Agents 400, shown as 1, 2, . . . N for each of the respective Apps such as Pizza Parlor ASI Agent, BMW Dealer ASI Agent, Small Business ASI Agent, Loan ASI Agent, Payroll ASI Agent; connecting to the Bank or other enterprise, allowing the ASI Network to function like a Telco-Network to do billing and other service management functions such as operations, administration, maintenance and provisioning.

[0179] Bank can also decide to provide other types of services in Point-of-Service ASI Apps. For example, Bank may agree with Car dealership to allow Bank customers to purchase a car from that dealer, request a car loan from Bank, and have the entire transaction performed using ASI Apps 110, as illustrated in FIG. 7. In this instance, the transactions are not merely two-way, between the user and Bank, but three-way, amongst the consumer, Bank and Car dealership. According to one aspect of the present invention, this three-way transaction can be expanded to n-way transactions, where n represents a predetermined number of merchants or other service providers or ASI Enterprises who have agreed to cooperate to provide services to users. The present invention therefore allows for “any-to-any” communication and transactions utilizing ASI, thus facilitating a large, flexible variety of robust, real-time, bi-directional transactions using AI Superintelligence.

[0180] Bank may also decide to provide ASI intra-merchant or intra-bank services, together with the inter-merchant services described above. For example, if Bank creates an ASI Point-of-Service application for use by the Bank Payroll department, Bank may provide its own employees with a means for submitting timecards for payroll processing by the Bank's Human Resources (HR) Department. An employee selects the Bank ASI HR Point-of-Service application and submits his timecard. The employee's timecard is processed by accessing the employee's payroll information, stored in the Bank's Back Office. The transaction is thus processed in real-time, and the employee receives his paycheck immediately.

[0181] FIG. 8A, FIG. 8B and FIG. 8C show flow diagrams illustrating one embodiment of the present invention(s). In FIG. 8A, a user starts a client process in step 810. In step 812, the user connects to an ASI browser displaying ASI Apps interfacing to ASI Switch. In step 814, the user issues a request from ASI browser or AI Prompt or other user interface to use a transactional application. ASI Switch connects the user to the selected ASI App in step 816. In step 818, ASI App State Machine Protocol, ASMP executes the user's ASI request by sending to and from the ASI Stub and ASI Agent the context-specific application workflow grouped, serialized, and marshaled data structure of information entries and attributes with methods applied to the data structure over the Internet Cloud.

[0182] In FIG. 8B, the ASI Agent safely and securely retrieves data from the data repository in step 820. In step 822, the absolute values of real, accurate, dedicated absolute data become input parameters for M/L Data Set in ASI Database. Step 824 returns results to ASI Stub. Step 826 sends results to the client process.

[0183] In FIG. 8C, step 828 creates ASI Database as M/L Data Set of absolute values of real, accurate, dedicated absolute data from enterprise data. Step 830 tunes LLM parameters with the M/L Data Set of absolute values from ASI Database. Step 832 generates tokens for sequence. Step 834 returns response to ASI Request with accuracy, without hallucination or bias. Step 36 lets user continue transaction or end transaction.

[0184] FIGS. 8A, 8B, 8C show a Flow diagram illustrating one embodiment of the present invention. A two-pronged approach is shown, where a user issues a Prompt or ASI request from an ASI Browser or other user interface to use a transactional application. An Application data structure identity ASI_ID is created. The ASI Application State Machine Protocol executes the user request. The ASI_ID has a Method Name and has input arguments of information entries and attributes and generates output arguments that are absolute values that now become input parameters for M/L Data Set. So, now the M/L Data Set contains absolute values of real, accurate, dedicated absolute data, rather than from emails and off the web and social media, constituting junk data from which predictive data is currently generated in AI 1.0. Now, in AI Superintelligence aka AI 2.0, LLM Parameters are tuned utilizing this new M/L Data Set of absolute values, of real, accurate, dedicated absolute data or historical data in an Enterprise. This now generates tokens for sequence. A Prompt response of predictive values is generated. This two-pronged approach ensures accuracy, eliminates bias and gives security by accessing and invoking context-specific application workflow process automation data structures located on remote hosts.

• • [0185] (1) Absolute data, for example, one's account balance at any instant in time, fetched from the back-office of an enterprise;
  • [0186] (2) Historical Data in an enterprise;
  • [0187] (3) Predictive data, where the Machine Learning Data Set comes from emails, social media and the web, in other words, this data is not reliable, as it is not accurate, introduces bias and lacks security.

[0188] The present invention utilizes real, accurate, dedicated absolute data, historical data and feeds them into the M/L Data Set for predictive analysis, so that it eliminates bias, enhances security and ensures data accuracy.

[0189] ASI Application State Machine Protocol of the present invention enables a user to invoke requests in an AI Prompt or an ASI browser, which is one embodiment of the present invention or other user interface by an ASI Application data structure identity with information entries and attributes and methods, with input/output parameters, serializes them into an application-specific type, customized for an enterprise and marshals it to the ASI server or ASI Agent or interconnected ASI Agents and then returns any output parameters as absolute values to the caller/client using the ASI Application State Machine Protocol and to the Machine Learning Data Set to train and tune the LLM parameters with real, accurate, dedicated absolute data, as opposed to predictive data of AI 1.0, which lacks accuracy and security and introduces bias as the data is taken from emails, social media and the web. This ensures accuracy and security and eliminates hallucination and bias. The ASI_ID instance uniquely identifies an instantiation of the ASI_ID type.

[0190] This includes a library providing support for the application programming interfaces (APIs) to remotely access an ASI_ID ASI Application data structure, its data and its functions in an ASI_ID Application data structure network. This interface provides two types of a class, a skeleton, which is the functionality of the ASI_ID and its stub, which allows remote access of the same ASI_ID.

[0191] Glossary of terms used is provided here below.

[0192] Item is its definition.

[0193] Abstract Class is a C++class which does not have all virtual functions defined.

[0194] Class is a C++/Java data structure definition which defines both the data and functions.

[0195] Interface is a Java term similar to the C++Abstract Class.

[0196] Meta is a “meta”-compiler that translates a higher level “meta”-language (ASIB) from the “meta”-file into a lower-level language (C++) output file for and before giving to a traditional compiler.

[0197] ASI_ID is a C++/Java data structure instance, which is defined by a class.

[0198] ASMP of the present invention allows the user to specify functions which can be executed remotely. The basic operation uses ASI_IDs and class information, instead of simple, unrelated functions and data. The arguments to the function is specified in the meta file and whether the type of argument passing is by value or reference can also be specified.

[0199] ASMP allows for transparent remote or local operation. The programmer does not need to know whether the ASI_ID is “local” or “remote”. The interface-automatically determines this and will allow for the correct operation based on the type of ASI_ID.

[0200] There are several requirements for ASMP to provide a clean and transparent operation of local and remote ASI_ID. FIG. 4B illustrates these basic requirements and operations layers of the ASI_ID ASI Application data structure layer.

[0201] ASI_ID—AI Superintelligence Application Data Structure Identity: is needed for ASMP to determine if the ASI_ID is local (skeleton) or remote (stub). This is also needed to determine arguments and ASI_ID serialization. This feature is provided in the preferred embodiment by the ASIAppASI_ID in the asiapp. lib library. Each new class “XYZ” must add a XYZ_ClassID, XYZStub_ClassID and XYZSkel_ClassID to the ASI App/ClassID.h file.

• • [0202] Network Line Protocol/TCP: is needed to communicate with the remote computer. For ASMP, ASIAppRemotePDU provides this protocol data unit (PDU) and transmits the data using data serialization.
  • [0203] Data Serialization: To transfer data between computers or devices, the arguments, herein the name-value pairs and the ASI_IDs themselves need to be sent over the network. This is the serialization of the data onto a network stream. The persistence nature of the framework used ensures this. The code is generated by the meta compiler in the skeleton.

[0204] To ensure that all data is passed as arguments to a method requires the user to check all arguments, herein, the name-value pairs and throw an exception, if there is something missing or wrong. This is provided by the meta compiler in the stub and skeleton.

[0205] To block a thread during network transmission and reception, the ASI_ID must use a different thread to perform the actual network activity and control the calling thread status. This allows calling a remote ASI_ID to behave similar to a local ASI_ID. This is performed by the framework class in the ASIAppRemotePDU class.

[0206] This allows for a method to be called from an ASCII string representation. This is useful since it provides a simple, but unique means of calling a class method. This can also be used by the programmer directly. This data marshaling is created by the meta compiler in the base class.

[0207] By maintaining reference counts in both the local and remote ASI_IDs, time consuming malloc's and free's are avoided as well as confusing details of which function is responsible for deleting which ASI_ID. This is provided by ASMP in dealing with ASIAppRemoteASI_ID types. The user cannot delete an ASIAppRemoteASI_ID child, causing an exception to be thrown, but must use the member function ASI_IDI_unreference( ). A user stores a copy of an ASIAppRemoteASI_ID child by calling the method ASI_IDI_reference( ). Otherwise, the ASI_ID may be destroyed by someone else. This interface is provided by ASIAppRemoteASI_IDInt. Abstract Base Class: To operate on an ASI_ID without knowing its location (local or remote) requires an abstract class which forms as the base class. This is the base class, which is the parent of both the stub and skeleton. This is an abstract ASI_ID (cannot be instantiated alone) and is created by the meta compiler.

[0208] The client and server classes are inherited from the abstract base class and from their respective ASI_ID layer classes. This allows them to inherit the functionality of the base class as well as the ASI_ID layer routines. This is created by the meta compiler.

[0209] The Meta compiler takes a definition file and creates using encoding the above requirements: ASI_ID Identity, Data Serialization, Data Marshaling, String Execution, Abstract Base Class, and the Stub/Skeleton Multiple Inheritance. If one were to code all of this by hand for even the simplest class, there would be too many errors to even manage. The meta compiler eliminates these errors.

[0210] This is the user created set of classes built around and on top of ASMP APIs. This is the basis of the ASI_ID layer to the next level up the software layers. This foundation appears local to the programmers using the ASI_ID layer even though it may be remote.

[0211] The programmer needs to be aware of the base class ASIAppRemoteASI_ID. There is an interface specification ASIAppRemoteASI_IDInt which is inherited by both the ASI_ID layer ASI_IDs and the data model ASI_IDs. For purposes of example, ASIAppName is a new data model ASI_ID, which contains one data member “name” which is a String. The meta compiler automatically creates two access components for this data member: get_name and set name. In addition, the meta compiler also creates the local and remote versions of this data ASI_ID: ASIAppNameSkel and ASIAppNameStub, respectively.

[0212] The abstract base class not only contains all of the member methods and data access components, but it contains support functions which provide a uniform interface to behave as an ASIAppRemoteASI_ID. This includes:

• • [0213] 1 ASIAppStringExecution to execute any method using a simple ASCII string, and ASI_ID type data.
  • [0214] 2. ASI_ID Lock, which provides a thread synchronization mechanism.
  • [0215] 3. ASI_ID Flags, which provides a simple and consistent Boolean flag variables.
  • [0216] 4. reference counts, which allow ASIAppRemoteASI_IDs to be shared without ownership concerns.
  • [0217] 5. conversions between ASI_ID, ASIAppRemoteReference, ASIAppRemoteStub and ASIAppRemoteSkel types.

[0218] The skeleton represents the server side of ASMP. This is a class, which is derived off the abstract base class ASIAppName and ASIAppRemoteSkel. All of the methods (except data access components) must be defined by the programmer for the skeleton since this is the actual ASI_ID. Whenever a real instance of the class is created, it will have the suffix “Skel”.

[0219] This is the client (or remote) side of an ASI_ID. This is similar to the skeleton because it is derived off the abstract base class ASIAppName and an ASI_ID layer class ASIAppRemoteStub. However, there is nothing for the programmer to define for this class. All methods are generated by the meta compiler.

[0220] This is a program in the preferred embodiment, which creates the three classes: abstract base, stub and skeleton. For each class, an interface file (header file .h) and a C++ definition file (source code .cpp) is created. It will be apparent to those of ordinary skill in the art that the implementation defined here represents an implementation of the preferred embodiment. Other embodiments will be apparent such as non-TCL, non-C++ and non-Java implementations and implementations such as within a DSP chipset.

[0221] The classname is the base class (such as Account). The meta compiler created Account file must be in the same directory as other parent definitions.

[0222] ASMP files are found under ASIApp/Util. These files parse the description file and produce the six C++ output files.

[0223] In the preferred embodiment, the syntax must be adhered to closely.

• • [0224] The six files are cbase, hbase, cstub, hstub, cskel or hskel.
  • [0225] The compiler will wait for the header section to complete. Then, begins the class name and parent, followed by the data section; and next followed by the method section, with method and arguments.

[0226] The operation of this ASI_ID layer is introduced through an example.

[0227] Referring to FIG. 3, consider a sample financial institution in which there is a main bank ASI Application data structure ASI_ID “Fidelity” and several bank Accounts “Bob” and “Di”. On the remote client side, the programmer first must establish contact with the remote server and then receive the Bank ASI_ID on the client side as a stub. Once the stub is received, the client can then look up accounts just as if the programmer was local to the skeleton on the server side. The programming code is the same on either the client or server side. The programmer does not need to know where the actual ASI_ID resides: local or remote.

[0228] The programmer must first create a definition file describing the ASIAppBank and ASIAppBankAcount ASI_IDs. This is written in a simple language, which is parsed by the meta compiler of the present invention.

[0229] This class contains both methods and data. The data is simply an integer describing the amount of money the account holds. The two methods: deposit and withdraw, simply increment and decrement this amount, respectively. The ASIAppBankAccountSkel.cc defines the skeleton methods. The stub methods are defined by the meta compiler.

[0230] For the Bank ASI_ID, the meta compiler will create six files: ASIAppBank.h, ASIAppBank.cpp, ASIAppBankStub.h, ASIAppBankStub.cpp, ASIAppBankSkel.h and ASI BankSkel.cpp. These six files describe the operation and remote execution of the ASIAppBank ASI_ID. Since there is no data, there will be no data access components generated. The returned ASI_ID ASIAppBankAccount is followed by the method name, getAccount, and the arguments (name-value pairs). In this case there are two integer arguments with name id and pin. The programmer, however, must still describe any additional functionality for the operation of this ASI_ID and the definitions of the skeleton methods contained in the ASIAppBankSkel. cc file.

[0231] In this simple example, getAccount will always return Bob's account.

[0232] The client and server are simple. The server side creates the skeletons and registers them in the name server: The client program is just as simple. The major benefit demonstrated above is that the programmer does not have to know whether the ASI_ID “Bob” is local or remote.

[0233] Trade-offs and considerations taken into account during the creation of the ASI Application data structure ASI_ID layer are described below:

[0234] This section describes in more detail the function and purpose of each class in ACMP of the preferred embodiment of the present invention.

[0235] This is the interface that all remote ASI_IDs must have. It contains several abstract class definitions, including ASI_StringExecutionInt, ASI_Lock and ASI Flags. Plus, it defines several methods used for all remote ASI_IDs.

unsigned get_ASI_IDI_referenceCnt( ) const

[0236] This returns the number of pointers outstanding for this ASI_ID. If garbage collection is enabled, this ASI_ID will automatically be destroyed when the referenceCnt reaches zero.

ASIAppReferenceld get_ ASI_IDI_referenceID( ) const

[0237] This is the remote referenceld for this ASI_ID. This ASIAppReferenceld uniquely tags an ASI_ID instance on the server for the established connection. This is not a well-known name in the sense that it is not guaranteed to be the same with a different connection.

unsigned ASI_IDI_reference( ) const

[0238] This increments the number of references outstanding. This needs to be performed whenever a new copy of the pointer is stored.

void ASI_IDI_unreference( ) Const

• • [0239] This decrements the reference count and should be called instead of delete.
    ASI_ID*ASI_IDI_ASI_ID( ) const
    ASIAppRemoteStub* ASI_IDI_stub( ) const

[0240] This will return a stub for this ASI_ID. If this ASI_ID is local, it will create a stub. If this is already a stub, it will increment the reference count.

ASIAppRemoteSkel*ASI_IDI_skel( ) const

[0241] This will return a skeleton for this ASI_ID. If this is a skeleton, it simply increments the reference count. If this is a stub, it will create a new skeleton, copy the data and return it.

ASIAppRemoteReference*ASI_IDI remoteReference( ) const

[0242] This will create an ASIAppRemoteReference ASI_ID which is only used for serialization.

[0243] This is the actual first level implementation of the above interface and adds String Execution to the above functions. From this ASI_ID, all of ASMP ASI_IDs are derived.

[0244] This is a type of network “pointer” which indicates where the actual skeleton ASI_ID resides.

ASIAppReferenceld referenceld

[0245] Port and host are used to uniquely specify the socket for the ASIAppRemoteConnectionServer. The referenceld is used to uniquely specify which ASLID on the ASIAppRemoteConnection Server this points to. The classID is simply used to construct a local stub ASI_ID.

[0246] All stubs are derived from this ASI_ID and the abstract base ASI_ID for the class. This ASI_ID provides some interfaces to ASMP library, which is used by the meta compiler.

[0247] ASIAppRemotePDU*_ASI_IDl_execute(ASIAppRemotePDU*pdu) const This will block until ASI_IDI execution is finished. It will take the pre-formatted PDU.

ASIAppMarshalld_ASI_ID_end(ASIAppRemotePDU*pdu) const

[0248] This is a non-blocking remote execution, which returns an ASIAppMarshalld, which can be used to receive the result.

ASIAppRemotePDU*_ASI_IDI_peek(ASIAppMarshalId id) const

[0249] This checks if the PDU id is returned from execution.

ASIAppRemotePDU*_ASI_IDI_receive(ASIAppMarshalId id) const

[0250] This blocks until the PDU is returned.

ASIAppRemoteClient*_ASI_IDI_connect( ) const

[0251] This ensures the connection to other side is established.

[0252] All skeletons are derived off this ASI_ID and the abstract base for the class. This ASI_ID provides the interface ASI_IDI_methodPDU( ) for the meta compiler to ASMP.

[0253] This is the actual data packet sent across the network. The data in this are:

[0254] This is the PDU packet number. This is a monotonically increasing integer to uniquely identify the packet.

[0255] This is one of several known protocol operations:

• • [0256] Disconnect—close the connection between ASIAppRemoteClient and ASIAppRemoteServer
  • [0257] Error—an error occurred in processing the request
  • [0258] Result—a packet containing the result of a request
  • [0259] Lookup—a request to find an ASIAppRemoteReference based on a well-known name in the

• • [0260] Ping—a request for the server to send a Pong back.
  • [0261] Pong—a response from the server to the client to a Ping
  • [0262] Method—a request to execute the command on the server
  • [0263] Unreference—a request to decrement a reference count.
  • [0264] Reference—a request to increment a reference count.
  • [0265] An ASCII string command to execute on the remote server. This is the “name” in a Name-Value pair.
    ASIAppReferenceld referenceId

[0266] This is the ASI_ID ASIAppReferenceId on the server to uniquely identify the ASI_ID of this PDU.

[0267] This is the data for a method execution. This is the “value” in a Name-Value pair.

[0268] This is the main class on the server side of ASMP. This is the entry point into the system for an ASIAppRemoteClient requesting access to an ASIAppRemoteServer.

[0269] This is the main class on the client side of ASMP. This is the entry point into the system for a connection and to create an ASIAppRemoteClient for a particular destination to the ASIAppRemoteConnectionServer.

[0270] This is server side of the client-server communication channel that processes each inbound request. The ASIAppRemoteServer will spawn a new thread for each ASIAppRemotePDU method packet. There is always one ASIAppRemoteServer for an ASIAppRemoteClient.

[0271] This is the client side of the client-server communication channel that sends each outbound request and receives the inbound response. There is always one ASIAppRemoteClient for an ASIAppRemoteServer.

[0272] This is the class, which is thrown by both the client and server side whenever an error is detected. All of these are fatal and are non-recoverable.

[0273] This is the class, which is thrown by both the client and server side whenever an exception is detected. None of these are fatal and the user should provide recovery code.

[0274] A timing diagram may be drawn that shows the timing between all of the ASI_IDs and the threads operating on them in the preferred embodiment. Such a timing diagram represents the startup of the ASI_ID layer on both the client and server sides. It also demonstrates a lookup(“root”) call from the client and a later getname() method call on the root ASI_ID.

[0275] Vertical lines in such a timing diagram represent the ASI_IDs (data and functions) used in the client and server sides. Horizontal lines represent the threads in the operating system-different threads have different line patterns. There are two threads on the client side (left) and there are three on the server side (right). Also, the dotted “write” line represents TCP traffic between the two machines (client and server).

[0276] It will be apparent to those of ordinary skill in the art that the system items defined above represent an implementation of the preferred embodiment. Other equivalent embodiments will be apparent to those of ordinary skill in the art.

[0277] The present invention also includes a dynamic ASIB, the AI Superintelligence Application Service Information Base of ASMP.

[0278] The following sections cover an overview of the architecture for the ASIB, as the enterprise needs to be customized for each Merchant or organization. To accomplish this, a uniform interface is provided which will allow the Merchant or organization, to provide a customized interface for the business or management ASI_IDs. A library provides the core parser and interpreter for the ASIB. It also is the base class for business and management ASI_IDs, which will interface with the enterprise interface.

[0279] Architectural Overview: The architecture of a an ASI Application data structure ASI_ID in the preferred embodiment requires four parts:

• • [0280] 1. The Extended Finite State Machine (EFSM) ASIB in the CoreBusinessASI_ID or Management ASI_ID (C++).
    State is the set of values describing the current position of the machine if it has memory.
    Transition is the action and state change performed by the machine after it receives an event.
    Event is the inbound trigger which causes the machine to perform a transition.
    Action is the output of the machine as a result of a transition.
    Diagram is a complete finite state machine description containing states and transitions.
  • [0281] 2. ASMP interface for the business or management ASI_ID to the ASIB. (C++);
  • [0282] 3. The enterprise interface protocol (specification);
  • [0283] 4. The ASIB instructions for the business or management ASI_ID (EISM, which stands for Enterprise Interface State Machine).

[0284] The first item (ASIB and CoreBusinessASI_ID or management ASI_ID) is built once. This is part of the ASMP library. The second item is built as a common business or other ASI_ID and should be generic enough to be configurable for different merchants or organizations. The third item is a specification that must be written by the merchant or other organization for its own enterprise interface. The fourth is configurable during runtime for different business or other organization or management ASI_IDs.

[0285] The following sections discuss the ASIB and CoreBusinessASI_ID or management ASI_ID, as well as show an example BankAccount ASI_ID which has two different merchant enterprise interfaces.

[0286] A simple Finite State Machine (FSM) consists of two items: a set of states S and their possible transitions T. A transition t consists of an initial state ts, and event e which triggers an action a, and a final state tf. An example consists of two states S={A, B} and two transitions T={t1, t2}. The transitions can be described as t1=(A, X, Y, B) and t2=(B, U, V, A). The transition t1 from state A to state B is triggered by an event X and causes an action Y. Likewise, the transition t2 from state B to state A is triggered by an event U and causes an action V. If the finite state machine is in state A and receives any event besides X, it will remain in state A. Only when a valid event occurs (by having a defined transition) does the FSM change its state.

[0287] In a formal FSM, the set of states is indeed finite. However, often an extended FSM, called the dynamic ASIB, is needed. Here the states are not finite, per se; there exists a number of finite state “blocks” on the diagram, but there are also global variables which may store values which may take on an infinite number of possibilities. This adds another dimension to the FSM and makes the whole system have an infinite number of “states”.

[0288] As an example, consider a simple counter that receives an input trigger and outputs an integer one greater than the previous output. The input event is anything. The output action is the integer “count”. In the formal FSM, there would need to be a state for each possible integer value. If the counter had a limit of 10, then there would be eleven states: an initial state and one for each output value. However, if an infinite counter were needed, an infinite number of states would be needed.

[0289] However, if an extended FSM or ASIB is used, there would only need to be one state. This is the idle (or initial) state. The counter would simply output the count value and increment this value.

[0290] The state machine is interpreted allowing for bytecode compilation into a stack machine opcode.

[0291] The stack machine allows for a simple implementation and compilation of the parsed state machines.

[0292] The state machine described in the preferred embodiment uses the scheme to create an intermediate bytecode, which is interpreted by the stack machine. The ASCII input file is passed off to the parser which converts this to the byte code. The byte code can then be used to run the stack machine (as a state machine) or to the dump program which creates an ASI_ID file dump of the instructions and the symbol table.

[0293] The parser will take the input ASCII, parse it for syntax and syntactical errors, and then create a stack machine instruction set for the resulting state machine. The conversion of the state machine diagram into a stack machine saves time for the run time interpreter and does the preprocessing of the symbol table.

[0294] The interpreter is now just a simple stack machine, which does receive input events and sends out actions. The stack machine contains a very limited set of instructions, which simply perform the basic arithmetic and conditional chores at run time.

[0295] All business or management ASI_IDs must interface with the back-end channel to communicate with the enterprise computer. Hence, the core business or management ASI_ID, from which all of the business or management ASI_IDs derive, must have embedded in it the FSM to be able to parse the EISM ASIB configured with diagrams.

[0296] The core business or management ASI_ID must be remotely accessible and therefore must be integrated within the ASI_ID payload. It has the interfaces for the enterprise interface and the FSM. The following example illustrates the description of an example of a CoreBusinessASI_ID or Management ASI_ID.

[0297] The back-end communication channel must be customized for each customer for their given application. Since this back end channel will be different for each customer, a program capable of handling the different capabilities and customizable features per customer is needed.

[0298] As illustrated below, consider a simple bank account class, which has a balance query and withdraw and deposit methods to change the account balance:

		class BankAccount {
		int balance( ) const;
		void withdraw(int amount);
		void deposit(int amount);
		}

[0299] Talking to the back-end may vary from merchant to merchant. Therefore, an intermediate machine needs to connect with the back-end to communicate using a name-value pair protocol, which is modifiable. Consider two banks, BofA and Fidelity. BofA may query the back-end for a balance of an account by sending the account number and then the word “balance: query”. This can be summarized as follows:

		send(“account number”)
		send(<eid>)
		send(“balance:query”)
		expect(“amount”)
		expect(amount)
		return amount

[0300] The other bank Fidelity may require the account number being set, receiving this confirmation and then send the “balance” query. This can be summarized as follows:

		send(“account-number”)
		send(<account number>)
		expect(status)
		send(“balance”)
		expect(amount)
		return amount

[0301] The second bank Fidelity contains more steps and can have more error conditions. Both of these cases can also be described using an FSM and ASIB EISM to configure the BankAccount class.

[0302] For a single expected string, the use is straightforward. However, to use the expect state for more than one string (more than one expected response), one must make use of the “extended” nature of the ASIB EFSM. Namely, one must use global variables to store the other dimension of state. These two bank examples show how different merchant back-ends can make use of the same business or management ASI_ID.

[0303] The bank ASI_ID class structure was shown above. However, since this will be derived off of the CoreBusinessASI_ID or Management ASI_ID it follows that this BankAccount ASI_ID needs an ASMP definition, assuming these three methods: balance, withdraw and deposit:

[0304] After compiling this ASMP ASI_ID, one can then add the hooks to provide the method connections to the FSM for this particular business ASI_ID.

[0305] Thus, a method and apparatus for a thinking system using an ASI distributed Application State Machine and ASI Command, Control, Communications and Computer Intelligence (C4I) system for independent, intelligent AI Prompting and ASI Browsing, using a configurable AI Superintelligence Application Layer Switch are disclosed. These specific arrangements and methods described herein are merely illustrative of the principles of the present invention. Numerous modifications in form and detail may be made by those of ordinary skill in the art without departing from the scope of the present invention. Although this invention has been shown in relation to a particular preferred embodiment, it should not be considered so limited. Rather, the present invention is only limited by the scope of the appended claims.