Namespace Engine key to RBAC

Mike's Notes

After a bit of experimentation, it turns out the Namespace Engine (nsp) is key to reliably implementing RBAC globally.

Resources

• https://learn.ajabbi.com/eng/9/docs/index.html
• https://www.blog.ajabbi.com/2025/01/pipi-and-its-databases.html
• https://www.blog.ajabbi.com/2025/02/how-to-set-pipi-configuration.html
• https://www.blog.ajabbi.com/2022/12/pipi-8-2021-2022.html
• https://www.blog.ajabbi.com/2025/09/rbac-policies.html
• https://www.blog.ajabbi.com/2025/09/rbac-causes-change-to-deployment-engine.html
• https://www.blog.ajabbi.com/2025/09/role-based-access-control-rbac.html

References

• Reference

Repository

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

Last Updated

12/09/2025

Namespace Engine key to RBAC

By: Mike Peters

On a Sandy Beach: 12/09/2025

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

This afternoon, I figured out that the Namespace Engine (nsp) already has a way to register the interfaces of every agent that is automatically built by the Factory Engine (fac). This includes industry domain-based applications, such as Websites, Health and Rail.

I added additional Interface Class Types, "Role", and "Policy", and solved the problem of making this global.

Roles

This allowed for the rapid addition of roles to any autonomous agent.

Examples

• Website Owner
• Website Administrator
• Website Editor
• Website Visitor
• Website Search Engine
• etc

This automatically generates security role names used by the Security Engine (scr).

Policy

This allowed for the rapid addition of policy to any autonomous agent.

Examples

• CNAME Record
• Website Hosting
• Patient Record
• etc

This automatically generates security policy names used by the Security Engine (scr).

Integration

This would also enable configuration storage in XML or other open formats for interchange and documentation.

This configuration system could be used for open-source SaaS applications.