TRV-2026-1592Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-1592 version: 1 kind: certified reason: Certified into the record timestamp: 2026-10-16T18:12:55.566538Z status: published lens: g_space sector: policy headline: Corporate ethical and responsible AI (CERAi) and AI trustworthiness: a lifecycle perspective and empirical insights dek: 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… gain_title: 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. problem_title: (none) trace_subject: (none) gain_reading: 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. gain_evidence: Both CERAIi design and development and CERAi deployment and usage have significant positive direct effects on AI trustworthiness problem_reading: (none) problem_evidence: (none) quick_read: Researchers built a three-stage lifecycle framework for corporate ethical and responsible AI governance, covering design and development, testing and training, and deployment and usage. They surveyed attendees of a U.S. national AI conference in early 2026 and analyzed 143 usable responses with structural equation modeling. The results suggest organizations seeking trusted AI may need governance that begins at design, not only visible controls at deployment. The evidence is perception-based and drawn from a small, self-selected group of conference attendees, so it does not show that governance causes trustworthy AI behavior. limitation: 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. tag: Evidence-backed gain key_points: The framework treats ethical AI and responsible AI governance as two components of one construct and AI trustworthiness as a distinct downstream outcome. | Design and development governance and deployment and usage governance each had significant positive direct effects on trustworthiness. | Testing and training governance had no significant direct effect on trustworthiness. | A serial mediation path ran from deployment and usage through testing and training to design and development and then to trustworthiness. rundown: The survey went to 500 attendees of a national AI conference in the United States, producing 143 usable responses from AI professionals in healthcare, financial services, manufacturing, retail and energy. The authors developed and validated multi-item scales for each lifecycle stage. The framework covers both conventional machine learning models and autonomous AI agents operating in organizational settings. The authors say it aims to move beyond abstract principles and policy analyses toward empirically grounded governance theory. Testing and training alone did not mediate the link between deployment and usage and trustworthiness. The authors read this as design-stage ethics acting as the mechanism through which later-stage governance relates to perceived trustworthiness, and they state that stakeholders appear to weight visible deployment-stage governance more heavily. sources: - peer_reviewed | Journal of Enterprise Information Management | https://doi.org/10.1108/jeim-05-2026-0911 | 2026-10-16 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- a94545a68965d0f83a8b54967f1f31376cc1d5467d426741a6bf103b250757dc
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
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.
ace