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.
Mrs Grammarly
And fix all my spelling mistakes. Some of this was built years before I had Mrs Grammarly and is only now being discovered. A lot of spelling mistakes. Oh dear!. 😎😎
Mrs. Grammarly's Last Request
Noisy, noisier, noisiestOur teacher's last requestBefore she took the planeTo somewhere warm in SpainBecause her nerves were brokenBy words so loudly spokenFor twenty-five years withoutA respite, there's no doubtJust remember this rule pleaseShe said with great uneaseDrop the y and add an iWhen comparing things wherebyYou'll cheer this poor old teacherAnd peace will finally reach her.- Old Faithful
Speed is king
Go as fast as hell. Trust Pipi's ability to self-repair.
Update 22/04/2026
Again, as with the recent Pipi Nest update, progress is painfully slow but steady. I now strongly suspect that the changes I need to make to System Engine (sys) will apply to all engines. Once the necessary solution is found, every engine will be easily altered. So very slow at the beginning, then very fast.
Update 23/04/2026
Its definitly a problem with named variable clashes and variable scopes. Now I know what to fix.
Update 29/04/2026
I'm having a break while the mental simulations run.
Update 19/05/2026
Now I know exactly how to fix it. The variable scopes have boundaries, with translation between them. The Nest revisions will also enable auto-installs on VMs, Docker, Windows, and Linux servers. Variable naming is now 100% predictable and can be automated.
Update 27/05/2025
Nest Engine (nst) renamed as Nestspace Engine (nst)
Resources
- https://www.blog.ajabbi.com/2026/04/pipi-nest-update-what-i-learned-this.html
- https://wiki.ajabbi.com/eng/9/engines.html
- https://www.blog.ajabbi.com/2026/02/having-data-centre-changes-roadmap.html
- https://www.blog.ajabbi.com/2026/02/using-slide-presentations-to-describe.html
- https://allpoetry.com/poem/13763142-Mrs.-Grammarly-s-Last-Request-by-Oldfaithful/
References
- Reference
Repository
- Home > Ajabbi Research > Library >
- Home > Handbook >
Last Updated
27/05/2026
Testing the Pipi System Engine (sys)
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
Every engine is also an autonomous agent.
- Engines are deterministic
- Stateful
- Imprinted by the path taken
- Formal Logic
- Agents are probabilistic
- No AI tokens
- No prompts
- Dialectical logic
Nestspace
The Nestspace is a container.
It acts as an interface between;
- The external environment
- Computer
- O/S
- Application Server
- Pipi System Engine (sys)
The Nestspace has hidden internal NEST Variables like;
- NEST_JAVA_EDITION
- NEST_NEST_NAME
- NEST_SYSTEM_OS
The only engine the Nestspace 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
About 20 of these engines are necessary for emergent behaviour to become sufficiently dominant 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 help speed up the import of the remaining engines via 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 😎
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.
DevOps log (edit)
A record of work done.
| NZ DateTime | Action | Engine | Status |
|---|---|---|---|
| 2026-04-21 11:58 | Import | System Engine (sys). | Complete |
| 2026-04-22 11:44 | Edit | System Engine (sys) - Application.cfc. | Complete |
| 2026-04-22 13:24 | Edit | System Engine (sys) - reassign VARIABLE scopes. | Complete |
| 2026-04-22 13:31 | Test | System Engine (sys) - connect to Nest /9cc/. | Success |
| 2026-04-22 13:45 | Edit | Rename /pipi/pipi_system.cfm as pip/pipi_version.cfm. | Complete |
| 2026-04-22 13:48 | Edit | Add /sys/pipi_system.cfm. | Complete |
| 2026-04-22 18:13 | Move | Migrate databases. | Complete |
| 2026-04-22 18:47 | Test | System Engine (sys) - Consistent variable names by checking the Namespace Engine (nsp). | Success |
| 2026-04-24 10:55 | Create | Nestspace Engine (nst) | Complete |
| 2026-04-24 10:58 | Import | Namespace Engine (nsp) | Complete |
| 2026-04-25 17:19 | Test | Nestspace Engine (nst) - Accurate nest build definitions. | Complete |
| 2026-04-25 20:49 | Create | Nestspace Engine (nst) - Temporary templates. | Complete |
| 2026-04-26 07:44 | Test | Namespace Engine (nsp) | Complete |
| 2026-05-18 08:21 | Edit | Rename Nestspace files. | Complete |
| 2026-05-19 11:56 | Edit | Restructure Nestspace code. | Complete |
| 2026-05- | Test | Nestspace auto-install | |
| 2026-05- | Test | Namespace Engine (nsp) - Sync variable names. | |
| 2026-05- | Edit | Nestspace <> Instance <> Version <> System - Change variable outputs. | |
| 2026-05- | Test | Nestspace <> Instance <> Version <> System. |
