One topic in the first class: who does what on a team, and one story followed from start to finish. Quiz 3 closes the class. The agent-safety reading below is due before the second class, which is the whole-class Phase 2 delivery.
Before the first class
- Nothing new to install.
The first class
Who does what, and one story from start to finish — the merge done by the reviewer who approved, never the author. Then Phase 2: the delivery note and what a good one looks like, the checklist below, how the phase is read, and ten minutes on your own team's repository against the checklist, one laptop per team. Quiz 3 runs at the end of the class.
Reading
Required, before Wednesday 7 October. Agent safety and the sandbox — why the tool you build with is allowed to touch some things and not others, one documented case, what the Antigravity sandbox does, and why you still own what shipped — is no longer a lecture. It is a reading, and it replaces the lecture on the same topic.
Before the second class
-
Finish Phase 2 and tag it in the repository — exactly
phase-2, lowercase. The tag is what gets graded. -
Finish
docs/delivery-notes/phase-2.md. You present from it. -
Every story has an assignee, set with the control on the right of the
issue, and every member has at least two. Both schema files are on
main. - Have your system reachable at its public address. You present from that address, not from a laptop.
- Prepare your own questions for the other teams. Arriving without them is itself a failure of the session.
The second class
It opens with a fifteen-minute merge-conflict clinic: what a conflict is, how to avoid most of them, and one resolved live in the example repository.
Then the Phase 2 delivery: five teams, twelve minutes each, presented from the repository at the tag with the delivery note as the script. It is not a queue of private meetings: all teams are in the room, each team presents, and the rest of the class is the audience and the question pool. You take questions from the room, and you ask them. The minute-by-minute format is on the deliverables page.
Due this week
Phase 2 — personas, stories, the schema, the split, the environment, and your token plan. 10 marks. Due Wed 7 Oct 2026, before class. The full checklist — where each item lives, who owns it, and what done means — is on the deliverables page. The eleven items:
- Personas —
docs/personas.md, two to four named roles; example deleted. - Stories with acceptance criteria — the Issues tab, at or above the floor, none outside proposal §6.
- The split — the assignee on every story; every member holds at least two.
- Boundaries — criteria on the stories that share data, naming the schema columns that pass and what happens when one is missing.
- Schema, the SQL —
db/schema.sql, runs on an empty project, keys, RLS on and a policy on every table. - Schema, the document —
docs/schema.md: what a row means, how tables relate, who may read and write and why. No column lists. - Backlog copy —
docs/backlog.md, the open stories at the tag. - Token plan and first ledger entry —
docs/finops-ledger.md. - Environment — every member has one own-account commit this phase.
- Delivery note —
docs/delivery-notes/phase-2.md, five headings; a worked example is on the deliverables page. - Tag — exactly
phase-2, onmain, after the last merge.
How it is read — three levels per row, the ledger binary, workflow slips as warnings — is in the rubric. The peer review form for Phase 2 is due Sun 11 Oct 2026, 23:59.
The phase is tagged in the repository at its due date, and the tag is what gets graded — not a submitted document and not a slide deck. See your repository for the tag names and the rules, and deliverables for the date and the floor.
Use
- Your repository — the tag names, the layout, and the pull request rules.
- Deliverables — the Phase 2 date, weight and checklist.
- Team roles — who answers for which part of the delivery.