Course policies, setup guides, and other administrative information.
20 items
AI use and academic integrity
Using AI tools in this course is allowed and expected, for students and convenors/tutors alike — this page gives a bit more detail on what that means in practice
Assessment
The model behind the three assignments and how everything is marked: the shared rubric, what you submit, deadlines, extensions, and appeals
Claude Code cheatsheet
CLAUDE.md, /clear, plan mode, and the rest of the Claude Code habits the course leans on, all on one page
Code of conduct
How we treat each other in this course
Communication
Where to go for what, and what each channel is actually for
This course is an experiment
COMP4020/8020 is running for the first time, so here's how we'll keep you in the loop, and keep things fair, as it evolves
Course overview
Learning outcomes, structure, and expectations
Crit agents
The named agents, one per crit group, that sit the same coursework you do and remember what they built with you
Enrolment
Permission codes, crit-group registration, late enrolments, pre-requisites, the census date, and joining after week 1
Ethics
Should this course even exist? And should you take it?
Following along from outside
The coursework is public end to end. Here's what anyone, or anything, outside the enrolled cohort can and can't do with it
Generating images
How to generate images for your prototypes --- with the course key, or a third-party text-to-image API
Your hosting access
Every full-stack repo deploys to its own app on Fly.io — this page is the whole story of the token, the deploy, and the shape your app has to keep
The lecture-demos repo
The public repo the live demo runs in. Clone it in week 1, pull to follow along, and reset at the start of each lecture
The lecture structure
How a lecture runs: one live demo launched on the premise you set and left running, two check-ins where you push it further, and Q&A to close
Your LLM access
The course issues you a Claude API key. This page covers wiring it into Claude Code, what gets logged, and how your usage allocation works
Onboarding
The whole course setup as a terse checklist: accounts, tools, your API key, and the course skills plugin, each linking to the full how-to
Your participation
Everything the course asks of you, as one list — the week-1 setup, the weekly rhythm, the assignment deadlines and the standing responsibilities — with links to the detail
Software and platforms
What each platform is, who pays for what, and the course policies that come with working agentically on ANU infrastructure
The studio crit model
How a studio crit works and how it's marked: the five beats of the session, the feedback protocol, and the two marks each week carries