hi, 2 questions on https://authzed.com/blog/user-defined-roles#adding-role-meta-permissions, not sure i understand the purpose of the built_in role also dont understand howcome the admin still has the delete permission (while project and build_in_role referencing the same project so it actually exclusion of the same relations)

This blog post illustrates a system that allows users to define roles. But sometimes you may want to have a role that comes built-in by default with the system and that you want it to be immutable. That's the built-in role - note how it is not possible to modify it, as defined by the schema. It also solves the chicken an egg problem of assigning some permissions to the first user of the system (e.g. the admin user)

yes i understand the intention. i just confused with the implementation - i dont understhand why this line exists: permission delete = project->role_manager - built_in_role->role_manager and why admin is still eligible for permission delete

> i dont understhand why this line exists: permission delete = project->role_manager - built_in_role->role_manager The idea is to disable the deletion of certain roles considered "built-in"