Link to current text
SIE.10:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Repair |
| Valid schema, therefore valid integration | Test meanings, relations, identity, composition, mappings, provenance, quality, and receiving Work separately. |
| One quality/confidence score | Record layer-specific evidence and categorical dispositions; preserve hard stops. |
| Happy-path demonstration | Add negative, boundary, unlike, changed-source, stale, conflict, and failure cases. |
| Provenance completeness means truth | Test the source claim and receiving adequacy; provenance only makes derivation inspectable. |
| High alignment benchmark score | Validate local endpoint relations and use loss against representative cases. |
| All-or-nothing readiness | A known defect can finish a bounded failure. A positive subset result requires the contract’s permission and all premises on which that subset relies. |
| Semantic validation authorizes release | Return the account to the actual engineering, quality, safety, legal, or application authority. |