Truace
Subscribe
60/100

Moderate evidence

GainPublished recordLaborGood Space

Full story
More
Export record JSONEmailLinkedInX

How Does Intelligent Manufacturing Improve Labour Income Share: A Quasi-Natural Experiment in China

Truvace record
TRV-2026-2555raw data (JSON)
Version
v1Published
First published
Evidence type
Observational study
Sources
1 sourcePeer-reviewed
sha256
1e9690e1605a…check it

As the core driver of Industry 4.0, intelligent manufacturing (IM) spearheads a paradigm shift in production by leveraging artificial intelligence (AI) and other advanced technologies. Using panel data of Chinese A-share listed manufacturing firms from 2010 to 2023 and applying a multi-period difference-in-differences model with the IM Pilot Policy (IMPP) as a quasi-natural experiment, this study empirically identifies a causal relationship between the IM and corporate labor income share. The findings show that…

The gain

A difference-in-differences study of Chinese A-share listed manufacturers from 2010 to 2023 found the intelligent manufacturing pilot policy significantly increased corporate labor income share, mainly through its intelligence rather than automation features.

What this doesn’t fix

The evidence covers only Chinese A-share listed manufacturing firms, and the benefit varied by market power, industry type and regional minimum wage.

Sources

1 on file
  1. Sage Opendoi:10.1177/21582440261491494
    Peer-reviewed2026-07-01

Cite this record

v1

Truvace Impact Record TRV-2026-2555, v1: “How Does Intelligent Manufacturing Improve Labour Income Share: A Quasi-Natural Experiment in China.” Truvace, 2026-11-12. /record/TRV-2026-2555 (accessed on the day you copy it). sha256 1e9690e1605a22d2…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv11e9690e1605a…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2555 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.