Cross-context flow may violate expectations even when technically lawful
Aliases: context collapse · contextual transfer · cross-domain data use
What it is
A cross-context information flow takes information generated within one social activity and role relationship into another—for example, using wellness activity in employment judgment or classroom interaction for commercial profiling. A valid contract, broad authorization, or secure transfer may still change recipient role, end, and transmission condition in ways that violate the originating norm. The issue is not simply leaving an app; meaning and consequence migrate with context.
Why it happens
A field appears portable while its interpretation depends on the institution and task that produced it. Steps are feedback in self-care but a risk proxy in insurance; classroom participation supports experimentation in learning but becomes durable judgment in a performance file. Cross-context systems retain values while discarding role constraints, quality limitations, and correction opportunities, allowing a receiving context to assign new meaning under different ends.
Studying it
Paired vignettes can hold data content constant while changing sender or recipient role, purpose, and condition, then compare acceptability, expectation, and perceived harm. Data-journey interviews ask participants to follow a flow from generation to a new decision and locate the normative break. Researchers must measure understanding of the actual flow; a judgment made under the false belief that no transfer occurred describes a faulty mental model.
Where it stops holding
Cross-context transfer is not inherently wrong. Public health, research, or a person's deliberate delegation can support a new flow after evaluating social end, proportionality, role power, and safeguards. Context boundaries can be nested or ambiguous: a school may combine educational, employment, and care relationships. Legal validity and contextual appropriateness are distinct judgments, and neither automatically substitutes for the other.
Applying it
- Carry originating role, task, quality limitations, and permitted transmission conditions with data rather than sending a context-free field.
- Review parameter changes whenever a new recipient or decision appears, especially power, contestability, and error consequence.
- Explain migration as “from whom, to whom, for which decision,” not merely partnership or service improvement.
- Test paired prototypes with identical data and different receiving contexts; substantial surprise or failed prediction calls for narrower flow, stronger separation, or renewed contextual choice.
Related
- Same group: O1.08.1 Appropriate information flow depends on its social context · O1.08.3 The framework explains why compliance can still provoke objection
- Adjacent: O1.03 Purpose limitation · O2.13 Disclosure of third-party sharing
- Search terms:
cross-context information flow·context collapse·role-based norms