The course-wide rules for late work, extensions, academic integrity and getting help.
Policies and support#
Late submissions#
Work loses 5% of the available mark per day it is late, for up to five days. After five days the submission is marked as a demonstration of timeliness rather than content, and receives zero — this applies however good the render looks. “The pipeline was still running” is not a circumstance, it is the assessment; plan render time into your schedule the way you’d plan for a camera that jams.
Extensions are granted for documented circumstances (medical, compassionate, equipment failure with evidence) and are requested by emailing the convenor before the deadline, not after. A request made once the deadline has passed is a late submission with a longer story attached.
Academic integrity, for a course about synthetic media#
Most academic integrity policies exist to stop you from passing off a machine’s output as your own. This course inverts that: using generative models is the medium, not the violation. What would be misconduct elsewhere — a diffusion model, an LLM, or an automated pipeline producing the footage, the script, or the voiceover — is simply how the work gets made here. Hiding that it happened is the one thing that isn’t allowed, because the pipeline itself is often part of what’s being assessed.
Given that, integrity in SLOP2758 means something more specific than “declare your AI use”:
- Declare your pipeline, not just that one existed. Say which tools or models did which job, what you wrote or directed by hand, and what came out of the generator with no intervention. “AI-assisted” is not a pipeline description; “a diffusion model generated the base footage, I wrote and fed every prompt, and the voiceover is a text-to-speech pass over a script I wrote myself” is.
- In the Slop Teardown, say plainly whether your artefact is found or invented. Presenting an invented artefact as a real find is the one move that voids the assessment outright, because the teardown is an argument about something claimed to exist; the argument is only as good as that claim is honest.
- Don’t submit someone else’s pipeline, prompt library, or teardown research as your own. Building on a classmate’s published prompt template is fine if you say so and change it into something that’s actually yours; handing in their template unchanged is not different from handing in their essay unchanged.
- Cite what a human wrote. Direction, editing decisions, and the director’s statement on the capstone are yours in the traditional sense — the usual rules about your own words apply there without modification.
If you are ever unsure whether a specific disclosure is enough, over-disclose and ask; a marker who has to guess at your pipeline will mark the guess, not the work.
Getting help#
Contact details and the best channel for each kind of question are on the people page — email the convenor for anything that affects the whole course (deadlines, marking, scope), and bring week-to-week build questions to the Set session rather than to an inbox. Set staff read questions asked in person faster than the same question in writing, because most build problems are faster to show than to describe.
Access and equity#
If a disability, caring responsibility, or other circumstance affects your ability to meet a deadline or attend a session, contact the convenor as early as possible — ideally before it becomes urgent, not after. Adjustments are made to the requirement, not to the standard the work is judged against.