<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Piercosma Bisconti Lucidi</string-name>
          <email>piercosma.bisconti@consorzio-cini.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
          <xref ref-type="aff" rid="aff5">5</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Lidia Marassi</string-name>
          <email>lidia.marassi@unina.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
          <xref ref-type="aff" rid="aff5">5</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Stefano Marrone</string-name>
          <email>stefano.marrone@unina.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
          <xref ref-type="aff" rid="aff5">5</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Domenico D. Bloisi</string-name>
          <email>domenico.bloisi@unint.eu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
          <xref ref-type="aff" rid="aff5">5</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Daniele Nardi</string-name>
          <email>nardi@diag.uniroma1.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
          <xref ref-type="aff" rid="aff5">5</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Carlo Sansone</string-name>
          <email>carlo.sansone@unina.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
          <xref ref-type="aff" rid="aff5">5</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>200</institution>
          ,
          <addr-line>Rome, 00147</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Department Of Electrical Engineering And Information Technologies, University of Naples Federico II</institution>
          ,
          <addr-line>Via Claudio 21</addr-line>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Department of Computer, Control and Management Engineering ”Antonio Ruberti”, Sapienza University of Rome</institution>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Department of International Humanities and Social Sciences, International University of Rome</institution>
          ,
          <addr-line>Via Cristoforo Colombo</addr-line>
        </aff>
        <aff id="aff4">
          <label>4</label>
          <institution>Naples</institution>
          ,
          <addr-line>80125</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff5">
          <label>5</label>
          <institution>Piazzale Aldo Moro 5</institution>
          ,
          <addr-line>Rome, 00185</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2025</year>
      </pub-date>
      <abstract>
        <p>As Artificial Intelligence (AI) systems are increasingly deployed in critical sectors, ensuring their responsible and reliable operation has become a priority. This paper examines the importance of technical conformity verification as a mechanism for embedding principles of fairness, transparency, and safety within the AI development lifecycle. It distinguishes between commercial and research-grade systems, highlighting how their respective maturity levels influence the depth of conformity assessments. The study emphasizes the strategic placement of verification eforts after model evaluation and before deployment to mitigate risks related to bias, opacity, and lack of accountability. Drawing on international standards such as ISO/IEC TR 24027, the authors propose a structured approach to conformity verification that includes checklists and bias assessment protocols. The goal is to foster AI systems that are not only high-performing but also trustworthy, inclusive, and aligned with ethical norms. Future work will involve validating these practices through empirical case studies and fostering collaboration between academia, industry, and regulatory bodies.</p>
      </abstract>
      <kwd-group>
        <kwd>mity assessment</kwd>
        <kwd>AI standards</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>CEUR
ISSN1613-0073</p>
    </sec>
    <sec id="sec-2">
      <title>1. Introduction</title>
      <p>
        Artificial Intelligence (AI) systems are being rapidly integrated into decision-making pipelines
across diverse sectors, including healthcare, finance, transportation, and public administration.
These technologies promise to enhance eficiency, reduce human error, and enable data-driven
policy and operational decisions. However, despite their technical advancements, AI systems
often carry risks related to bias, opacity, and limited accountability [
        <xref ref-type="bibr" rid="ref1 ref2">1, 2</xref>
        ]. These risks are
frequently embedded in the development process itself, which typically follows four key stages:
data collection and preparation, model development, evaluation, and deployment. Each phase of
this lifecycle introduces potential failure points. Biased training data can lead to discriminatory
models [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], algorithmic design choices may amplify unintended patterns [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], and even
comprehensive evaluations can fall short if they lack demographic disaggregation or ignore contextual
variables [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Once deployed, these systems may be dificult to audit or correct, particularly in
high-stakes or regulated environments.
      </p>
      <p>
        In light of these challenges, there is growing consensus around the need for AI systems to
conform to established technical standards that codify principles of fairness, transparency, and
reliability [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. These standards serve as a foundation for the responsible development of AI,
providing normative guidance on risk assessment, bias mitigation, and system accountability.
Among these, ISO/IEC TR 240271 ofers specific recommendations for identifying and addressing
bias across all phases of the AI lifecycle, from dataset construction to model deployment.
      </p>
      <p>Yet the mere existence of such standards is not suficient to ensure ethical or robust outcomes.
To translate principles into practice, they must be operationalized through concrete conformity
assessment protocols—structured procedures that systematically evaluate whether an AI system
meets the requirements defined by the standards. These protocols should be tailored to diferent
stages of technological maturity and integrated directly into the AI development workflow,
allowing developers to anticipate and correct potential failures before systems reach production
environments. As demonstrated by real-world incidents, such as the temporary suspension of
ChatGPT in Italy due to regulatory concerns over data processing and transparency, neglecting
these safeguards can have immediate legal and reputational consequences.</p>
      <p>In this context, embedding conformity verification into the AI lifecycle is not merely a
regulatory formality but a critical component of building AI systems that are not only performant
but also fair, transparent, and trustworthy by design.</p>
    </sec>
    <sec id="sec-3">
      <title>2. Technical Conformity Verification</title>
      <p>Ensuring that AI systems meet established technical standards is essential for promoting safety,
reliability, and public trust. This is particularly relevant for systems deployed in sensitive or
high-impact environments. Technical conformity verification involves assessing whether an AI
system adheres to normative requirements regarding its design, development, and behavior.
This section outlines key considerations for integrating conformity assessment within the AI
lifecycle, distinguishing between types of systems, and identifying the appropriate timing for
such assessments.</p>
      <sec id="sec-3-1">
        <title>2.1. Commercial vs. Research-Grade AI Systems</title>
        <p>AI systems difer significantly in their readiness for deployment. For this reason, it is important
to distinguish between commercial products and research-grade systems, as the requirements for
conformity verification vary accordingly.</p>
        <p>A widely adopted framework for measuring technological maturity is the Technology
Readiness Level (TRL) scale. Originally developed by NASA, TRL levels range from early conceptual
stages (TRL 1–3) to fully operational systems (TRL 7–9). Research prototypes typically fall
within TRL 1–6, while commercial products are generally situated at TRL 7 and above2.
• TRL 1–3: Basic principles and proof-of-concept exploration, often limited to academic
research.
• TRL 4–6: Prototype development and validation in relevant settings, representing the
so-called “valley of death” in innovation.</p>
        <p>• TRL 7–9: Final stages of testing, system qualification, and commercial deployment.</p>
        <p>While full conformity verification is mandatory for commercial AI solutions, research-oriented
systems may undergo a lighter form of evaluation, primarily focusing on methodological validity
and reproducibility. Nonetheless, even research systems can benefit from partial conformity
assessment, especially when addressing fairness, safety, or replicability in applied contexts.</p>
      </sec>
      <sec id="sec-3-2">
        <title>2.2. Positioning Conformity Verification Within the AI Lifecycle</title>
        <p>Conformity verification should be strategically integrated within the AI development process.
The optimal point for intervention is after the model evaluation phase and before deployment.
This allows for a comprehensive assessment of risks and limitations before the system is made
available to end-users or integrated into operational environments.</p>
        <p>Figure 1 illustrates the typical AI development pipeline and highlights where conformity
assessment is most efectively applied.
2See NASA TRL definitions: https://www.nasa.gov/directorates/heo/scan/engineering/technology/txt_accordion1.
html</p>
        <p>Conducting verification before deployment is critical for minimizing legal, ethical, and
reputational risks. Without it, issues such as inadequate bias control or insuficient data
governance may only surface post-deployment, making remediation costly or infeasible. A
notable example of premature deployment is the temporary suspension of ChatGPT in Italy
due to concerns over user verification and data processing transparency 3—demonstrating the
high stakes involved in releasing unverified AI systems.</p>
      </sec>
      <sec id="sec-3-3">
        <title>2.3. Why Verification Matters</title>
        <p>A structured conformity process supports compliance with technical and ethical expectations,
especially in applications involving sensitive user data or life-impacting decisions. In addition
to addressing model performance and safety, conformity verification ensures:
• User protection: Verifying mechanisms for access control and risk mitigation.
• Data privacy: Assessing transparency in data usage and storage.
• Bias detection: Identifying and addressing sources of algorithmic unfairness, in line
with standards such as ISO/IEC TR 240274.</p>
        <p>In this context, standards play a foundational role. Yet their efectiveness depends on
implementation through structured, repeatable processes. The next sections propose a framework
to operationalize this verification through detailed checklists and bias assessments based on
international technical guidelines.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>3. Conclusion</title>
      <p>As AI systems become increasingly embedded in real-world applications, ensuring their
alignment with technical standards is not merely a regulatory formality—it is a necessary safeguard
for ethical, reliable, and accountable deployment. The complexity and autonomy of these
systems demand proactive mechanisms for risk identification, bias control, and performance
validation, particularly in high-stakes domains where the consequences of technical failures
may afect human rights, public safety, or institutional trust.</p>
      <p>In this paper we outlined the rationale for integrating conformity verification into the AI
development lifecycle, emphasizing the importance of distinguishing between research-grade
prototypes and commercial-grade systems. Such diferentiation enables the application of
proportionate verification protocols tailored to the system’s level of technological maturity
and intended deployment context. Importantly, we have highlighted the optimal placement of
conformity checks—between model evaluation and deployment—where they can most efectively
prevent costly or irreparable failures in production settings.</p>
      <p>Beyond assessing performance, conformity assessment frameworks grounded in international
standards such as ISO/IEC TR 24027 provide essential tools for the systematic identification
3See oficial press release from the Italian Data Protection Authority: https://www.garanteprivacy.it/home/docweb/
-/docweb-display/docweb/9870847
4ISO/IEC TR 24027:2021, “Information technology — Artificial intelligence — Bias in AI systems and AI aided decision
making,” available at: https://www.iso.org/standard/77607.html
and mitigation of algorithmic bias, data governance weaknesses, and opaque engineering
choices. By incorporating structured verification steps—such as bias audits, documentation
reviews, and checklists—developers can embed fairness, transparency, and safety directly into
the development process, rather than treating these as post-hoc concerns.</p>
      <p>The need for such frameworks is particularly pressing in critical applications involving
sensitive data or life-altering decisions. In these contexts, the absence of reliable conformity
verification not only exposes users to harm but also undermines public confidence in AI systems
more broadly.</p>
      <p>Looking ahead, future work should aim to refine and validate these verification protocols
through empirical case studies and cross-sectoral collaboration. Engagement between
standards bodies, regulatory institutions, industry practitioners, and academic researchers will be
crucial to ensure that verification practices remain up-to-date, context-sensitive, and practically
implementable. Only through such integrated, interdisciplinary eforts can we build AI systems
that are not only powerful, but also just, inclusive, and trustworthy by design.</p>
    </sec>
    <sec id="sec-5">
      <title>Declaration on Generative AI</title>
      <p>During the preparation of this work, the authors used GPT and DeepL to perform grammar
and spelling check. After using these tools and services, the authors reviewed and edited the
content as needed and take full responsibility for the publication’s content.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>N.</given-names>
            <surname>Mehrabi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Morstatter</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Saxena</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Lerman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Galstyan</surname>
          </string-name>
          ,
          <article-title>A survey on bias and fairness in machine learning</article-title>
          ,
          <source>ACM Computing Surveys</source>
          (
          <year>2021</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>H.</given-names>
            <surname>Suresh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. V.</given-names>
            <surname>Guttag</surname>
          </string-name>
          ,
          <article-title>A framework for understanding unintended consequences of machine learning</article-title>
          ,
          <source>Communications of the ACM</source>
          <volume>64</volume>
          (
          <year>2021</year>
          )
          <fpage>62</fpage>
          -
          <lpage>71</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>S.</given-names>
            <surname>Barocas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. D.</given-names>
            <surname>Selbst</surname>
          </string-name>
          ,
          <article-title>Big data's disparate impact</article-title>
          ,
          <source>California Law Review</source>
          <volume>104</volume>
          (
          <year>2016</year>
          )
          <fpage>671</fpage>
          -
          <lpage>732</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>B.</given-names>
            <surname>Mittelstadt</surname>
          </string-name>
          ,
          <article-title>Principles alone cannot guarantee ethical ai</article-title>
          ,
          <source>Nature Machine Intelligence</source>
          <volume>1</volume>
          (
          <year>2019</year>
          )
          <fpage>501</fpage>
          -
          <lpage>507</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>A.</given-names>
            <surname>Jobin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Ienca</surname>
          </string-name>
          ,
          <string-name>
            <surname>E. Vayena,</surname>
          </string-name>
          <article-title>The global landscape of ai ethics guidelines</article-title>
          ,
          <source>Nature Machine Intelligence</source>
          <volume>1</volume>
          (
          <year>2019</year>
          )
          <fpage>389</fpage>
          -
          <lpage>399</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>K. N.</given-names>
            <surname>Vokinger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Feuerriegel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. S.</given-names>
            <surname>Kesselheim</surname>
          </string-name>
          ,
          <article-title>Mitigating bias in machine learning for medicine</article-title>
          ,
          <source>Communications medicine 1</source>
          (
          <year>2021</year>
          )
          <fpage>25</fpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>