Explainability answers this prediction / this answer. Transparency answers what is this system, trained on what, for whom, with which known limits? Model cards, data cards, and user disclosure are the artifacts reviewers, customers, and sometimes regulators expect—alongside Vol. 19 eval numbers and Vol. 20 bias/fairness choices.
Transparency is not dumping weights or PII. It is proportionate disclosure: enough for the audience to use, contest, or refuse the system. It feeds governance, compliance, and responsible AI. Privacy constraints (next-but-one) limit what you may publish.
Learning Objectives
By the end of this lesson, students should be able to:
- Define transparency as audience-specific disclosure, distinct from explainability.
- List core fields of a model card and a data card.
- Choose what to disclose to users vs internal reviewers vs the public.
- Write a minimal YAML/JSON card plus a user-facing notice from a policy template.
- Avoid both “transparency theater” (vague slogans) and unsafe oversharing (secrets, PII, exploit detail).
- Link cards to bias/fairness criteria, eval harness versions, and known failure modes.
Transparency is documented, audience-appropriate disclosure about an AI system’s purpose, data, model, evaluation, limitations, and human oversight. A model card describes the model (intended use, metrics, slices, caveats). A data card describes datasets (provenance, collection, consent, known gaps). A system card covers the deployed product (tools, RAG corpus, guardrails, escalation). User disclosure is the short notice people see (“you are interacting with AI,” how to appeal). Transparency does not require publishing proprietary weights or training corpora wholesale.
Audiences and Artifacts
| Audience | Needs | Typical artifact |
|---|---|---|
| End user / customer | That AI is in use; limits; how to get a human | In-product notice, FAQ, ToS snippet |
| Internal reviewer / RAI | Eval protocol, slices, fairness criterion, residual risks | Model + data + system cards, Vol. 19 harness commit |
| Procurement / partner | Intended use, out-of-scope, security/privacy posture | One-pager + card excerpts |
| Regulator / auditor (when required) | Traceability, owners, change log | Governed dossier—see compliance |
| Researchers / public (optional) | Reproducible claims without leaking data | Published card, not raw PII dumps |
Model Cards vs Data Cards vs Disclosure
Model card (core fields)
Data card (core fields)
User disclosure
- AI involvement in plain language
- What the system does not do (medical/legal advice, etc.)
- How to appeal or reach a human
- What is logged (high level)
- No fake demographic “study” claims
Good transparency
- Specific, versioned, owned
- Matches actual eval harness and production flags
- States out-of-scope uses honestly
Transparency theater
- “We value ethics” with no metrics or owners
- Stale cards after a silent model swap
- Publishing PII samples or jailbreak recipes
Minimal Card + Notice (Policy-as-Code Sketch)
Related Lectures
| Lecture | Role |
|---|---|
| Explainability | Per-decision reasons vs card-level disclosure |
| Bias / Fairness | What slice metrics and criteria belong on the card |
| Privacy | What you must not publish or over-retain |
| Copyright | License fields on the data card |
| Governance | Who approves and versions cards |
| Benchmarks (Vol. 19) | Cite harness, not screenshot vibes |
“Transparency means open-sourcing the weights.” Often the useful artifact is a card plus user notice, not a weight dump. Second: a slogan page with no version, owner, or eval commit. Third: copying another vendor’s model card numbers as if they were yours. Fourth: publishing sample rows that contain PII. Fifth: treating explainability plots as the model card. Sixth: never updating the card after a prompt or retrieval-corpus change.
Knowledge Check
- Short Answer: What is transparency in this lecture? Answer: Audience-appropriate disclosure about purpose, data, model, eval, limits, and oversight.
- True/False: Explainability and transparency are the same artifact. Answer: False—reasons for an output vs system disclosure.
- Multiple Choice: A data card primarily documents: (a) dataset provenance, consent, gaps, license, (b) SGD hyperparameters only, (c) CSS themes. Answer: (a).
- Short Answer: Name two model-card fields. Answer: Any of: intended use, out-of-scope, metrics/slices, fairness criterion, limitations, owner/version.
- True/False: User disclosure should state that AI is in use and how to reach a human when relevant. Answer: True.
- Multiple Choice: Transparency theater looks like: (a) ethics slogans with no metrics or owners, (b) versioned cards tied to a harness commit, (c) clear out-of-scope lists. Answer: (a).
- Short Answer: Why mention the eval harness commit on the card? Answer: So reported metrics are reproducible under the same Vol. 19 protocol.
- True/False: Publishing PII samples is required for a good data card. Answer: False—describe the data without dumping secrets.
- Multiple Choice: After a silent model or corpus swap you should: (a) version and update the card, (b) leave the old card, (c) delete all docs. Answer: (a).
- Short Answer: Which sibling lecture covers license lines on the data card? Answer: Copyright.
Key Takeaways
- Transparency is proportionate disclosure—model cards, data cards, system cards, user notices.
- Cards need owners, versions, intended use, eval protocol, slices/fairness, and honest limits.
- Do not confuse SHAP plots, open weights, or marketing slogans with a card.
- Never publish PII or attack recipes in the name of openness.
- Next: Privacy — what you may collect, keep, and leak.
Lab: Students fill the YAML stub for a fictional internal bot. Peer-review: can a new engineer tell intended use, out-of-scope, eval commit, and appeal path in under two minutes? Red-team the card for PII overshare.
Whiteboard: Three columns—User notice / Internal card / Public excerpt. Arrow constraints from Privacy and Copyright into what may be written.
Recap: Transparency is versioned, owned disclosure—cards and notices—not unexplained plots or weight dumps. Bind cards to Vol. 19 evals and Vol. 20 fairness choices, then continue to Privacy.