KNOBE Studio — create, verify, and transform knowledge objects in your browser

Studio needs a browser with JavaScript modules and Web Crypto (any current browser over https or localhost). The engine could not be loaded in this session.

Working from a course journey?

Drag the journey .knobe.md here

Your instructor posted it with the assignment. It is read in this page and goes nowhere else.

Start from

Instructor: seal a reading Course-scoped terms for an assigned reading. The seal proves the file is intact, not that reuse is authorized. Student: seal a reflection Your own words at submission time. The seal records your declaration; it does not prove authorship. Researcher: seal a transcript A verbatim transcript with participant attribution and fidelity limits. The seal proves the record is unaltered, not that the transcription is accurate. Enterprise: seal a policy summary A condensed summary sealed in quarantine: an orientation aid, not the policy, until review clears it. Blank Engine defaults only. A single paragraph and a Seal click produce a valid object.

Title

Content

The human-readable markdown body. It is sealed with its own body_hash.

The content contains a KNOBE payload block. The sealed file would carry more than one block and report body_verified: omitted.

Author

Recorded in the sealed attribution as source 1.

All fields

Summary

Content type

Created date

License

Blank uses the engine default, CC BY 4.0.

Privacy level

Quarantine status

The originator's declared posture, not a receiver's clearance.

Attribution

Source 1 · the Author named above

Contribution

Role

This contributor holds rights in the contribution (rights_bearing: true)

Include good_faith_declaration: true Fidelity limits

Represents

Trust as

Do not infer (one item per line)

Use conditions

Permitted (one item per line)

Requested preservations (one item per line)

Consent note

Other

Language

Tags (comma-separated)

File preview

Updates as you type. The preview is the exact file the Seal button produces, including its hash.

Drag a .knobe.md file here

The file is read in this page and goes nowhere else.

No file handy?

A derivative declares its parent: the new object's parents entry records the original's title and payload hash. The original must verify first; a broken seal cannot anchor a chain.

Drag a sealed .knobe.md here to derive from it

The file is read in this page and goes nowhere else.

No file handy?

A journey is one sealed file that describes an assignment sequence: who seals each step, what kind of work it is, and the AI policy for that step. Its readable body is a syllabus-ready description; its sealed payload is what Studio reads when a student loads the file. Post both the journey file and this page's link with your Canvas assignment.

Revising an existing journey?

Course

Term

Journey title

Instructor

Steps

Syllabus preview

This text becomes the journey file's readable body. Paste it into the Canvas assignment description if you like; the file itself carries the same information for Studio.

Check a batch of submissions at once. In Canvas: Download Submissions on the assignment, unzip, then drag the folder here. Files are read in this page and go nowhere else; no student data leaves this device.

Optional: what should submissions chain to?

Drag submission files, or a whole folder, here

Files are read in this page and go nowhere else.

Seal a cohort receipt

The receipt seals what this table shows: at seal time, these files existed with these payload hashes and produced these verdicts. Verdicts and hashes only; student-declared names are not sealed in. Anchored anywhere with an independent timestamp, its one hash timestamps every listed submission.

Who is attesting

Recorded as the receipt's attribution, role cohort_verifier.

Submission verdicts for the loaded cohort
File	Title	Author	Integrity	Conformance	AI disclosure	Chain	Review

An accessibility adaptation (plain language, translation, captions, description) is sealed as its own object: it chains to the source by hash, credits the adapter, and states honestly what it preserves and what it omits. The source work remains authoritative.

Drag a sealed .knobe.md here to adapt it

The file is read in this page and goes nowhere else.

No file handy?

What sealing records

Sealing assembles your declared fields into a payload, computes a SHA-256 hash over its canonical form, and stores both inside the file. Anyone can later recompute the hash and see whether the sealed record changed. A match confirms integrity, not truth: it does not establish that the content is accurate, that the declared author wrote it, or that a use is authorized. The verdict vocabulary is the protocol's four-state model; the Lens page describes each state, and the specification defines the algorithm.

What Studio keeps

Nothing. Files exist in this page's memory until you download them. There is no account, no draft storage, and no history; reloading the page clears everything. Studio's engine, knobe-core.js, is published on this site and its verdict parity with lens.py is documented on the implementations page.