Where it started
What idea, image, question, or constraint began the work, and who or what supplied it?
Process dossier
Show how the work was made.
The dossier tells reviewers how your work came to be. It is scored on two things: whether the account is clear and honest, and whether your choices show.
What to prepare
A clear account beats a technical spectacle.
The dossier is not scored on how much a machine wrote, how technical your process was, or how much evidence you attach. A plain-language account can earn full marks. Specific beats long: one real example is worth a page of description.
Tools and systems
Which models, apps, agents, or scripts did you use, roughly when, and for what?
How it was made
Walk through the process from start to finished text, plainly enough for a non-technical reader.
Your choices
What you asked for, kept, rejected, and changed — with at least one specific example. Curating generated text counts fully.
What the machine contributed
Which parts of the text, structure, or ideas came substantially from machine output. Approximate and honest is right.
Rights and ethics
Source material and permissions, any imitation of living authors, and the privacy of real people.
How it is scored
Twenty points, two questions.
10
Clarity and honesty. Can a reader understand what you did, and does the account hold up against the evidence you supplied?
10
Direction. Do your choices visibly shape the work? Revision is one form of direction, not a requirement.
✓
Pass/fail. The dossier must show that a machine took part, and rights and privacy must be respected. Finalists need at least 8 of 20.
Evidence levels
Three ways to document process.
All three can earn full marks.
01
Written dossier: a 3–8 page account.
02
Process portfolio: selected prompts, drafts, notes, examples, or diagrams.
03
Repository or logs: GitHub, GitLab, archive, or commit history. Reviewers sample; they do not audit.