aceModerate evidence
Published recordLaborProblem Space
More
How Human–AI Interaction Reshapes Construction Workers’ Safety Behaviors: Insights from Agent-Based Modeling
- Truvace record
- TRV-2026-2488raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- b3e674bdb302…check it
Abstract The complex nature of human–artificial intelligence (AI) interaction (HAI) introduces new challenges for worker safety. While ensuring human well-being in HAI has become a shared objective, the lack of quantifiable approaches limits our ability to capture its nuanced effects on workers. To address this gap, the present study develops an agent-based modeling framework grounded in stimulus-organism-response (SOR) theory. The model simulates workers’ interactions with AI systems and peers within a bounded…
The problem
In an agent-based simulation validated at a smart construction site, workers' safety behavior steadily declined as their interaction with AI systems deepened, with extra-role safety behavior falling most.
What this doesn’t fix
The findings come mainly from an agent-based simulation in a bounded two-dimensional space, with empirical validation at one smart construction site.
Sources
1 on file- Journal of Construction Engineering and Managementdoi:10.1061/jcemd4.coeng-18562
Cite this record
v1Truvace Impact Record TRV-2026-2488, v1: “How Human–AI Interaction Reshapes Construction Workers’ Safety Behaviors: Insights from Agent-Based Modeling.” Truvace, 2026-11-12. /record/TRV-2026-2488 (accessed on the day you copy it). sha256 b3e674bdb30221ca…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2488 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.