Attempt at user <-> proof <-> requirement modeling 

Ok, this is an example of how I would change the relationships between user, proof and requirement, with changes to views, controllers, models and with passing specs (I cleaned them up a bit, they were getting messy and not DRY).