Mike's Notes
I'm writing up some notes on current work driven by a teaching customer.
Resources
- Resource
References
- Reference
Repository
- Home > Ajabbi Research > Library >
- Home > Handbook >
Last Updated
02/09/2025
The internal control hierarchy of Pipi
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
Descriptions
Account
Every customer or user has an account, which is opened when they sign up.
Each customer account;
- It is of only 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
Each deployment;
- It has only one deployment tenancy type.
- Is in 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
Each deployment object;
- Is 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).
Each publication;
- Is one publication type.
- It can be combined to build a whole system.
- Code
- CSS
- Database
- Deployment
- Email Newsletter
- Notebook (Jupyter, etc)
- Website
- XML
- etc
Website
Each website;
- Is one language.
- Is one website type.
- Can be combined with other websites (to become a multi-language website).
- API (Endpoints)
- Docs (like JavaDocs)
- Help
- Website (standard)
- Wiki
- Workspace (enterprise applications)
- etc
Example
How internal names are automatically provided by Pipi, using the example of 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/ eng.example.com workspace.example.com/eng/ |
