For instructors
Point it at your course in two minutes
Fill in five fields and generate a link. Your wording is encoded into the link itself, so there is no server, no database and nothing to keep in sync — send the link and your students see your policy instead of the defaults.
Configure it
Your link will appear here.
Kept in your own browser only, until you generate a link. Nothing is uploaded. When a link is active you will see an amber bar at the top of every page naming your course — that bar is how a student knows the policy they are reading is yours.
Policy wording you can copy
Three sentences that close the gaps students actually exploit. Adapt the bracketed parts.
Generative AI may be used in this course only where an assignment says so in writing, and only with disclosure. Where an assignment is silent, treat AI use as prohibited and ask me before you start — asking is never penalised. AI must never be used for hazard, quantity, incompatibility or waste decisions, for any timed assessment, or for interpreting your own experimental data; for those, use the safety data sheet, the lab manual, and [your demonstrator]. Any permitted use must be verifiable by you, cited to sources you have read, and declared using the five-line template at [link].
Using it in class
- Run it as a discussion, not a handout
- Ask students to bring a task they are unsure about and work the four questions aloud. The disagreements are the lesson, particularly on the second question, where students routinely cannot name the skill being assessed.
- Make the grey column the assignment
- Give them the middle list and ask which items they think should be permitted in your course and why. You will learn where your syllabus is ambiguous, which is cheaper than learning it from a misconduct hearing.
- Say the quiet part about grading schemes
- Students assume a pass/fail course lowers the stakes. The integrity standard is identical, and the practical consequence — arriving in the next course without the skill — is worse, because nobody noticed.
- Show them one fabricated citation
- Nothing changes behaviour faster than watching a plausible DOI resolve to nothing in front of the class.
Changing the questions themselves
Everything students read lives in src/content.mjs, with no logic in it. Edit the questions, the nine answers, the three lists or the failure modes, then run npm run build and redeploy. The static pages, the interactive test, the sitemap and the structured data are all generated from that one file.