| “The report has EvidenceRole for Claim A.” | Treats a source label as a system-role kind or assignment without recovering the actual relation. | Use an evidence-use relation with EvidenceEpistemeSlot, EvidenceTargetClaimSlot, scope, polarity, window, and provenance constraints when current. |
| “Dataset X proves safety.” | Treats dataset presence as proof, assurance, and safety claim. | Use A.10 for evidence, B.3 for assurance or safety assurance, and name unsupported attempted use. |
| “The standard has normative role.” | Role word hides standard-use, requirement-use, source-use, or publication-use. | Recover the relation governed by the current claim and apply E.10.D2, E.17, F.10, or the direct requirement pattern. |
| “The badge is current, so release is allowed.” | Status display becomes gate passage or permission. | Use status-use relation plus gate or release subject pattern; dashboard display alone is not a decision. |
| “Simulation output is counterfactual evidence.” | Simulator output is promoted to realized or interventional causal evidence. | Use C.28; keep simulationResultRef, model assumptions, validation, and bounded supported/unsupported use distinct from empirical, identification, estimate, and direct-sampling results. |
| “The work run is the evidence role.” | Work occurrence, actual performer, assignment check, local result, result episteme, and later evidence-use are collapsed. | Use A.13 for the actual performer and A.15.1 for independent admission of the dated Work. Add F.6 only if the use must also identify the assignment under which the Work was performed. Use A.6.1 for actual bindings, the domain pattern for the local result, C.2.1 for its episteme, A.10/G.6 for provenance, and A.2.4 only for first-use classification. |