20 Engines

Mike's Notes

While I finish off testing the Pipi System Engine (sys), here is the plan for the next stage.

Update 27/04/2026

Today, I have also been setting up some new twin 27" monitors to help with coding. I need larger 16pt Arial or Noto Sans font sizes these days.😎

Resources

• https://www.blog.ajabbi.com/2026/04/testing-pipi-system-engine-sys.html
• https://developer.ajabbi.com/eng/9/report/roadmap.html
• https://wiki.ajabbi.com/eng/9/engines.html

References

• Reference

Repository

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

Last Updated

27/04/2026

20 Engines

By: Mike Peters

On a Sandy Beach: 26/04/2026

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

Project

This project is the importation of 20 engines necessary for Pipi to self-manage with a minimal set of internal features, no adaptation or self-evolution. That will come later.

Variables

All of these engines have worked for years (some with origins dating back 26 years) and are mature and stable, but have been migrated from a laptop to a data centre, where the host environment differs. I forgot to sort that out first. 😎 The Nest Engine (nst) was rapidly invented to solve that problem, but the variables generated by the nest are also causing name clashes.

Process

Each engine needs the same minor tweak as it is imported. I'm carefully checking all spelling in each engine. Each engine is then left running while I watch the logs. Once the log engine is imported, logs can be visualised in Mission Control using third-party open-source tools. This will speed things up a lot.

20 Engine import list

In no particular order.

1. System Engine (sys)
2. Nest Engine (nst)
3. Namespace Engine (nsp)
4. Variables Engine (var)
5. Render Engine (rnd)
6. Template Engine (tem)
7. Log Engine (log)
8. Data Engine (dta)
9. Configuration Engine (cnf)
10. Versioning Engine (ver)
11. Code Engine (cde)
12. Conductor Engine (cnd)
13. Directory Engine (dir)
14. Node Engine (nde)
15. CMS Engine (cms)
16. Core Engine (cor)
17. 
    

Pipi is the IDE

I built Pipi using Pipi, so I'm stuck in chicken-and-egg land at the moment. The more engines are imported, the easier this will get. I have a rough idea of the import order, but all subject to change.

Pipi Editions

Each engine is like a different kind of Lego brick, and each Pipi is built out of hundreds of these bricks. The 4 Editions are built with the same bricks, combined in different ways. The Instances of any Edition are built exactly the same, but their databases with the same data models will store different histories, weights, parameters, etc., as they adapt and evolve.

DevOps Engine (dvp)

The DevOps log below is currently maintained manually, but will be generated automatically once the DevOps Engine (dvp) is back up and running. These logs will be automatically published on the Ajabbi Developer website using an interactive format with more detail.

---

DevOps log (edit)

A record of work done.

NZ DateTime	Action	Engine	Status
	Test	System Engine (sys)
	Create	Nest Engine (nst) - Code for Linux vs Windows path delimiters.
	Test	Nest Engine (nst)
	Test	Namespace Engine (nsp)
	Test	Variables Engine (var)
	Test	System Engine (sys)
	Import	Render Engine (rnd)
	Edit	Render Engine (rnd) - variables.
	Edit	Render Engine (rnd) - spelling.
	Test	Render Engine (rnd)
	Test	Render Engine (rnd) - run Nest Engine (nst) templates to create a nest.
	Test	System Engine (sys)
	Import	Template Engine (tem)
	Edit	Template Engine (tem) - variables.
	Edit	Template Engine (tem) - spelling.
	Test	Template Engine (tem)
	Import	Template Engine (tem) - import temporary nest templates
	Test	System Engine (sys)
	Test	Render Engine (nst) + Template Engine (tem) + Nest Engine (nst)
	Test	System Engine (sys)
	Create	Temporary web form UI for each engine
	Test	Temporary web form UI for each engine
	Import	Log Engine (log)
	Edit	Log Engine (log) - variables.
	Edit	Log Engine (log) - spelling.
	Test	Log Engine (log) - CRUD log file formats
	Render	Log Engine (log) - logs
	Import	Graphing library for logs
	Create	Embed visualisations on Mission Control web pages.
	Test	System Engine (sys)
	Import	Data Engine (dta)
	Edit	Data Engine (dta) - variables.
	Edit	Data Engine (dta) - spelling.
	Test	Data Engine (dta)
	Test	System Engine (sys)
	Import	Configuration Engine (cnf)
	Edit	Configuration Engine (cnf) - variables.
	Edit	Configuration Engine (cnf) - spelling.
	Test	Configuration Engine (cnf)
	Test	System Engine (sys)
	Import	Versioning Engine (ver)
	Edit	Versioning Engine (ver) - variables.
	Edit	Versioning Engine (ver) - spelling.
	Test	Versioning Engine (ver) - automatic versioning.
	Render	Versioning Engine (ver) - version logs
	Test	System Engine (sys)