Review Context Collision

A failure in which a system applies assumptions from a simulated or fictional context to a real external entity that appears to match it.

A name, role, identifier, or pattern in a simulation resembles something real. The system then carries fictional assumptions into an external action or judgment.

Matching labels do not establish matching identity. Systems that cross simulation and real-world boundaries need explicit identity checks and action limits.

A training scenario uses a fictional company name that later matches a real supplier, and an automated report attaches simulated risk claims to the real company.

Context collision is not ordinary context drift. It is a categorical collision between simulated or fictional meaning and a real entity that appears to match.

Same label, wrong reality.

* [[scenario|Scenario]] * [[context-to-reality-drift|Context-to-Reality Drift]] * [[verification|Verification]] * [[sanitized-information|Sanitized Information]]

* [NASA Software Engineering Handbook, “Requirements Validation”](https://swehb.nasa.gov/spaces/7150/pages/16449673/SWE-055+-+Requirements+Validation) — requires validation that software will perform as intended in the customer environment, including nominal and off-nominal conditions. This supports the identity and environment checks behind this Renaissance Solutions term; NASA does not use the label “Context Collision.”

* Compare with [[scenario|Scenario]] and [[context-to-reality-drift|Context-to-Reality Drift]].