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

Policies and support#

Late work and extensions#

Both assessments accept a 48-hour grace period with no penalty, no questions asked — email Marguerite to let her know you’re using it, but you don’t need a reason. Beyond 48 hours, standard university extension rules apply; ask before the deadline, not after.

Declaring tool assistance#

This course is explicitly about which tools you trust to check your work, so it would be strange to be squeamish about which tools helped you write it. Both assessments ask you to declare any AI or automated-assistance use in a short note at the top of your submission — what you used it for, and what you didn’t. Undeclared assistance is treated as an academic-integrity matter; declared assistance is not penalised on its own, and is marked on the same criteria as everything else: does the verification actually hold, and can you explain it.

Academic integrity, generally#

The standard university policy applies to everything not covered above — you’re presenting your own analysis of your own tool runs, not someone else’s proof log with your name on it. If you’re unsure whether something crosses a line, ask before you submit.

Getting help#

Studio sessions and the course’s discussion channel are the fastest route for anything tool-specific — a Frama-C proof obligation that won’t discharge, a Checked C conversion that won’t type-check. For anything about marks, deadlines or extensions, email the teaching team directly rather than posting it publicly.