The instructor designs and seals the sequence; students seal their steps against it; the TA checks the batch; disputes return to the instructor with a sealed record. Every arrow is a payload hash.
1 · Instructordesigns and seals the sequence→
2 · Studentsseal their steps against it↓
3 · TAchecks the batch in one table←
4 · Back to the instructordisputes work from the sealed record↑
Three paths
Instructor
Build and seal the sequence at knobe.org/studio (Journey tab).
Post the journey file and its description to the Canvas assignment.
Set the submission type to File Uploads.
Student
Download the journey file attached to the assignment.
Load it at knobe.org/studio, pick your step, write, and seal.
Upload the sealed file to Canvas like any other file.
TA
Download Submissions in Canvas and unzip.
Drag the folder into Cohort check with the journey loaded.
Read the table; export the CSV for the gradebook.
If the assignment restricts file types, the allowed list must include md, or Canvas rejects every submission. This is the most common setup failure.
What the file is
Readable headertitle, date, license: scannable by anyone
The work itselfthe student's own writing, readable anywhere, no app needed
Sealed recordwho made it, what it builds on, the AI declaration, and the hash that proves nothing changed