THE UNIVERSITY OF ALABAMA®
myBama
AI-enhanced Educational Game Design
Evidence Portfolio · D1–D5

Your portfolio

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 a reviewer can compare the submitted file with the recorded digest. A hash does not prove authorship, learning, or that the artifact was independently validated.

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.

Keep your GenAI Provenance Log current — it is your AI-use disclosure of record.

Google AI Studio → TeachPlay

Submit the game and the evidence behind it.

Build the smallest defensible game loop in Google AI Studio Build mode, test the public preview, then attach the URLs and evidence that let an instructor inspect the artifact.

  1. Provide the live preview URL and, when available, the exported GitHub repository URL.
  2. Attach the objective-to-mechanic crosswalk, a short playtest record, and the AI provenance log.
  3. Add two or three still images plus a short recording that show the actual loop, not a marketing screen.
  4. Write one revision note that connects an observed trace to a concrete change.

The portfolio records what you submit; instructor approval still depends on inspecting the real artifact and its evidence.

Open the concrete prompt and integration playbook →

Four-panel illustration of a playable preview, design crosswalk, playtest observation, and revision record connected as a submission packet.
Generated visual: the submission packet keeps the game, design logic, observed playtest, and revision decision together.
The Five Slots

One artifact per deliverable.

Drop a PDF, a zipped prototype folder, a short recording, 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.

Filled: 0 / 5 · Manifest status: incomplete
Download manifest.json Download static page Preview in assertion →
View live manifest JSON 
{}
How Hashing Works

Three reasons to hash locally.

Privacy

Files never upload

SHA-256 runs in your browser via crypto.subtle.digest. The handbook sees only the hex digest — never the bytes.

Integrity

Evidence becomes verifiable

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.

Portability

Move the hash, not the file

Pin the artifact wherever you like — Drive, LMS, personal site. The credential refers to the content, not its location.