Creating 18 Engine descriptions

Mike's Notes

18 working engines are currently being imported into Pipi Core, configured, and tested.

Alex has sent me a DeepSeek chat that generated descriptions of those engines and how they worked together by analysing the existing web page "20 Engines". DeepSeek also produced a Mermaid Diagram from Markdown code based on those descriptions. DeepSeek was partially correct in some descriptions.

The Mermaid diagram was wrong, but what a great tool for Pipi to self-document with CL and accurate Markdown descriptions. It will be widely used in future as a plugin.

Feedback and suggestions are very welcome as always.

Resources

• https://www.blog.ajabbi.com/2026/04/agents.html
• https://en.wikipedia.org/wiki/Mermaid_(software)
• https://wiki.ajabbi.com/eng/9/engines.html
• https://chat.deepseek.com/
• https://wiki.ajabbi.com/eng/9/wiki-engine.html

References

• Reference

Repository

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

Last Updated

06/05/2026

Creating 18 Engine descriptions

By: Mike Peters

On a Sandy Beach: 06/05/2026

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

Most Pipi engines have historically been poorly described. This is an attempt to write better descriptions for the 18 engines currently being imported.  I had a go, then used Gemini to come up with better wording, then Mrs Grammarly did her bit. 😎

Much later, once the workspace UI are working, a one-page summary about each engine can be written for the pipiWiki. The Wiki Engine (wik) in the resources above has an example of such a summary.

Descriptions

Each engine has;

• Unique Name (Unique 3-letter code)
• S: Short description suitable for tooltips under 100 characters.
• D: Description under 255 characters.

System Engine (sys)

• S: System identity and lifecycle controller.
• D: Manages the vital signs and lifecycle of Pipi’s dynamic engine ecosystem, fostering complex emergent behaviours through seamless interaction.

Nest Engine (nst)

• S: Host and environment interface bridge.
• D: Serves as the foundational gateway between the host OS, Java, the application server, and the internal Pipi environment.

Namespace Engine (nsp)

• S: Global identification and addressing.
• D: Enforces a conflict-free global naming convention, ensuring every system element is uniquely addressable across the entire platform.

Render Engine (rnd)

• S: Static file and asset rendering.
• D: Processes and renders static resources, including HTML, CSS, source code, and databases.

Template Engine (tem)

• S: Reusable pattern templates.
• D: Manages reusable structural pattern templates used by the CMS to generate database-driven pages and components.

Variables Engine (var)

• S: Centralised variables library.
• D: Provides a centralised repository for managing variables used across templates, system configurations, and executable logic.

Log Engine (log)

• S: Universal logging and telemetry controller.
• D: Aggregates and configures logging parameters across all active engines to provide system-wide transparency and diagnostics.

Data Engine (dta)

• S: Database lifecycle and CRUD operations.
• D: Commands the creation, evolution, and deletion of databases and their underlying data objects with full administrative control.

Configuration Engine (cnf)

• S: Engine blueprint and manufacturing settings.
• D: Supplies the precise DNA and configuration parameters required for the automated fabrication of individual Pipi engines.

Versioning Engine (ver)

• S: Semantic versioning and update tracker.
• D: Maintains system integrity by aggregating incremental updates from all engines into a unified semantic versioning timeline.

Code Engine (cde)

• S: Internal code generation.
• D: Facilitates automated code generation, including class libraries and logic synthesis directly within the Pipi platform.

Conductor Engine (cnd)

• S: Internal process regulator.
• D: Operates as the high-level orchestrator for major internal system processes and synchronisation.

Directory Engine (dir)

• S: CMS file system and path manager.
• D: Manages the logical and physical file system directories generated and utilised by the CMS.

Node Engine (nde)

• S: Hierarchical template tree architect.
• D: Maintains the addressable tree structure of templates to define content hierarchy within the CMS.

CMS Engine (cms)

• S: Digital content management.
• D: Powers the end-to-end lifecycle of digital content, from initial creation and editing to final publishing.

Core Engine (cor)

• S: Primary system driver and logic hub.
• D: The central engine that powers fundamental system behaviours and executes the primary logic that keeps Pipi running.

Factory Engine (fac)

• S: Automated engine fabrication.
• D: Assembles and deploys engines based on stored configuration files and real-time updates.

Page Engine (pge)

• S: Semantic relationship and metadata mapper.
• D: Maps external relationships for pages, managing keywords, references, and "See Also" semantic connections.