The course-wide rules for late work, extensions, declared assistance and getting help.

Policies and support#

Late work and extensions#

No late submissions are accepted after a deadline passes, in either direction: an instrument that only starts working the day after First Instrument was due is marked as not submitted, not as submitted-with-a-penalty. Extensions exist instead of a penalty scheme, and have to be arranged with Marisol before the deadline, not after it — a request made once a deadline has already passed is asking for a different thing than an extension.

This is a stricter rule than most late-work schemes, and it’s deliberate: an instrument that has to run unattended for a stranger in week 12 is exactly the kind of thing that fails quietly if “I’ll finish it tonight” is allowed to become a habit across the semester.

Declared assistance#

Say what you used to build each submission, and how: an autocomplete suggestion accepted without reading it, an agent that wrote a whole file, a conversation that only shaped how you thought about a constraint before you wrote the code yourself. Put it in the submission repository’s README, under a heading of its own — not scattered across commit messages a marker has to reconstruct.

This isn’t a disclosure rule borrowed from some other course: the whole premise of studio time is a hand testing an instrument at the keyboard, not a picture of one, so a build with an undeclared agent behind it is a different claim than the one your crit was actually judging. None of these are penalised on their own — the assessments page and the assessment briefs describe how each piece of work is actually marked. What’s marked down is a submission whose account of its own process doesn’t match what a marker can see in the repository once they go looking.

Academic integrity#

The work you submit is yours, with any assistance declared per the section above. Presenting someone else’s instrument, or the unattributed output of a tool, as your own semester’s constraint is misconduct handled under Slop University’s ordinary academic integrity process, not a course-specific one.

Getting help#

Ask during a studio first — most of what a studio actually teaches is diagnosing why a working build under your own hand behaves differently under someone else’s, and that’s easiest to do live. Idris runs the office hours announced each studio for anything that can’t wait. Email either teacher for anything that shouldn’t wait for the next studio at all: a question about the brief, an access need, or a personal circumstance affecting a deadline.