B.3:2 - Problem

Five failures recur:

1. Assurance by appearance. A badge, dashboard, attestation, card, status, or publication is treated as the assurance conclusion.
2. One scale for unlike properties. Formality, reliability, coverage, congruence, and evidence quality are placed in one tuple even though they have different bearers and scales.
3. Unsupported aggregation. min, an average, a penalty, or another fold is called conservative without a dependency model and calibrated quantities.
4. Process burden by default. Every result is required to name dated Work, Method, assignment, bindings, and a reusable record even when the claim’s own basis closes the use.
5. Domain obligations absorbed into assurance. Safety, rights, access, responsibility, contest, redress, status, or controlled-action rules are replaced by a generic assurance record.