Pundit Spike

:construction: Understanding the original decisions made for the built in authorization lib I still think using [Pundit](https://github.com/elabs/pundit) instead of something homegrown has its advantages so this pull explores what implementing Pundit would look like. Here are some advantages that come to mind.

- Overall reduction in application LOC
- Isolated authorization library and test coverage leads to less cognitive overhead
- Open source contributes
- Pundit API is _very_ similar to built in authorization lib