TRV-2026-1765Certified recordPeer-reviewed

A Dual-Channel Model of Artificial Intelligence Adoption Intention Among Executives of Traditional-Industry SMEs: Perceived Value, Perceived Implementation Risk, and the Boundary Condition of Digital Foundation

**A Dual-Channel Model of Artificial Intelligence Adoption Intention among Executives of Traditional-Industry SMEs: Perceived Value, Perceived Implementation Risk, and the Boundary Condition of Digital Foundation** **Weixiang Gan** Post Doctorate Researcher, Lincoln University College, 47301 Petaling Jaya, Malaysia **Qiaoran Liu** Agriculture and Rural Affairs Bureau of Yindu District, Anyang City 455000, China **Mengfei Xiao** Post Doctorate Researcher, Lincoln University College, 47301 Petaling Jaya, Malaysia…

Education · Problem Space — documented harm · certified 2026-10-18 · v1 · article view · machine-readable

Current reading — problem

Peer demonstration and subsidies do not move these executives, because the risk of implementing AI is one they cannot absorb, even where they see value in it.

What this doesn’t fix

The design is cross-sectional, so the estimates are associational and the ordering of constructs rests on theory rather than on temporal precedence. The moderation terms also add very little explained variance.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1765, v1: “A Dual-Channel Model of Artificial Intelligence Adoption Intention Among Executives of Traditional-Industry SMEs: Perceived Value, Perceived Implementation Risk, and the Boundary Condition of Digital Foundation.” Truvace, 2026-10-18. /record/TRV-2026-1765 (accessed at citation time). sha256 3178eeeab98df1a7…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv13178eeeab98d…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1765 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.