E.17.ID.CR:8 - Common Anti-Patterns and How to Avoid Them
Positive boundary-use profile. Read the anti-pattern table below only after the ordinary working card has recovered the bounded comparative review unit. The ordinary result is positive: compared source epistemes or source publications, shared review frame, bounded comparative lift, blocked downstream claim or effect, and boundary trigger. If one row below fires, keep the comparison unit only for bounded review use and name the neighboring governing pattern for the crossed claim; do not turn the table into a general negative catalogue of every action the unit cannot perform.
| Anti-pattern | Why it is wrong | How to avoid it |
|---|---|---|
| Comparison-unit instability | The text sounds as if it governs a note in one section, a publication unit in another, a comparative move in a third, and a whole review process in a fourth. | Stabilise one bounded comparative review unit early and keep note, sheet, UI, and rendering labels explicit as ordinary forms of that object rather than stylistic substitutes. |
| Bridge gloss inflation | A helpful comparative sentence or stance word starts acting like a Bridge or use licence. | Require bridgeOccurrenceRef and boundedUseClaimRef; keep any Card optional, and use bridgeStanceRef only for a separate F.9.1 episteme about that exact claim. |
| Soft prompt smuggling | The review unit is really creating an abductive prompt or action-selection case, but hides it in gentle prose. | If prompt selection or action-selection claim governs the next action, publish U.AbductivePrompt with explicit promptSpecies, openQuestion, and cue or action-selection provenance instead of keeping it here. |
| Viewing capture | Same-entity restatement or representation-shift work is pulled into interpretation just because the result is more readable. | Name the base source relation or representation work first and use bounded comparison only when bounded comparative lift is primary. |
| Explanation-face laundering | Interpretation language is used to avoid explicit E.17.EFP class and bounded-use review. | If face class or bounded connective prose is primary, stay with E.17.EFP. |
| Gentle-tone advisory overread | A calm explanatory tone makes work or reliance, assurance, or gate guidance sound harmless. | Publish boundedComparativeUse, overreadRisk, worldContactPolicy, and downstreamAuthorityLimit explicitly. |
| EntityOfConcern shift | A changed target is mislabeled as interpretation because the prose still sounds comparative. | Apply OntologicalReframing or A.6.4 once continuity witnesses or changed target govern the claim. |
| Interface neutrality fiction | A guided or contrastive aid pretends to be audience-neutral while steering blocked downstream use. | Make targetUserModel, interactionMode, and contrastiveQuestion explicit and keep the non-bounded use forbidden. |