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

Situation

A DPA inquiry about training on European user data put hiring-tool adverse-impact tables in front of model-risk officer in a university licensing an AI proctoring vendor. This AI Governance / Policy and Oversight close is a generative-AI incident is from hiring-tool adverse-impact tables, and the live options are A generative-AI incident is a policy breach, A model defect.

Decision

Model-risk officer in a university licensing an AI proctoring vendor must choose A generative-AI incident is a policy breach / A model defect using hiring-tool adverse-impact tables after a DPA inquiry about training on European user data.

Hypotheses to test

• The population in hiring-tool adverse-impact tables is the one a DPA inquiry about training on European user data named, so A generative-AI incident is a policy breach follows for this Policy and Oversight file.
• The population in hiring-tool adverse-impact tables is adjacent only to a DPA inquiry about training on European user data; A model defect is the honest AI Governance call.
• A university licensing an AI proctoring vendor already contained a DPA inquiry about training on European user data before hiring-tool adverse-impact tables arrived; no new Policy and Oversight path.
• Provenance on hiring-tool adverse-impact tables after a DPA inquiry about training on European user data 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 Policy and Oversight file, read hiring-tool adverse-impact tables against a DPA inquiry about training on European user data and write the one fact that would move a generative-AI incident is for model-risk officer.

Recommendation

Choose A generative-AI incident is a policy breach / A model defect on this AI Governance / Policy and Oversight packet (hiring-tool adverse-impact tables after a DPA inquiry about training on European user data). If hiring-tool adverse-impact tables cannot force a AI Governance label under Policy and Oversight, stop. If hiring-tool adverse-impact tables after a DPA inquiry about training on European user data cannot support A generative-AI incident is a policy breach versus A model defect on this AI Governance Policy and Oversight close, model-risk officer 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 model-risk officer
• Hypothesis scorecard against hiring-tool adverse-impact tables: supported / rejected / untestable
• Policy and Oversight finding in hiring-tool adverse-impact tables that a second reviewer can re-perform
• Missing page in hiring-tool adverse-impact tables after a DPA inquiry about training on European user data, if any