Upload each deliverable as you finish it. The browser hashes the file (SHA-256) locally —
the hash is what gets stamped into your credential's evidence[] array, so the
assertion points to an artifact that provably existed at submission time.
Files never leave this browser tab. Export the manifest when you're ready to send it to a facilitator or pin it to a permanent URL.
Drop a PDF, a zipped prototype folder, or paste a link. Each slot accepts exactly one artifact
per deliverable — re-uploading replaces the prior hash and records a new submitted
statement in the learning-analytics queue.
{}
SHA-256 runs in your browser via crypto.subtle.digest. The handbook sees only the hex digest — never the bytes.
The hash anchors each artifact to your assertion. A facilitator who re-hashes the file you send can confirm it's the same one you submitted.
Pin the artifact wherever you like — Drive, LMS, personal site. The credential refers to the content, not its location.