C.22.2:18 - Misuse Modes and Repairs

Misuse mode	Symptom	Repair
Card-as-executable-work request	A solution-shaped task or implementation request is treated as a problem-side record.	Recover the signal, joint EntityOfConcern, effective ReferenceScheme, ClaimScope, claim family, reason this is not a preselected Work request, improvement check or acceptance probe, and honest next use before applying a Work pattern.
Content creep	The card starts carrying claims outside the problem-side record.	Keep only the cue or reference needed by the problem-side record and apply the pattern that defines or constrains the claim being made.
Hidden scalarization	Goldilocks, readiness, priority, OEE, QD, or indicator wording becomes one local score.	Preserve source-set kind, selection or retention criterion, characteristic or Q-bundle relation, and non-scalar next use.
Silent retargeting	A changed EntityOfConcern, representation scheme, diagram, functional description, or transformation-flow path interpretation inherits old readiness by wording continuity.	Name the representation-transition, retargeting, bridge, structural-reinterpretation, or wording-use relation before reuse.
Refresh dead end	Expiry or unknown handling is recorded as a passive note.	State refresh, retirement, bounded use, `abstainOrNoChange`, or the relation that is reopened.