I have been stewing on your problem and don't think your solution is probably the right one. I see a few issues like how do you distinguish maker updates from checker updates because for a trigger to allow one and send the changes off to another table for verification it needs to be able to tell EVERYTIME. The next question is do you need this setup or do you really need to make sure that you can go back to a former version of the record AND know who changed it. Also based on your solution you can approve a single field, how do you plan to handle related field changes, ie: state changed and so did city but you only approved state, result = invalid address.
If you are going to do this you should probably do it as a whole record approval/disapproval but you still need to be sure that there is an iron-clad way to tell the difference between maker and verifier.
I guess it comes down to, what is the problem or business requirement you are trying to solve for?