The model quality report checks the population against uniqueness constraints, totality constraints, subset constraints and data types, but not against ring constraints.

As a result a ring constraint can be declared on a fact type while the population contradicts it, and nothing reports it. Examples: a symmetric relationship where both directions have been entered, so the same situation is stated twice; an irreflexive relationship where something is related to itself; an asymmetric relationship where both directions are present; a relationship declared free of cycles where the population contains one.

For a symmetric relationship the useful finding is the redundant one: once symmetry is declared, entering the reverse as well states the same fact twice, which is exactly what a population is supposed to avoid. Both readings can still be verbalized from the single stated fact.

Expected: the population is checked against the declared ring constraint, in the same way as the other constraint types.