C.26.2:4.3 - Rival explanation rule
Before using this pattern, name the principal ordinary rivals:
| Rival | Repair |
|---|---|
| Policy, command, coercion, or management pressure | Use work-claim or authority-claim patterns unless export or probe loss remains live. |
| Shared incentive or common external stimulus | Keep the claim as parallel response if that explains the coordination. |
| Routine, habit, script, or playbook | State the routine; avoid current-state wording that requires additional evidence. |
| Dashboard-following, metric gaming, or social desirability | Use C.26.1 when probe-caused change makes a passive reading of the output false, and use evidence patterns for the resulting evidence claim. |
| Copied artifact, template, policy sentence, or API response | State what was copied and any export loss. Use F.9 for a Bridge between exact local senses, E.24.PUB for publication occurrence, form, or carrier, and E.17 when a multi-view publication form or face is current, before retaining EDSE. |
| Diffusion, contagion, media amplification, or signaling | Use the appropriate propagation or evidence pattern and keep only the remaining work-enacted state claim. |