Implementing the prevention is not as easy as the cures. In other words, we cannot use a Firebase object and hold everything over there. Instead we have to use a service to keep track of implemented cures - called prevention, because when they are in place, their role is to prevent something bad from happening.
Take the current noted cure, for example: it says we want to see if an article is within an acceptable range. So if we implement that mechanism inside the Evidence service and keep an eye on how that service deals with defects, we accomplish two major goals.
First, we have the chance to weed out the problematic articles. This is not a big deal, in fact we could do that by adding a simple condition check in the evidence service and we wouldn't need to implement another service to do that for us.
Second, we can analyze the URL related to that problematic article and find out why we ended up with extra long or extra short content and THAT is what we can't accomplish...