The internal control hierarchy of Pipi

Mike's Notes

I'm writing up some notes on current work driven by a teaching customer.

i18n

• For Languages, a 3-letter string is added. e.g. eng for English and mri for Maori.
• For Locales, a 2-letter capitalised string is added. e.g. eng-GB for English spoken in the UK, eng-US for English spoken in the United States.

Resources

• https://www.blog.ajabbi.com/2025/01/design-token-based-ui-architecture.html

References

• Reference

Repository

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

Last Updated

07/09/2025

The internal control hierarchy of Pipi

By: Mike Peters

On a Sandy Beach: 02/09/2025

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

Pipi is a self-organising system. Self-regulating constraints are operating on internal models. There are numerous internal hierarchies of control within Pipi, with properties that are inherited, including multi-inheritance.

Examples include;

• Class packages: eg, namespace
• Nested systems: eg, Account > Deployment > Deployment Object > Publication > Website > Workspace
• Schema, ontologies, etc: eg, SNOMED, MovieLab
• Design systems: eg, Account > Design System > Component > Design Token

Descriptions

Account

Every customer or user has an account, which is opened when they sign up.

A customer account has these properties;

• One account type.
• Contains one or more deployments.

Account types:

Each account type comes with different options. Enterprise has the most options, and Individual has the least.

• Enterprise (paid).
• DevOps (paid).
• SME (paid).
• Individual (free).

Deployment

A deployment has these properties;

• One deployment tenancy type.
• One language.
• Contains one or more deployment objects.
• Can contain other deployments to create global settings for an account (Enterprise or DevOps).

Deployment tenancy types:

• Exclusive tenancy
• Shared tenancy
• System

Deployment Object

A deployment object has these properties;

• One deployment object type

Deployment Object Types:

Used by the administrator through configuration settings.

• Billing
• Datasource
• Folders
• Permission
• Plugin
• Publication
• Usage
• Users and Groups
• etc

Publication

All publications are created by the Content Management System (CMS).

A publication has these properties;

• One publication type.
• Can be combined to build a whole system.

Publication Types

• Code
• CSS
• Database
• Deployment
• Email Newsletter
• Notebook (Jupyter, etc)
• PDF
• Website
• XML
• etc

Website

A website has these properties;

• One language. 
• One website type.
• Can be combined with other websites (to become a multi-language website).

Website types

• API (Endpoints)
• Docs (like JavaDocs)
• Help
• Website (standard)
• Wiki
• Workspace (enterprise applications)
• etc

Example

ASCI internal names are automatically provided by Pipi. 

An example control hierarchy;

Account > Deployment > Deployment Object > Publication > Website > Workspace.

Inheritance	Internal name	Examples
Account	<ASCI characters>	ajabbi
Deployment	<Account>-<4 Digit>-<Locale>	ajabbi-0001-eng-uk
Deployment Object	<Deployment>-<ObjectType>	ajabbi-0001-eng-uk-pub
Publication	<Deployment Object>-<Publication Type>	ajabbi-0001-eng-uk-pub-cde ajabbi-0001-eng-uk-pub-dta ajabbi-0001-eng-uk-pub-wbs
Website	<Domain>	wiki.ajabbi.com/eng/ blog.example.com/en-nz/ eng.example.com workspace.example.com/eng/