Assess whether a generative-AI incident is a policy breach or a model defect

Situation

Bias and Training Data work in a city using a hiring-screen algorithm now turns on a generative-AI incident is because an internal audit finding that human review logs are empty put hiring-tool adverse-impact tables in play. Board AI liaison should say what hiring-tool adverse-impact tables proves.

Decision

Board AI liaison in a city using a hiring-screen algorithm must choose A generative-AI incident is a policy breach / A model defect using hiring-tool adverse-impact tables after an internal audit finding that human review logs are empty.

Hypotheses to test

• The population in hiring-tool adverse-impact tables is the one an internal audit finding that human review logs are empty named, so A generative-AI incident is a policy breach follows for this Bias and Training Data file.
• The population in hiring-tool adverse-impact tables is adjacent only to an internal audit finding that human review logs are empty; A model defect is the honest AI Governance call.
• A city using a hiring-screen algorithm already contained an internal audit finding that human review logs are empty before hiring-tool adverse-impact tables arrived; no new Bias and Training Data path.
• Provenance on hiring-tool adverse-impact tables after an internal audit finding that human review logs are empty is broken; do not pick A generative-AI incident is a policy breach or A model defect yet.

Analysis required

• Reproduce the incident row in hiring-tool adverse-impact tables and say whether it ever touched production data.
• Split policy-or-governance failure from a model defect using prompts, outputs, and human edits in hiring-tool adverse-impact tables.
• Reproduce the incident row in hiring-tool adverse-impact tables and say whether it ever touched production data.
• For this AI Governance Bias and Training Data file, read hiring-tool adverse-impact tables against an internal audit finding that human review logs are empty and write the one fact that would move a generative-AI incident is for board AI liaison.

Recommendation

Choose A generative-AI incident is a policy breach / A model defect on this AI Governance / Bias and Training Data packet (hiring-tool adverse-impact tables after an internal audit finding that human review logs are empty). If hiring-tool adverse-impact tables cannot force a AI Governance label under Bias and Training Data, stop. If hiring-tool adverse-impact tables after an internal audit finding that human review logs are empty cannot support A generative-AI incident is a policy breach versus A model defect on this AI Governance Bias and Training Data close, board AI liaison must leave the classification unresolved and name the missing control or provenance fact.

Command returns

• Bottom-line AI Governance option on a generative-AI incident is, then the evidence in hiring-tool adverse-impact tables, then the action for board AI liaison
• Hypothesis scorecard against hiring-tool adverse-impact tables: supported / rejected / untestable
• Bias and Training Data finding in hiring-tool adverse-impact tables that a second reviewer can re-perform
• Missing page in hiring-tool adverse-impact tables after an internal audit finding that human review logs are empty, if any