Categories: Governance and Responsible AI
How to use this module: every scored answer should open by naming its category, defining it in one sentence, then enumerating what it involves β because the enumeration is what the note-taker writes down, and each named item is a potential rubric match. Category first, components second, your story third. These lessons are the category cards.
AI Governance
Definition: the organizational layer that keeps AI systems accountable β who owns each system, what policies apply, how risk is assessed, and how compliance is demonstrated.
What's involved:
- An AI inventory β knowing every place AI is used, no shadow systems
- Ownership and accountability β a named owner per system, answerable for it
- Risk assessment per use case β keyed to whether it affects the public
- Policy compliance β state GenAI guidance (EO N-12-23 / CDT), NIST AI RMF framing
- Model transparency β every output explainable to an auditor
- Review cadence and audit trail β decisions and changes are recorded and revisitable
- The kill switch β capability can be disabled by decision, instantly
The opener: "This is fundamentally an AI-governance question β governance is the accountability layer: inventory, ownership, risk assessment, policy compliance, transparency, and audit. Let me take those in order for this caseβ¦"
Cite it when: the question mentions policy, oversight, "how do we control," compliance, "should we allow," or anything about the organization's relationship to AI rather than one system's internals.
Responsible AI
Definition: the design practice of building individual AI systems that are safe, fair, and trustworthy β governance's principles turned into engineering decisions. (Distinguish the pair: governance is the org layer; responsible AI is what you build into each system.)
What's involved:
- Advisory vs. determinative β the system informs; humans (or auditable rules) decide
- Human-in-the-loop β review paths for low-confidence and high-stakes outputs
- Grounding and citations β answers traceable to authoritative sources
- Output wording as architecture β "appears to meet," never "you are qualified"
- Fairness β comparable people treated comparably; watch training-data bias
- Measured accuracy before and after launch β no eval, no deploy
- Fail-closed behavior β uncertainty routes to people, never to guessing
- Microsoft's six principles by name when Azure-flavored: fairness, reliability & safety, privacy & security, inclusiveness, transparency, accountability
The opener: "I treat this as a responsible-AI design problem β advisory output, human review, grounded and cited answers, measured accuracy, fail-closed defaults. Here's how each appliesβ¦"
Cite it when: the question asks how to keep AI safe, accurate, fair, or appropriate for the public β anything where the concern is the behavior of one system toward people.
The pairing move
These two categories chain naturally, and chaining them is a senior move: "There's a governance layer β this system goes in our AI inventory with a named owner and a risk assessment β and a responsible-AI layer in the design itself: advisory output, human review, citations, measured accuracy." Two categories, ten scorable terms, fifteen seconds.