Link to current text
SIE.9:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Repair |
| Expose the integrated table | Start from the receiving action and design only the claims and branches it needs. |
| One null or HTTP error for every absence | Distinguish semantic absence/unresolved states from access, timeout, and implementation failure. |
| Provenance in internal logs only | Expose the action-changing provenance/currentness summary and stable trace reference. |
| Hide source IDs behind one key | Preserve source schemes and identity-disposition references. |
| Endpoint is available, therefore usable | Validate meanings, branches, currentness, service conditions, and representative Work through SIE.10. |
| Semantic result authorizes action | Name the application, engineering, quality, safety, legal, or other decision owner. |