Putting a wrapper around Pipi

Mike's Notes

I had an epiphany while building out the new workspace UI yesterday.

Resources

• https://en.wikipedia.org/wiki/Wrapper_function
• https://en.wikipedia.org/wiki/Wrapper_library
• https://en.wikipedia.org/wiki/Headless_software
• https://www.blog.ajabbi.com/2022/12/pipi-8-2021-2022.html
• https://www.blog.ajabbi.com/2023/12/pipi-9.html
• https://www.blog.ajabbi.com/2025/10/industry-workspace.html

References

• Reference

Repository

• Home > Ajabbi Research > Library >
• Home > Handbook > 

Last Updated

23/10/2025

Putting a wrapper around Pipi

By: Mike Peters

On a Sandy Beach: 23/10/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

The new workspace applications smell like a wrapper around Pipi 9.

A GUI is a graphical user interface—windows, menus, tools, etc.— that you can click with a mouse. A wrapper is a piece of software that wraps an existing piece of software, like Pipi 9, and provides its interface (UI).

Headless

Pipi has been a "headless" working system since Pipi 8 in 2021. Getting Pipi to self-generate a UI has been a major task due to the number of rules and configuration standards imported. I wanted to solve some hard usability problems for users, which have taken time to address.

• Accessibility
• Localisation
• Usability
• Personalisation
• Reliability
• Security
• Learning material

Documentation

I have also had to find a way to document a system with a novel architecture and subsystems that no one else uses. And then Pipi uses evolutionary algorithms rather than LLM, plus a lot of other stuff in the mix.

• How to name things that are breaking conventions?
• How to describe processes that are indeterminate yet highly reliable?
• The UI will be a very thin skin on top of a multi-layer system that is at least 28 architecture layers deep.
• There is no version control. Pipi is both the IDE and the source control. It's also the manager.

UI wrapper

It turns out that the new workspace Ui is simple, lightweight and very fast. It has a tiny attack surface, if at all. The UI looks, functions and smells like a wrapper. I figured that out only now while building the UI.

Discovery

I wonder what else will be discovered in this stretch. I have yet to start on the Templates, which are workspace customised configurations, examples include;

• Health
• Modules
• Booking
• Facility
• Cafe
• Clean
• Kitchen
• Security
• Ward
• Room
• Bed
• Health Record
• Health Worker
• Imaging
• Medication
• Patient
• Procedure
• Transport
• Settings
• Billing
• Dashboard
• Plugin
• Users
• Templates
• Allied
• Animal Vet
• Emergency
• Family Doctor Clinic
• Hospital
• Public Health System
• Patient

Thank you

I want to thank the early adopters who are helping me test and provide valuable feedback.