Generate alerts based on scenarios

[stevebauman]

Alongside #2, a scheduled job should run and look over changes that have been recorded in Scout to look for issues and generate alerts with severity.

[TravisWilder]

would be create to be able to create also some rules (via code -not gui) not only to review changes and report issues to them.
like user with settings like PW do not expire (which is not valid for us)

[stevebauman]

This may be difficult - I'm not sure how I can allow devs to use custom code in an application that is installed via a git clone, as it could be overwrote by a git pull origin {new-version}, or prevent you from updating due to possible conflicts.

I believe have two options (there may be more, I'm unsure of other ways):

1. Convert Scout to use packagist instead and then have devs / users create a Laravel application and then composer require directorytree/scout
2. Create an "update" process inside the application that performs updates for you using a web GUI, unzips the applications contents and overwrites the local application contents but leaves any locally created files untouched

Thoughts?