ai-ml-governance
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when
Install
npx skills add https://github.com/cbrock84/headcount/tree/main/plugins/data-analytics/skills/ai-ml-governance
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install cbrock84-headcount@llmmart
git clone https://github.com/cbrock84/headcount.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole cbrock84/headcount collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
AI and ML governance
Regimes governing automated decision-making differ by jurisdiction and sector and are changing quickly. Anything affecting credit, employment, housing, insurance, healthcare, or education carries specific legal obligations — involve Legal & Risk and qualified counsel rather than treating it as an engineering question.
Define intended use before evaluating anything
Write down what the system is for, what it is not for, who is affected by its output, and what happens when it is wrong. Most AI failures are use outside intended scope by someone who did not know the scope existed.
Then decide the consequence tier, because it sets everything after it:
- Advisory — a human decides, the model suggests. Lightest oversight.
- Assistive — the model acts, a human reviews before effect.
- Autonomous — the model acts with effect. Highest bar, and rarely appropriate where a person is materially affected.
Evaluation
A held-out evaluation set that reflects real inputs, including the awkward ones. Built before deployment and kept stable, or you cannot compare versions.
- Measure the failure that matters. Aggregate accuracy hides the errors you care about. A model that is 95% accurate and wrong disproportionately on one group is not 95% good.
- Evaluate by segment, always. This is where fairness problems and quiet degradation appear.
- Both error directions. False positives and false negatives usually have different costs, and the threshold should reflect that ratio rather than a default.
- Establish a baseline. Compare against the current process — often a simple rule — not against zero. Plenty of models fail to beat the heuristic they replaced.
Monitoring
Models degrade silently: the world moves, inputs drift, and accuracy falls without any error being raised.
Monitor input distribution against training, output distribution over time, performance against whatever ground truth arrives later, and the rate of human override. A rising override rate is the best early warning you have, and it is usually already visible in a queue nobody reads.
Human oversight
Meaningful, not nominal. A reviewer approving hundreds of decisions an hour is not overseeing anything — they are laundering the model's output through a person.
Meaningful oversight requires the reviewer to see why the model decided, to have time to disagree, and to have their disagreement change the outcome and be recorded.
Documentation
Per model: intended use and exclusions, training data and its provenance, evaluation results by segment, known limitations, monitoring in place, and the owner. This is what you need when someone asks why a decision was made — and increasingly what a regulator expects to see.
Retirement
Have a way to turn it off. Know what happens to the process when you do, and confirm the fallback still works — a manual path that has not been exercised in two years is not a fallback.
Sources
references/sources.md in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.
Never
- Deploy without an evaluation set and a monitoring plan.
- Use a model outside its documented intended use because it seems to work.
- Train or fine-tune on customer data without confirming the lawful basis covers it. The basis for collecting it rarely extends to this.
- Let a model make a consequential decision about a person with no route to human review.
Files (headcount)
-
references
-
sources.md 3.8 KB
# Sources — `data-analytics:ai-ml-governance` <!-- Generated by scripts/build-sources.py from sources/*.toml. Do not edit. --> Check these before answering on anything they cover, and cite what you used. The use note on each one is binding: most of what a professional cites is free to read and not free to reproduce. ## 29 CFR Part 1607 — Uniform Guidelines on Employee Selection Procedures US Equal Employment Opportunity Commission · US · public domain (US government) — quote freely <https://www.ecfr.gov/current/title-29/subtitle-B/chapter-XIV/part-1607> **Authoritative for:** What counts as a selection procedure, when adverse impact exists, and what validation evidence an employer must hold to defend one that has it. This is the document that settles disputes about hiring tests, scored assessments and promotion criteria — including automated ones. ## Artificial Intelligence and the ADA US Equal Employment Opportunity Commission · US · public domain (US government) — quote freely <https://www.eeoc.gov/eeoc-disability-related-resources/artificial-intelligence-and-ada> **Authoritative for:** When an algorithmic assessment screens out a person with a disability, and what accommodation is owed inside an automated hiring flow. ## ISO/IEC 42001 — AI management systems ISO · global · **sold — cite the identifier only, never the text** <https://www.iso.org/standard/42001.html> **Authoritative for:** What a certifiable AI management system requires — the only thing an external auditor can certify against, and increasingly what enterprise customers ask for by name. Sold, so name the clause and never reproduce it. ## NIST AI 600-1: Generative AI Profile NIST · US · public domain (US government) — quote freely <https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-generative-artificial-intelligence> Machine-readable: <https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.600-1.pdf> **Authoritative for:** Which risks are unique to or amplified by generative models, as distinct from general machine learning risk. Settles the claim that generative systems are just another model. ## NIST AI RMF Playbook NIST · US · public domain (US government) — quote freely <https://airc.nist.gov/airmf-resources/playbook/> **Authoritative for:** For each framework subcategory, which actions and documentation artifacts satisfy it. The operational layer the framework itself deliberately leaves abstract. ## NIST AI Risk Management Framework, AI 100-1 NIST · US · public domain (US government) — quote freely <https://www.nist.gov/itl/ai-risk-management-framework> Machine-readable: <https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf> **Authoritative for:** What the four AI risk functions are and what an organization must be able to evidence under each. It ends the argument about what claiming to have an AI governance program has to mean concretely. ## OECD Recommendation of the Council on Artificial Intelligence OECD · global · free to use with attribution — credit the publisher <https://legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0449> **Authoritative for:** The intergovernmentally agreed definition of an AI system, which other regimes adopt by reference. That definitional question is the one it actually settles. ## Regulation (EU) 2024/1689 — the AI Act Publications Office of the European Union · EU · free to use with attribution — credit the publisher <https://eur-lex.europa.eu/eli/reg/2024/1689/oj> **Authoritative for:** Whether an AI system is prohibited, high-risk or limited-risk in the EU and what obligations attach. Binding law rather than guidance, and only the Official Journal version is authentic. --- Sources are maintained in `sources/` upstream, not here. If one is wrong, out of date, or missing, fix it there — this file is regenerated and an edit to it is lost.
-
-
SKILL.md 4.1 KB
--- name: ai-ml-governance description: Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision. --- # AI and ML governance > Regimes governing automated decision-making differ by jurisdiction and sector and are changing > quickly. Anything affecting credit, employment, housing, insurance, healthcare, or education > carries specific legal obligations — involve Legal & Risk and qualified counsel rather than > treating it as an engineering question. ## Define intended use before evaluating anything Write down what the system is for, what it is **not** for, who is affected by its output, and what happens when it is wrong. Most AI failures are use outside intended scope by someone who did not know the scope existed. Then decide the consequence tier, because it sets everything after it: - **Advisory** — a human decides, the model suggests. Lightest oversight. - **Assistive** — the model acts, a human reviews before effect. - **Autonomous** — the model acts with effect. Highest bar, and rarely appropriate where a person is materially affected. ## Evaluation A held-out evaluation set that reflects real inputs, including the awkward ones. Built before deployment and kept stable, or you cannot compare versions. - **Measure the failure that matters.** Aggregate accuracy hides the errors you care about. A model that is 95% accurate and wrong disproportionately on one group is not 95% good. - **Evaluate by segment**, always. This is where fairness problems and quiet degradation appear. - **Both error directions.** False positives and false negatives usually have different costs, and the threshold should reflect that ratio rather than a default. - **Establish a baseline.** Compare against the current process — often a simple rule — not against zero. Plenty of models fail to beat the heuristic they replaced. ## Monitoring Models degrade silently: the world moves, inputs drift, and accuracy falls without any error being raised. Monitor input distribution against training, output distribution over time, performance against whatever ground truth arrives later, and the rate of human override. **A rising override rate is the best early warning you have**, and it is usually already visible in a queue nobody reads. ## Human oversight Meaningful, not nominal. A reviewer approving hundreds of decisions an hour is not overseeing anything — they are laundering the model's output through a person. Meaningful oversight requires the reviewer to see why the model decided, to have time to disagree, and to have their disagreement change the outcome and be recorded. ## Documentation Per model: intended use and exclusions, training data and its provenance, evaluation results by segment, known limitations, monitoring in place, and the owner. This is what you need when someone asks why a decision was made — and increasingly what a regulator expects to see. ## Retirement Have a way to turn it off. Know what happens to the process when you do, and confirm the fallback still works — a manual path that has not been exercised in two years is not a fallback. ## Sources `references/sources.md` in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding. ## Never - Deploy without an evaluation set and a monitoring plan. - Use a model outside its documented intended use because it seems to work. - Train or fine-tune on customer data without confirming the lawful basis covers it. The basis for collecting it rarely extends to this. - Let a model make a consequential decision about a person with no route to human review.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.