Certified into the record
The exact text we saved
This is the version exactly as it was saved, character for character. The SHA-256 hash below is a 64-character code worked out from that text. Run the same text through SHA-256 and you get the same code; change a single letter and the code comes out completely different. Each version also stores the previous version’s hash, which chains them together so no version can be swapped out quietly.
TRUVACE RECORD VERSION record: TRV-2026-2576 version: 1 kind: certified reason: Certified into the record timestamp: 2026-11-12T07:56:17.526659Z status: published lens: p_space sector: labor headline: How Employee–AI Collaboration Influences Coworkers’ Helping Behaviour: An Attribution Theory Perspective dek: As artificial intelligence (AI) is increasingly integrated into the workplace, employee-AI collaboration is evolving from a personal productivity tool to a social cue that coworkers can observe and interpret. Existing research has largely emphasised the performance and well-being effects of employee-AI collaboration; however, few studies have revealed, from the observer's perspective, its potential negative spillover mechanisms on coworkers' helping behaviour. Based on attribution theory, this study constructs a… gain_title: (none) problem_title: In a two-wave survey of 375 coworker evaluations in Chinese firms, the more coworkers saw a colleague as collaborating with AI, the less help they gave that colleague (r = -0.530), partly because they read it as laziness or avoiding responsibility. trace_subject: (none) gain_reading: (none) gain_evidence: (none) problem_reading: In a two-wave survey of 375 coworker evaluations in Chinese firms, the more coworkers saw a colleague as collaborating with AI, the less help they gave that colleague (r = -0.530), partly because they read it as laziness or avoiding responsibility. problem_evidence: laziness attribution and responsibility-avoidance attribution play a mediating role quick_read: A peer-reviewed study in Behavioral Sciences examined how coworkers react when they see a colleague working with AI. In a two-wave survey of 375 matched coworker evaluations, the more a colleague was seen as collaborating with AI, the less help the respondent reported giving that colleague. The raw correlation was r = -0.530, and the regression coefficient was -0.406. Coworkers who saw heavy AI collaboration were more likely to suspect laziness (β = 0.551) or an attempt to dodge responsibility when results were poor (β = 0.583). Both suspicions were linked to less helping. The authors report responsibility avoidance as the stronger pathway. The link was stronger when the human and the AI depended closely on each other's work, because coworkers could not tell where the employee's effort ended and the AI's contribution began. In the survey, the laziness pathway was not significant when interdependence was low, but it was when interdependence was high. A second experiment with 320 full-time employees was designed to test the causal effect. limitation: Study 1 is correlational and rests on coworkers' perceptions of a colleague's AI use rather than usage logs or actual collaboration frequency, and its participants were from firms in Chinese regions such as Hubei and Jiangsu. tag: Evidence-backed problem key_points: Study 1 used a two-wave survey: 450 questionnaires were sent out and 375 valid matched coworker evaluations were kept, an effective response rate of about 83.3%. | Respondents came from firms in regions such as Hubei and Jiangsu in finance, IT services and education that had widely adopted AI, and each rated the same target coworker at both time points. | Perceived AI collaboration correlated with less helping (r = -0.530) and with laziness attribution (r = 0.624) and responsibility-avoidance attribution (r = 0.599). | In the regression, AI collaboration predicted laziness attribution (β = 0.551) and responsibility-avoidance attribution (β = 0.583); laziness (β = -0.169) and responsibility avoidance (β = -0.189) each predicted less helping. | At high task interdependence (+1 SD), the indirect effect via laziness was -0.065 with a 95% confidence interval of [-0.130, -0.015]; at low interdependence it was -0.054 with an interval of [-0.109, 0.003], which includes zero. | The indirect effect via responsibility avoidance excluded zero at both low (-0.076) and high (-0.101) interdependence. | Study 2 was an online 2 × 2 scenario experiment with 320 full-time employees, who read about a hypothetical coworker named Zhang San using AI frequently or rarely. rundown: The research team, writing in Behavioral Sciences in 2026, drew on attribution theory, which holds that observers infer motives from visible cues. Coworkers can see an employee use AI and see the output, but not the prompt design, information filtering, output checking and judgement correction behind it. The authors argue this gap can lead observers to read AI use as shortcut-taking. Study 1 recruited respondents who used AI at work and could name a coworker whose AI use they could observe. At the first wave they rated the coworker's perceived AI collaboration and task interdependence. At the second wave they rated laziness and responsibility-avoidance attributions and how much help they gave. Measures were adapted from existing five-point scales, and reliability coefficients ranged from 0.885 to 0.943. The authors tested common method bias with several checks and concluded it was not serious. The model fit the data well (CFI = 0.992, RMSEA = 0.030). Laziness attribution only partly explained the helping drop, since AI collaboration still predicted less helping with it in the model (β = -0.203). Study 2 randomly assigned participants to four conditions that varied AI collaboration and human-AI task interdependence, then asked them to judge the coworker and report their own willingness to help. The authors designed it to add causal evidence to the survey findings. sources: - peer_reviewed | Behavioral Sciences | https://doi.org/10.3390/bs16060985 | 2026-06-12 prev: 0000000000000000000000000000000000000000000000000000000000000000
- SHA-256 hash
- 610527a96138f582d33c792e59af00f1feceac767a5f49fbd354557a998526bb
- Previous version’s hash
- 0000000000000000000000000000000000000000000000000000000000000000
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2576 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.
ace