Master of Public Affairs · Brown University · Fall 2026
Course plan authors: Han Zhang and Codex (OpenAI)
Thursdays, 9:00–11:30 am · 280 Brook Street, Room 110 · 12 class meetings
Office hours: Thursdays, 2:00–4:00 pm · Watson 242
| W1 | W2 | W3 | W4 | W5 | W6 | W7 | W8 | W9 | W10 | W11 | W12 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Learning the AI agent | Using AI for evidence | Government AI | Project design | AI governance | Project review and presentation | |||||||
| AI agent what students learn to do |
What an AI agent is | Git and version control | Configuring the agent | AI for data collection | AI for data coding | AI for visualization and publishing | Algorithmic bias | Auditing a federal AI system | Designing your final project | AI governance debates | Code review and replication | Final presentations |
| Policy analysis Bardach & Patashnik eightfold path |
Introduction to the eightfold path | Your project: problem definition and the eight steps | Problem definition and initial alternatives | Evidence and the policy question | Measures and evaluation criteria | Findings, alternatives, and communication | Errors, criteria, and trade-offs | Government AI: criteria and alternatives | Alternatives, criteria, and possible outcomes | Replication and revision | The eightfold path, revisited | |
| Introducing the framework | Discussing actual project work | Government AI policy | Comparing alternatives | AI governance | Reviewing and communicating findings | |||||||
The policy row shows discussion focuses. Return to any of the eight steps as your project develops.
Learn agentic AI tools through actual tasks. Follow a demonstration and practice the same method using the example data or suitable data from your own project. Weeks 1–3 use life expectancy data from Our World in Data. Weeks 4–5 use Federal Register rules and their abstracts for collection and text coding.
Discuss what agentic AI can and cannot do for policy analysis, using the eightfold path of Bardach and Patashnik. Week 1 introduces the eight steps in class. From Week 2, each group applies the steps to its own project, starting with a basic problem definition. Each week, groups bring an actual result or an unresolved question, and report where AI helped and where it did not. The discussion draws on your experience of using the agentic AI tools on your project, recorded in the weekly memos, and on a reading in the weeks that have one. Groups return to earlier steps as the question and the evidence develop.
Study the policy of AI. Weeks 7, 8, and 10 treat AI systems as the object of policy. Readings and cases cover algorithmic bias, AI systems in government, and the alternatives for governing AI.
These are the recurring questions for every project. Groups may work on several steps at once and revisit them through the semester. Alternatives are the policy options a decision-maker could choose.
| Activity | Minutes |
|---|---|
| Learning agentic AI tools | 45 |
| Hands-on exercises with the tools | 45 |
| Discussion of readings, projects, and cases | 45 |
This is a guide, not a rule. Early weeks spend more time learning the tools. Later weeks spend more time in discussion.
Group project: 50%. Groups of two or three develop a policy product for a named audience, supported by a GitHub repository. Three checkpoints are worth 5% each, the presentation 10%, and the final product and GitHub repository 25%.
The policy product. It takes one of two forms.
| Form | What you submit |
|---|---|
| Decision memo | PDF, three to five pages, plus a technical appendix |
| Web page or app | A public web page, a dashboard, or a small application. Any form the audience can open in a browser. |
Whichever form, the product follows the eight steps of policy analysis. Each step appears in the product, in the order below, however briefly:
Add one short section on the agent: which steps you gave to it, one concrete example of its contribution or its limit, what you checked, and what you did next.
The GitHub repository. It contains the guidance another analyst needs to replicate the numbers and results in your product, and the code itself if you built a web page or an app.
Weekly memos: 30%. Write 1–2 observations about your project or a classroom case: which policy-analysis step you attempted, how AI helped or fell short, and what you would do next. Aim for 150–200 words total. Describe what you actually tried and observed in your own words. Do not use AI to write the memo. Begin in class and submit to Canvas Discussions on the dates below. Grading rewards specific examples and thoughtful interpretation.
Classwork and participation: 20%. Complete the hands-on exercises, policy discussions, peer review, and replication in class. Grading considers your contribution and ability to explain the work.
Calendar: no class Oct 8 or Nov 26. Final product and GitHub repository due Dec 17.
| Week | Topics and agentic AI tools | Hands-on | Project and policy discussion | Assignments |
|---|---|---|---|---|
| Week 1Sept 10 | What an AI agent is
|
|
AI and the eightfold path
|
|
Learning goalSet up Codex or Claude Code and run a first policy-data task on your own computer. Analyze life expectancy data, make a chart, and check the results. Form an initial judgment about AI's usefulness across the eightfold path. | ||||
| Week 2Sept 17 | Git and version control
|
|
Your project: problem definition and the eight steps
|
Weekly memo · Sept 24 before class. |
Learning goalUse Git to manage an analysis, define an initial problem for your own project, and reflect on a first attempt to apply the eight steps with AI. | ||||
| Week 3Sept 24 | Configuring the agent
|
|
Problem definition and initial alternatives
|
Checkpoint 1: question and data · 5% Group GitHub repository and README: policy question, audience, proposed data source, and intended product. Due Oct 1 before class.Weekly memo · Oct 1 before class. |
Learning goalWrite instructions grounded in a task you have already tried, and leave with a provisional question and a feasible route to project data. | ||||
| Week 4Oct 1 | AI for data collection
|
|
Evidence and the policy question
|
Checkpoint 2: data collection · 5% Project collection script, source records, and a README that lets another person rerun the workflow. Due Oct 15 before class.Weekly memo · Oct 15 before class. |
Learning goalCollect a documented dataset and explain how its coverage supports or changes the project question. | ||||
| Oct 8: no class. The Week 4 checkpoint and short memo are due Oct 15. | ||||
| Week 5Oct 15 | AI for data coding and model choice
|
|
Measures and evaluation criteria
|
Weekly memo · Oct 22 before class. |
Learning goalConstruct a measure, evaluate it on held-out human codes, and explain whether it is useful for the intended policy analysis. | ||||
| Week 6Oct 22 | AI for visualization and publishing
|
|
Findings, alternatives, and communication
|
Checkpoint 3: preliminary results · 5% A script-produced figure, the finding it supports, and a first version of the group’s policy product. Due Oct 29 before class.Weekly memo · Oct 29 before class. |
Learning goalProduce a checked finding for a specific reader and explain its relevance to the policy choices being considered. | ||||
| Week 7Oct 29 | Algorithmic bias
|
|
Errors, criteria, and trade-offs
|
Weekly memo · Nov 5 before class. |
Learning goalUse actual checks and contrasting criteria to assess what the analysis supports and what should change. | ||||
| Week 8Nov 5 | Auditing a federal AI system
|
|
Government AI: criteria and alternatives
|
Weekly memo · Nov 19 before class. |
Learning goalAssess a documented government AI case and explain which judgments the available evidence permits. | ||||
| Week 9Nov 12 | Designing your final project
|
|
Project progress across the eight steps
|
|
Learning goalMake a feasible revision to an existing project or identify the work needed next. | ||||
| Week 10Nov 19 | AI governance
|
|
Alternatives, trade-offs, and decisions
|
Weekly memo · Dec 3 before class. |
Learning goalCompare policy alternatives and defend a recommendation while explaining how AI contributed to the analysis. | ||||
| Nov 26: Thanksgiving recess. Next class Dec 3. | ||||
| Week 11Dec 3 | Code review and replication
|
|
Replication and revision
|
Weekly memo · Dec 10 before class. |
Learning goalUse a classmate’s rerun to improve both the project and its explanation. | ||||
| Week 12Dec 10 | Final presentations
|
|
The eightfold path, revisited
|
Group presentation · 10%Dec 10, in class.Final product and GitHub repository · 25% Policy product, scripts, source information, and instructions for reproducing the results. Due Dec 17. |
Learning goalCommunicate a defensible policy analysis and assess AI’s role using the work completed during the semester. | ||||