Cascade of permissions on Pipi

Mike's Notes

Making visible the account access right to Pipi.

Resources

• Resource

References

• Reference

Repository

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

Last Updated

14/03/2026

Cascade of permissions on Pipi

By: Mike Peters

On a Sandy Beach: 14/03/2026

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

Think of Pipi as an iceberg. Most of it is hidden underwater. 

This is the matrix of Pipi account permissions. Each account has a different role, creating opportunities for the account above and is dependent on the one below.

Pipi currently has about 3,000,000 lines of code. Most of it is self-generated, so the code volume is a bit of a guess at the moment, based on sampling. (There is no version control, only semantic versioning. 😊 )

Code %	Role	Account	License
0.001	User	Personal	Open-source
1	System	Enterprise
1	System Configuration	Developer
1	Developer Rules	Researcher
1	Pipi Admin	Agent	Closed-core
96	Self-organising	Pipi

Personal Account

• Everyone gets one and uses it to do work
• User interface personalisation
• language
• accessibility
• preferences
• privacy

Enterprise Account

• Run the system
• Security, roles and permissions.

Developer Account

• Configure the enterprise system
• Modules
• API
• Integrations
• IaC

Researcher Account

• Make the rules the developers use
• Import the ontologies
• Add the laws of physics

Agent Account

• Interact with Pipi
• Creates new categories for the researchers.

Pipi

• Autonomous self-organising world-model
• Path taken
• Digital twin
• Swarm
• Learns from account interaction