Shipping a simple cause sensitive flagging scheme

As the task of forging a custom flagging scheme is not without pitfalls and also a little underdocumented, i would like to add another basic flagging scheme that discriminates towards the "cause" of a flag. I think this would make accessible our history mechanics to config-users much more straight forwardly and also demonstrate the power/complexity of the history mechanics more visibly.

I know we have the dmp-scheme, but that is a little too blown up with regards to its specific focus on a specific data scheme.

I imagine a 2-column scheme, holding the flagging value in one column and the "cause" in another. The cause field, i imagine as jut being the label set with the test application, or, if not given, just the functions name.

Background is, that in hands-on/workshop sessions exactly that kind of thing is searched for. In a current case, a user generated variables with the flagging result of each test separatly just to be able to discriminate for the test cause afterwards. The process of generating an own flagging scheme, i think is currently not really doable without some lead or experience, so usually one is left with suggesting the use of the dmp scheme. I just think there should be a more vanilla/neutral scheme available in the range between dmp and no-history sensitivity.