Problems and evidence

A problem shown by PROVEN starts with something observable in a field, a text fragment, or the catalog structure. It is not a score and not a generic verdict about store “quality”.

#What the result should explain

Depending on the check, evidence can include:

• the field that was evaluated;
• the observed fragment;
• the type of check and how the result can be used;
• details needed to understand the cause;
• an explicit indication when some data was unavailable for evaluation.

#How results are used

Some results can be acted on directly, some need review, and some are kept only for evaluation. This distinction is not a probability or confidence percentage.

#No fabricated totals

If PROVEN can see only part of the catalog or only certain fields, the report says exactly what was checked. PROVEN does not extend conclusions to data it did not analyze.

#Evidence before change

Evidence is the basis for review. A fix can be proposed only when the observed problem and the current source state allow a safe change.

#Continue the process

After reviewing the problem and its evidence, continue with Remediation and control to see how a change is prepared and reviewed before publication.