Course description
Trustworthiness is a claim that must survive contact with a real system.
DSC 261 is an evidence-first technical course on evaluating, attacking, defending, inspecting, monitoring, and controlling deployed machine-learning systems. Centered on primary research from leading venues and hands-on experiments with modern language models and agents, it teaches a broader discipline: define the system boundary, state a falsifiable trust claim, choose valid evidence, and produce an executable artifact—such as a metric, attack, defense, monitor, or control protocol—that supports an accountable decision.
Course format: instructor-led technical lectures, structured paper responses, hands-on problem sets, and a quarter-long project. There are no student paper presentations. Students present their own project and evidence at the end of the quarter.
Published course materials
Module 1: Course opening and compact foundations
Module 1 spans the first two meetings. It begins with concrete failures that motivate trustworthy machine learning, then develops only the model foundations needed to reason about modern language models and deployed LLM systems.
Published course materials
Module 3: Grounding
Lecture materials
Grounding reading list
Core Grounding lecture papers, in lecture order.
Optional extension
Published course materials
Data Valuation
Which data should we keep, clean, acquire, or prioritize for a chosen task? This lecture connects data valuation to data-centric trustworthy AI: model influence, LLM data selection, distributional similarity, KAIROS, and learning across possible repairs of uncertain data.
Lecture materials
Download Data Valuation slides PDF50 slides · Updated October 29, 2026 · Public PDF
Topics covered
- Using data values for selection, cleaning, acquisition, and reweighting.
- Influence functions and valuation across the LLM development pipeline.
- Wasserstein distance, MMD, Gaussian kernels, and the intuition behind bandwidth.
- KAIROS: reference-based, model-agnostic valuation and distributional influence.
- Learning from uncertain data: possible worlds, possible models, and data repairs.
Core reading list
Background and further reading
Optional readings for the valuation methods, distribution comparisons, and LLM applications introduced in the lecture.
Published course materials
Module 4: Alignment and Post-training
Does alignment make a model trustworthy, or better at pleasing its evaluator? The lectures connect reward overoptimization, sycophancy, preference-model biases, and the integrity of oversight.
Core reading list
Three papers taught in depth, in lecture order.
Opening context and case reports
Original source screenshots link to the complete reports. Incident accounts and instructional context are distinct from the three core research papers.
Optional extension
Ordered curriculum
Course topics: evaluating concrete safety claims
Nine modules and a Data Valuation lecture connect evaluation and grounding to data-centric methods, post-training, adversarial robustness, agent security, oversight, privacy, and control. Internal-model techniques are introduced where they help evaluate a concrete safety claim.
M1 · Foundations
- Why responsible data science is a technical discipline
- Reconstructing a deployed LLM system
M2 · Uncertainty
- Evaluation validity
- Hallucination, uncertainty and abstention
Download Module 2 PDF — Uncertainty
M3 · Grounding
- Grounding, citations and claim verification
Download Module 3 PDF — Grounding
Data Valuation
- Selection, cleaning, and LLM data valuation
- Distributional similarity, KAIROS, and learning from uncertain data
Lecture PDF and readings
M4 · Alignment & Post-training
- SFT, RLHF, DPO and RL with verifiable rewards
- Reward hacking, overoptimization, sycophancy and evaluation gaming
M5 · Adversarial Robustness
- Adaptive attacks, jailbreaks and valid attack–defense evaluation
- Data poisoning, backdoors and supply-chain attacks
M6 · Agent Security & Reliability
- Prompt injection and secure agent design
- Agentic evaluation, capability elicitation and sandbox boundaries
- Delegation, coordination and multi-agent failure
M7 · Oversight & Monitoring
- Weak supervision and scalable oversight
- Reasoning faithfulness, activation probes and system logs
Combined session: selected mechanisms and evidence for concrete safety claims.
M8 · Privacy
- Training-data extraction and memorization
- Honest privacy auditing, attribution and measured deletion
Attribution and measured deletion are supporting material for the privacy session.
M9 · Misalignment & Control
- Hidden objectives, alignment faking and emergent misalignment
- AI control protocols, adversarial evaluations and safety cases
Coverage and pacing: the topic units above describe the curriculum in teaching order. Units may span or share meetings; see the populated calendar below. Oversight and Monitoring share a combined session. Privacy attribution and measured deletion are supporting material.
Course calendar
Fall 2026 meetings
Grounding is scheduled for October 20 and 22, followed by two Alignment and Post-training meetings. Later topics are planned as below; combined coverage and supporting material are identified explicitly.
Earlier topic labels summarize module coverage; session-level boundaries are approximate. September 24 and 29 retain the original published lecture labels. The October 6 lecture was canceled, and its makeup date is not yet confirmed. Planned pacing may be adjusted as the course progresses.
| Meeting | Date | Topic |
| 01 | Thu · Sep 24 | M1 · Foundations Course opening and foundations |
| 02 | Tue · Sep 29 | M1 · Foundations Reconstructing a deployed LLM system |
| 03 | Thu · Oct 1 | M2 · Evaluation & Uncertainty Evaluation and uncertainty |
| 04 | Tue · Oct 6 | Lecture canceled No lecture; makeup date not yet confirmed |
| 05 | Thu · Oct 8 | M2 · Uncertainty Uncertainty and abstention, continued |
| 06 | Tue · Oct 13 | M2 · Uncertainty Uncertainty and abstention, continued |
| 07 | Thu · Oct 15 | M2 · Uncertainty Uncertainty and abstention, continued |
| 08 | Tue · Oct 20 | M3 · Grounding Retrieval, citations and claim support Download Module 3 PDF — Grounding |
| 09 | Thu · Oct 22 | M3 · Grounding Verification, calibrated decisions and abstention Download Module 3 PDF — Grounding |
| 10 | Tue · Oct 27 | M4 · Alignment & Post-training SFT, RLHF, DPO and RL with verifiable rewards |
| 11 | Thu · Oct 29 | M4 · Alignment & Post-training Reward hacking, overoptimization, sycophancy and evaluation gaming |
| 12 | Tue · Nov 3 | M5 · Adversarial Robustness Adaptive attacks, jailbreaks and valid attack–defense evaluation |
| 13 | Thu · Nov 5 | M5 · Adversarial Robustness Data poisoning, backdoors and supply-chain attacks |
| 14 | Tue · Nov 10 | M6 · Agent Security & Reliability Prompt injection and secure agent design |
| 15 | Thu · Nov 12 | M6 · Agent Security & Reliability Agentic evaluation, capability elicitation and sandbox boundaries |
| 16 | Tue · Nov 17 | M6 · Agent Security & Reliability Delegation, coordination and multi-agent failure |
| 17 | Thu · Nov 19 | M7 · Oversight & Monitoring Weak supervision and scalable oversight; reasoning faithfulness, activation probes and system logs Combined session: selected mechanisms and evidence for concrete safety claims. |
| 18 | Tue · Nov 24 | M8 · Privacy Training-data extraction, memorization and honest privacy auditing Attribution and measured deletion are supporting material. |
| — | Thu · Nov 26 | Thanksgiving holiday — no class |
| 19 | Tue · Dec 1 | M9 · Misalignment & Control Hidden objectives, alignment faking and emergent misalignment |
| 20 | Thu · Dec 3 | M9 · Misalignment & Control AI control protocols, adversarial evaluations and safety cases |
Quarter-long work
The project is the spine of the course.
Small teams will make and test one technically precise trust claim about a real LLM system. A successful project produces evidence—not a survey—and ends with a reproducible artifact, a concise report, and an in-person project presentation.
Measure or audit
Design a valid evaluation, uncertainty study, privacy audit, fairness audit, attribution test, or monitor.
Attack or defend
Implement an adaptive red-team evaluation, poisoning experiment, prompt-injection defense, or robust-refusal protocol.
Inspect or control
Test an interpretability claim, intervention, agent sandbox, escalation rule, or adversarial control protocol.
Weeks 1–2
Question and system boundary
Form teams, identify the system and stakeholders, state the claim, define the operating context, and name the failure event.
Week 3
Project proposal
Submit a concise proposal with primary sources, threat model, variables, feasibility check, and collaboration plan.
Weeks 4–5
Evaluation contract and pilot
Freeze the scenarios, metrics, baselines, thresholds, and analysis plan; run a small pilot before scaling.
Week 7
Mid-quarter evidence review
Show an executable artifact and preliminary evidence; document negative results, validity threats, and necessary redesign.
Weeks 9–10
Final study and reproducibility package
Complete the study, preserve configurations and raw outputs, and prepare a defensible conclusion with explicit boundaries.
Finals week
Project presentations
Each team presents its question, method, strongest evidence, failure boundary, and deployment implication. The exact presentation schedule will be posted on Canvas.
No student paper presentations. Paper teaching remains instructor-led. Student presentation time is reserved for original project work and the evidence each team produced.
Assessment
Grading emphasizes execution and evidence.
Canvas is authoritative for exact deadlines, rubrics, and any instructor-announced adjustments.
| Component | Weight | What's expected |
| Project proposal | 10% | Draft of motivation, related work, datasets and evaluation, and collaboration plan (maximum 2 pages excluding references) |
| Project mid-point evaluation | 20% | Preliminary analysis and results (maximum 3 pages excluding references) |
| Final project artifact and report | 35% | Reproducible implementation, Final analysis and results (maximum 4 pages excluding references) |
| Project presentation | 35% | Clear explanation of motivation and methodology, positive or negative results, and response to questions. |
People
Instructional team
BS
PP
Parjanya Prashant
Teaching assistant · Project collaborator
JZ
Jiongli Zhu
Teaching assistant · Project collaborator
Working norms
Technical ambition with responsible boundaries
Responsible security research
Red-team, extraction, prompt-injection, and agent experiments must remain within approved systems, accounts, data, and rate limits. Do not target people or services outside the assignment scope.
Reproducibility
Preserve model and dataset versions, prompts, code, seeds, configurations, raw outputs, exclusion rules, and analysis decisions. A result without provenance is not a finished result.
Collaboration and attribution
Teams may divide work, but every member must understand the full claim and evidence. Cite papers, code, datasets, tools, and external assistance precisely.
Use of generative AI
AI tools may support course work when their use follows the assignment and Canvas policy. Students remain responsible for verification, disclosure, source accuracy, and every submitted claim.
Accessibility and accommodations: students should contact the UC San Diego Office for Students with Disabilities and notify the instructor through the established course process. The Canvas syllabus contains the controlling policy language.