A policy that lives in the repo

Most university AI policies live in syllabi PDFs or honor code portals — documents students read once, if at all. Stanford's CS336 has tried something different: it put its AI agent guidelines directly in the assignment's GitHub repository, in a file called CLAUDE.md.

CLAUDE.md is a convention — not a standard, to be precise — associated with Anthropic's Claude coding tools, which look for such files to read project-specific instructions before taking action. By placing one in the CS336 assignment repo, the course instructors are attempting to make their AI policy machine-readable, not just human-readable.

The practical implication: if a student uses a Claude-based coding assistant on the assignment, the agent is supposed to read those guidelines and operate within them. That's a meaningful architectural choice, even if its enforcement has real limits (more on that below).

What CS336 actually is

Context matters here. CS336 is Stanford's course on the foundations of language models — students implement components like tokenizers, attention mechanisms, and training loops from scratch. It is, by design, a course about understanding how these systems work at a low level.

That makes the AI assistance question genuinely complicated. Using an LLM to write the code that implements an LLM is not obviously cheating, but it does undercut the pedagogical point. The CLAUDE.md approach suggests the instructors are trying to draw a line that's more nuanced than a simple prohibition.

The limits of CLAUDE.md enforcement

It's worth being direct about what this approach cannot do. CLAUDE.md is a convention, not a technical control. An AI tool that doesn't implement the convention — or a student who uses a tool that ignores it — won't be bound by the file at all. There's no cryptographic enforcement, no audit log, no way for the course to verify compliance.

What the file does accomplish is clearer than what it enforces: it communicates intent, sets expectations for students using compatible tools, and creates a documented record of what the course considers appropriate AI behavior. That's not nothing, but it's also not a technical solution to a policy problem.

Why this is worth watching

The broader significance here isn't specific to CS336. Universities are struggling to write AI policies that are specific enough to be useful and flexible enough to survive the pace of tool development. Most have landed on vague language that satisfies administrators and confuses students.

Embedding policy in the development environment — where students actually work — is a different approach. It's closer to how software teams handle security policy (linters, pre-commit hooks, CI checks) than how universities have traditionally handled academic integrity.

Whether it works depends on adoption: of compatible tools, of the convention itself, and of a culture where students treat the CLAUDE.md file as a real constraint rather than a suggestion. None of that is guaranteed. But as an experiment in operationalizing AI policy at the assignment level, it's one of the more concrete examples to emerge from a major research university so far.