A.20:8 - Common mistakes

Mistake	Why it fails	Repair
Class label as truth	`LipschitzBounds` or `TypeDomainRange` does not identify the constraint application.	Name the constraint, edition, case, test, and result.
`abstain` for everything missing	Not applicable, not run, unknown, and policy consequence require different actions.	Keep applicability, evaluation state, outcome, and gate consequence separate.
Missing required result joins to pass	A neutral element erases incompleteness.	Use the complete required-set summary rule.
Constraint failure suppresses GateFit	Independent repair information disappears and results depend on evaluation order.	Preserve each applicable result; let A.21 combine them.
A.20 becomes a package architecture	Publication, paths, refresh, and gate fields are copied into a local result.	Keep only the result and cite the consumer’s pattern.
Entity reference becomes bridge	Retargeting and semantic correspondence are confused.	Use A.6.4; add F.9 only for a separate cross-semantic claim.