<?xml version="1.0" encoding="UTF-8"?>
<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.1" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-1.xsd">
  <titleInfo>
    <title>AI bias, liability and corporate accountability: A governance perspective</title>
  </titleInfo>
  <name type="personal">
    <namePart>Dutta, Suryanshu and Sakshi, Shah</namePart>
    <role>
      <roleTerm authority="marcrelator" type="text">creator</roleTerm>
    </role>
  </name>
  <typeOfResource>text</typeOfResource>
  <originInfo>
    <place>
      <placeTerm type="text">Chartered Secretary: The Journal for Governance Professionals</placeTerm>
    </place>
    <issuance>monographic</issuance>
  </originInfo>
  <language>
    <languageTerm authority="iso639-2b" type="code">eng</languageTerm>
  </language>
  <physicalDescription>
    <form authority="marcform">print</form>
    <extent>55(10), Oct, 2025: p.129-132</extent>
  </physicalDescription>
  <abstract>Artificial Intelligence is now embedded in corporate governance, assisting in compliance reporting, agenda setting, and risk identification. For Company Secretaries, whose statutory role under the Companies Act, 2013 is to safeguard compliance and advise the board, the challenge lies in confronting outputs that appear authoritative yet may be unreliable. This article treats algorithmic bias as a governance problem with legal consequence. It considers potential liabilities under domestic law, reviews global regulatory approaches, and outlines a framework through which Company Secretaries can preserve accountability and ethical standards in an era of technological adoption.- Reproduced 

https://www.icsi.edu/media/webmodules/CSJ/October_2025/22.pdf
</abstract>
  <relatedItem type="host">
    <name>
      <namePart>Chartered Secretary: The Journal for Governance Professionals </namePart>
    </name>
  </relatedItem>
  <recordInfo>
    <recordCreationDate encoding="marc">260224</recordCreationDate>
  </recordInfo>
</mods>
