bugs in "surprising" (to me) states

I was poking at an "old" list of bugs I had made, to see if I can ditch my 
list, when I found these.
I've seen 'resolved' as a keyword on a few, e.g. 5522.  I don't remember 
adding it to our menagerie, nor am I sure what it means.  Seems confusing 
to have it both as a kw and as a state.  If it is something we agreed to, 
I need a refresher course.
5523 is not marked external, but it seems like it should be (and decided, 
and should get the boilerplate to trigger Henry to agree or not)
5524 appears to be deserving of decided + boilerplate
5530 seems mis-classified as Satisfied; there is a final comment from 
Henry indicating a need for change, and no response from us.  I realize it 
is going to be vulnerability in our process, that someone can implicitly 
move them out of Satisfied, and we seem to have such a case.  I don't have 
any good (i.e. bulletproof) process solution myself.
5545 appears to be deserving of decided + boilerplate

Best Regards, John

Street address: 2455 South Road, P328 Poughkeepsie, NY USA 12601
Voice: 1+845-435-9470      Fax: 1+845-432-9787