1am/one-ai-policy

No single AI policy can fit a whole university

· from a student consultation on AI at ANU · Mayukh Das

ANU is setting up an AI Oversight Committee, and one seat on it belongs to a student. In October the student representatives for my college ran an open consultation to work out what that student should bring to the table. I am one of those representatives, so I spent two hours listening to students talk about AI in their courses. I went in to collect opinions. I came out with one of my own.

Poster for an open student consultation: have a say in how AI is governed at ANU
The poster for the session.

AI is here, and it is not magic

The session made two things clear to me at once. The first is that AI is here to stay. The second is that it is not a machine that solves everything. These models are not deterministic: ask the same question twice and you can get two different answers. Reaching for a language model to solve every problem makes no sense.

Pretending it isn't there makes even less. The useful question is how we use it to augment what people can already do.

What students were worried about

The concerns were specific:

Others sat at the opposite end and argued for allowing AI for everything.

One size does not fit all

What struck me was that each side was right about some course and wrong about another. A course built on personal reflection about foreign policy, or a course in art, might reasonably ban AI entirely, because the thinking or the making is the whole point. Systems engineering or deep learning is different. There, research and implementation can be fast-tracked with AI while the decisions stay human.

Different courses, and different colleges, will need to handle this differently, depending on what they are trying to teach. Try writing one rule for all of them:

one rule, five courses

My own illustration of the argument, built from the examples in this note. It is not ANU policy.

What I believe now

Any single AI policy for a whole university would be fundamentally flawed. Different courses teach different skills. Those skills lead to different jobs, and those jobs already have different AI practices. The only person placed to judge all of that is an expert in the field, which means the course convener.

The principle I would hand them is simple. Foundational skills are taught without AI, and AI is used to speed up the rest. A coding course might allow AI for writing documentation but not for writing the code, because writing code is the skill being taught.

Teach the foundations without AI. Use AI to speed up everything built on top of them.

The part that falls to the teachers

This puts real weight on conveners, and not only the ones in computer science. As AI arrives in every discipline, academics from outside computing need to understand these tools intimately too. You cannot make a good call about a tool you have never used, and their students are walking into a world that is changing either way.

The future is already here. We learn to augment what we do with it, or we risk falling behind.

These are my own views, not a position of the student representatives or of the ANU.