Authorization and per-subproject roles assignment (Myth::Auth?)

@rmilecki Almost! `mayList()` is a model function - you can think of it like a directory: "Can the current user list files in this directory?" In your example above you probably want `if (! $company->mayRead())` - equivalent to "Can the current user view this specific file?"

Docs and examples are definitely on the list, but there's a lot of raw content I still need to create for the framework itself and these modules before I come back to some of the refining. I would love some community help, so if you find this module useful and want to make some recommendations or PRs please do! Even just hearing about what is confusing can be useful.

---

Why Auth and Permission in 2 other packages?

I see no reason why that should be the case. Permits was designed specifically to work with another package for Authentication and general user Authorization, with Myth:Auth specifically in mind. The type of authorization offered by Permits is rather unique and not going to be applicable to as many projects as something like Myth:Auth. At the same time it would be silly to rewrite all the authentication code just to keep it "under one roof".