F.9.1:7 - Common Anti-Patterns and How to Avoid Them

Failure	Why it fails	Repair
Card-first entry	Packaging is made a prerequisite for relation or claim truth.	Start from the obtaining Bridge and exact bounded-use claim; add a Card only when reuse pays.
Stance as Bridge kind	The gloss competes with F.9 relation semantics.	Keep the F.9 kind unchanged and make the stance a separate episteme about one use claim.
Stance as licence	Friendly wording silently authorizes substitution or action.	State claim polarity and current reliance separately; apply the pattern that defines the needed authorization.
`CL` as threshold	Evidence shorthand becomes a rule for use.	Keep `CL` in the evidence account and retain the exact use rule and tolerated loss in the bounded-use claim.
Loss note as tolerance	An observed difference is treated as accepted loss.	Keep observed loss in evidence and permitted loss in the bounded-use claim.
Several stance tags	Labels replace one intelligible sentence and hide incompatible readings.	Use one primary stance plus plain loss and boundary wording.
Stance as coarsening cure	`projection` or `nonEquivalent` replaces source return and blocked-use duties.	Apply A.6.3.CSC and keep the stance only as optional interpretation help.
Bundle-wide stance identity	Equal labels on several claims are treated as one reusable semantic relation.	Treat each stance episteme as local to its exact bounded-use claim.