Testing the Pipi System Engine (sys)

Mike's Notes

The next long batch of work starts today. I'm working this out as I go, and I don't yet know how long this will take. The plan will likely change. I hope the start will be the hardest part, and then it will get easier. But I have been wrong before. 😎😎😎😎😎😎😎

Dwight D. Eisenhower’s philosophy on planning is best summarized by his famous quote,

"Plans are worthless, but planning is everything".

He emphasized that while rigid, written plans fail upon first contact with reality (or the enemy), the process of planning prepares leaders to adapt, coordinate, and react intelligently to unexpected emergencies. - Wikipedia

Big picture

I want to double-check everything as I go and complete or archive any unfinished work without doing upgrades.

Speed is king

Go as fast as hell. Trust Pipi's ability to self-repair.

Resources

• https://www.blog.ajabbi.com/2026/04/pipi-nest-update-what-i-learned-this.html
• https://www.blog.ajabbi.com/2026/02/having-data-centre-changes-roadmap.html

References

• Reference

Repository

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

Last Updated

21/04/2026

Testing the Pipi System Engine (sys)

By: Mike Peters

On a Sandy Beach: 21/04/2026

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

Anatomy 101

The Pipi System Engine (sys) is like the whole (hence the name "loki"). It has an outer boundary and is built from hundreds of other kinds of engines nested up to 27 layers deep. There can be many copies of each engine type. There are also hundreds more engines waiting to be imported from the Pipi 6, 7, and 8 archives.

Engine-Agent Duality

Each engine is also an autonomous agent without tokens, is stateful, and learns slowly. There are no prompts.

Pipi Nest

The nest is a container.

It acts as an interface between;

• The external environment
• Computer
• O/S
• Application Server
• Pipi System Engine (sys)

The nest has hidden internal Pipi Variables like;

• PIPI_JAVA_EDITION
• PIPI_NEST_NAME
• PIPI_SYSTEM_OS

The only engine the nest can communicate with is the Pipi System Engine (sys).

Test Process

It makes sense to move each engine one by one and check that messaging is working using the Pipi Variables.

The first Engine to test is the Pipi System Engine (sys). Once tested, it will be left running, with live logs for monitoring.

Down the rabbit hole

Its internal engines will then be added one by one for testing and commissioning.  Most engines should be good to go, but everything needs to be carefully checked.

Each engine consists of one or more engines. These engines can communicate with each other. There are internal structures that act as membranes and pathways. Each engine can also operate at reduced capacity if it is the only engine, which will help with staging and initial testing. Then watch the logs as more engines are slowly added.

Critical threshold

There are about 20 of these engines necessary for emergent behaviour to become dominant enough for self-management to operate reliably. Those are the engines I will start on first. Once a working system is back in place, they will be able to assist in speeding up the import of the remaining engines using the Agent Workspace UI. A set of simple web forms should do it.

Engine Logs

Things that I have seen before to watch out for include

• Power Laws
• Fractals
• Noise
• and other crazy stuff 😎

It's Pipi's patterns of behaviour that fascinate me. Maybe it's from the feedback loops?

Mission Control

I need to find a light, open-source graphing tool that can visualise these logs and be embedded on web pages. Like Houston, there will be a big live screen monitoring everything. As progress is made, A video camera can point at the screen to live-broadcast on YouTube for anyone who's curious or for online talks. This maintains a physical network separation of the data centre from the internet.

Test Results

NZ DateTime	Action	Engine	Status
2026-04-21 11:58	Import	System Engine (sys)	Complete
2026-04-22	Test	System Engine (sys) - Consistent variable names.
2026-04-22	Test	System Engine (sys) - connect to 9cc/ Nest
2026-04-22	Create	Nest Engine (nst)
2026-04-22	Test	Nest Engine (nst) - Code for Linux vs Windows path delimiters.
2026-04-22	Test	Nest Engine (nst) - Accurate nest build definitions.
2026-04-22	Create	Nest Engine (nst) - Temporary templates.
2026-04-23	Import	Render Engine (rnd)
2026-04-23	Test	Render Engine (rnd)
2026-04-23	Test	Render Engine (rnd) - run Nest Engine (nst) templates to create a nest
2026-04-24	Import	Template Engine (tem)
2026-04-24	Test	Template Engine (tem)
2026-04-24	Import	Template Engine (tem) - import temporary nest templates
2026-04-24	Test	Render Engine (nst) + Template Engine (tem) + Nest Engine (nst)
2026-04-25	Create	Temporary web form UI for each engine
2026-04-25	Test	Temporary web form UI for each engine
2026-04-26	Import	Namespace Engine (nsp)
2026-04-26	Test	Namespace Engine (nsp)
2026-04-26	Test	Namespace Engine (nsp) - Sync variable names.
2026-04-	Import	Log Engine (log)
2026-04-	Test	Log Engine (log) - CRUD log file formats
	Import	graphing library for logs
	Import	Data Engine (dta)
	Test	Data Engine (dta)
	Import	Configuration Engine (cnf)
	Test	Configuration Engine (cnf)
	Import	Versioning Engine (ver)
	Test	Versioning Engine (ver) - Automatic versioning.