C6 · Week 7: Assignment 2 retro
A brief demo of your Assignment 2 prototype, then articulate the breakthrough.
No fresh provocation this week: the crit reflects on Assignment 2, the last static assignment, due the Monday of this week. Give a short demo, then articulate the breakthrough. From here the course pivots to the full-stack pipeline.
There is nothing new to write. The breakthrough comes from the PROCESS.md you
submitted with Assignment 2: pick the specific change that made the course click
and show it as a before/after. That file, written up in your repo by the usual
cutoff, is what the shipped half of this week’s crit mark reads from; the demo
is where you present it.
One piece of housekeeping rides along: your crit-7 starter, deployed and loading
at https://<your-crit-7-repo>.fly.dev/. The repo and its Fly.io token arrive
by Ed message at the start of the week; paste the token’s block inside the
checkout, run the one deploy command, and
open the URL. The untouched starter is what’s expected — there is nothing to
build — and the doctor course skill checks exactly this. Your tutor opens
the URL at the door; it carries no marks and doesn’t enter the crit
conversation. Next week’s ANU-system build is not the
moment to discover the token is still sitting in an unread Ed message, or that
the deploy path has never been tried.
The spec
The brief on this page poses the problem and leaves room for your response. The spec is the fixed contract: what your tutor considers when judging whether that response meets the requirements. Some lines can be checked mechanically; the rest call for human judgement.
- your Assignment 2 PROCESS.md is written up in the repo by the cutoff — it is what the shipped mark reads
- the breakthrough you present from it names something specific — a prompt, a harness change, an insight — not "better prompts"
- it shows the before/after: what the agent was doing, what changed it, and why it worked
- a short demo of your Assignment 2 prototype, presented in the session