Explain to me this casbin rule {
 p\_type: 'p',
 v0: 'admin',
 v1: '/:company/:project/:team',
 v2: '/companies/public-domains',
 v3: 'POST',
 },
The rule you provided is in the context of Casbin, an authorization library that supports access control models like ACL, RBAC, ABAC, etc. The rule specifies a permission that defines what actions a user or role can perform on certain resources. Let's break down the components of this rule:

- **p_type: 'p'**: This indicates that this is a policy rule. In Casbin, policies can be defined for permissions (denoted by 'p') or for roles (denoted by 'g' for grouping).

- **v0: 'admin'**: This represents the subject or role that the rule applies to. In this case, it specifies that the permission is granted to the 'admin' role.

- **v1: '/:company/:project/:team'**: This is the resource path that the rule applies to. The colons (:) indicate variables in the path, meaning that this rule applies to any resource that matches the structure of the path. For example, it would match URLs like `/companyA/projectX/team1`, `/companyB/projectY/team2`, etc.

- **v2: '/companies/public-domains'**: This is another resource path, which could represent a specific endpoint that the 'admin' role has permission to access. This path is more specific and does not have variables.

- **v3: 'POST'**: This specifies the HTTP method that is allowed for the resource paths defined in v1
Explain to me this casbin rule {
 p\_type: 'p',
 v0: 'admin',
 v1: '/:company/:project/:team',
 v2: '/companies/public-domains',
 v3: 'POST',
 },
 { p\_type: 'p',
 v0: 'user',
 v1: '/:company/:project/:team',
 v2: '/companies/public-domains',
 v3: 'GET',
 },
 { p\_type: 'g',
 v0: 'user',
 v1: '/:company/:project/:team',
 v2: 'create',
 },
 { p\_type: 'g',
 v0: 'user',
 v1: '/:company/:project/:team',
 v2: 'delete',
 },
 { p\_type: 'g',
 v0: 'admin',
 v1: '/:company/:project/:team',
 v2: '*',
 }

This is a Casbin rule set that defines permissions for a hypothetical web application. Casbin is an authorization library that uses a policy-based access control (PBAC) model.

Let's break down each rule:

1. `{ p_type: 'p', v0: 'admin', v1: '/:company/:project/:team', v2: '/companies/public-domains', v3: 'POST' }`
   This rule grants the 'admin' role the permission to post data to the `/companies/public-domains` endpoint within a specific team (rep