ComplianceGPT Lab · Summer 2026

Schedule

Weekly overview and daily structure for the 6-week program

Weekly Overview

WeekDatesThemeKey Event
Week 1 Jun 22–26 Introduction to AI Research Orientation · First pipeline run
Week 2 Jun 29 – Jul 3 AI Fundamentals ML → DL → NLP → LLMs · Cluster access · First GPU experiments
Week 3 Jul 7–10 Prompt Engineering Project proposal presentations
Week 4 Jul 14–17 Retrieval-Augmented Generation Project work begins · Mid-point check-in
Week 5 Jul 21–24 ComplianceGPT Deep Dive Final experiments · Poster draft due
Week 6 Jul 28–31 Research Communication July 31: REU Closing Ceremony

Weekly Structure

Wednesday is the main on-campus session each week. Thursday and Friday are remote work days. Monday is an informal check-in — the mentor is available to unblock students, but there is no scheduled lecture.

Monday
Roadblock office hours
Ad hoc — mentor available to unblock. No formal agenda. Message on Slack to schedule.
Wednesday ★ On campus
Main session — NCS 242
Lecture + live coding + task assignment. 10am–noon. Independent work follows.
Thursday — Remote
Independent work
Async progress update on Slack by noon. Mentor responds within 2 hours.
Friday — Remote
Deliverable due + wrap-up
Submit weekly deliverable by 5pm. Brief Slack update on what you finished and what's next.

Wednesday On-Campus Structure

Every Wednesday session (NCS 242, 10am) follows this structure:

10:00 – 10:20
Mini Lecture — Mentor introduces the week's topic. Concept explanation, key terms, motivation. No hands-on yet — just listen and ask questions.
10:20 – 10:50
Live Coding / Demo — Mentor demonstrates the concept in code. Students follow along on their own machines. The goal is seeing it work before you try it yourself.
10:50 – 11:15
Discussion and Task Assignment — Group discussion of the concept. Mentor assigns the week's specific tasks. Tasks are written down, not just verbal.
11:15 – 4:00
Independent Research — Students work on assigned tasks. Mentor available in NCS 242 or via Slack. 2pm Slack check-in required.

Remote Days (Thursday and Friday)

By noon
Slack progress update — Post in #daily-updates: what you're working on today and any blockers. Keep it to 2–3 sentences.
All day
Independent Work — Assigned tasks, reading, experiments, writing. Async Slack questions answered within 2 hours on weekdays.
Friday 5pm
Weekly deliverable due — Submit via GitHub commit or Google Doc share link posted to Slack.

The Rule of Specific Tasks

At the end of every meeting you will receive a specific task, not a general direction. "Keep working on your project" is not a task. Examples of real tasks:

  • "Run batch_runner.py on 10 rows, find the first wrong prediction, write one sentence about why."
  • "Write 3 adversarial scenarios for the law enforcement HIPAA exception."
  • "Read the Keshav 3-pass paper method and apply it to the Brown et al. GPT-3 paper."
  • "Complete exercises 1–4 in notebooks/prompt_engineering.ipynb."

Weekly Deliverables at a Glance

WeekDeliverableDue
1First pipeline run + 1-page reflectionFriday Jun 27
2Python exercises + error analysis + project selectionFriday Jul 3
3Project proposal (5 min oral Wed) + 1-page project summary (written Fri)Wed Jul 9 · Fri Jul 11
4Mid-point pitch (5 min) + experiment log with incremental resultsWed Jul 16 · Fri Jul 18
5Poster draft + 2-page write-up draft + final results CSVFriday Jul 25
6Poster inspection Mon Jul 28 · Final poster + write-up Thu Jul 30Mon Jul 28 · Thu Jul 30