The definition of pseudOS is as follows:
"pseudOS is a design methodology that emulates multi-tasking functionality at the application level."
The details of the origins and usage of pseudOS are outlined in the "Overview" doc, but I will give a brief abstract here.
Basically, it is generally accepted practice to use an RTOS (Real Time Operating System) on applications that require complex multi-tasking behavior and time-critical responses to external events. Many times applications start out being programmed using a "standard" approach, but as prioritization, resource management, time-critical response issues and other requirements become more prevalent in the design, the entire project can collapse under its own weight. A typical scenario is a function that is constantly checking to determine whether it needs to exit or call a more critical function. As the combinations and permutations increase, the process grows exponentially and the functional cross-dependencies become unsustainable and unmanageable.
An RTOS is designed specifically to address these issues, by establishing an external execution control manager as the OS kernel. What pseudOS does is to provide an alternative solution to the same class of problems that typically require an RTOS, without the need for an OS kernel. pseudOS is not a panacea, nor intended to replace all instances where an RTOS might be considered useful. However, as a design methodology, it is surprisingly versatile, and will often be limited only by the creative vision of the programmer. Once a simple set of rules for setting up an infrastructure to support the pseudOS state machine are followed, programming proceeds in an efficient and intuitive manner, using standard ANSI C.
pseudOS applications even have a different "look and feel". They tend to appear more list- and table-driven, which also aids in clarity and ease of maintenance.
Although pseudOS appears to hold promise as a novel and viable programming methodology, having many inherent advantages over most mainstream approaches that are taught today, I am currently seeking a collaborator in the academic field who can vet the materials and provide an accurate perspective of where it fits into the grand scheme of things, from a theoretical perspective. I have been approaching the subject entirely from a practical embedded engineering standpoint and the new techniques have been showing great promise in my own designs. However, it is important that someone with the proper "gravitas" be involved in the public dissemination of this information, if nothing else to avoid the making of false claims. Probably the most practical vehicle for full release of this material would be in book form.