TRV-2026-1592Certified recordPeer-reviewed

Corporate ethical and responsible AI (CERAi) and AI trustworthiness: a lifecycle perspective and empirical insights

Purpose This study develops and empirically validates a Corporate Ethical and Responsible AI (CERAi) lifecycle framework. The framework comprises three interdependent stages: design and development, testing and training, and deployment and usage. The study aims to move the research beyond abstract principles and policy analyses toward empirically grounded, lifecycle-integrated artificial intelligence AI governance theory. It positions ethical AI and responsible AI governance as the two constitutive components of…

Policy · Good Space — documented gain · certified 2026-10-16 · v1 · article view · machine-readable

Current reading — gain

In a survey of AI professionals, corporate ethical AI governance at the design and development stage and at the deployment and usage stage was associated with higher perceived AI trustworthiness.

What this doesn’t fix

The findings reflect perceived trustworthiness among a limited sample of conference-attending AI professionals, and the authors caution that they do not definitively validate uniform accumulation of governance effects across stages.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1592, v1: “Corporate ethical and responsible AI (CERAi) and AI trustworthiness: a lifecycle perspective and empirical insights.” Truvace, 2026-10-16. /record/TRV-2026-1592 (accessed at citation time). sha256 a94545a68965d0f8…

Calibration history

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

  1. Certifiedv1a94545a68965…

    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-1592 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.