Show your work is a query string

A 400-line solution appears in a student's solver.py at 23:52, eight minutes before the deadline. Another student's solver.py grew over four evenings, 30 lines at a time, with a failed refactor on Tuesday that was reverted Wednesday.

Both files pass the tests. The grader opens solver.py?history on each student's files URL. The journal lists every write with a timestamp and a content hash; ?at= reads the file as it was at any of them, ?diff shows what changed between two. Next to it, /api/v1/terminal/raw?format=html renders the student's shell session: the test runs, the tracebacks, the command that finally worked.

The instructor doesn't install monitoring software or demand screen recordings. Nobody asked the students to keep a log; the container kept one.

The process is in the journal, and the journal doesn't need to be turned on.