State the user, task, artifact boundary, and one bounded capability claim.
Final Showcase and ReflectionDemonstrate a bounded claim, defend the evidence, learn from feedback, and name what comes next.
The final showcase is an evidence defense, not a polish contest. Students demonstrate an app or equal-credit fallback, explain one decision, defend one source and security claim, disclose assistance, respond to feedback, and preserve a calibrated next step.
Bring a class-safe app or fallback and any evidence you want to use. If prior work is missing, use the supplied Study Sprint dossier. No public URL, live AI, account, paid tool, prior packet, video, polished interface, or personal disclosure is required.
Four outcomes you can demonstrate.
The focus is judgment students can show, not vocabulary they can merely repeat.
Connect a demonstration, process decision, source trail, and security decision to visible evidence.
Explain what AI or people helped with, what changed, what was checked, and who remains responsible.
Use specific peer feedback to improve one claim, control, explanation, or next test.
Two meetings with separate learning arcs.
Meeting 1 plans 68 taught minutes plus a 12-minute flex and access buffer; Meeting 2 plans 68 plus 12.
Rehearse an Evidence Defense
Choose an equal-credit route, reveal the six-part defense arc, complete three explicit rehearsal rounds, practice disclosure and question handling, and prepare evidence-based feedback.
- Route and defense arcChoose an own-artifact or supplied route; distinguish a bounded defense from a polished pitch.
- Three rehearsal roundsCommit a capability claim, evidence choice, and uncertainty response before the course rationale.
- Disclosure, questions, and feedbackMake assistance visible, answer from evidence, and turn critique into a next test.
- Rehearsal handoffPreserve the six-part defense, one hard question, and one revision target.
- Flex/access bufferUse the rehearsal studio, packet, paper, projected transcript, private writing, speech-to-text, augmentative and alternative communication (AAC), or LMS text.
Showcase, Defend, Revise, Reflect
Use an instructor-assigned route and four timed rounds to demonstrate evidence, ask bounded questions, give work-centered feedback, revise one decision, preserve observable course evidence, and complete a private reflection.
- Norms, mode, and rolesConfirm what may be shown, choose timing by class size, and assign presenter, evidence reviewer, and boundary reviewer roles.
- Four 10-minute showcase roundsEach round uses 4 minutes defense, 2 minutes evidence questions, 2 minutes feedback, and 2 minutes transition or revision.
- Calibrate, revise, and closeCheck feedback against evidence, revise one item, preserve submission evidence, and complete the course close.
- Flex/access and private reflectionFinish an equivalent presentation route, complete private reflection, and resolve submission questions without public disclosure.
Final Showcase Evidence Packet
Prepare and deliver one route-neutral evidence defense; preserve its purpose, demonstration, process decision, claim/source record, security or human-control record, assistance disclosure, limitation, anonymous feedback response, and next step.
What to submit
- Look in the LMS for an item named Final Showcase Evidence Packet. Submit only if that item is assigned. Use either the four-page packet, a rendered Showcase Rehearsal Studio summary, LMS text, DOCX/export, scanned paper, speech-to-text, an augmentative and alternative communication (AAC) supported response, or an instructor-approved accessible equivalent. You may use the Studio to draft the packet, but submit one final format only. The LMS supplies the deadline, points, late rule, and resubmission rule.
- Name the presentation route and artifact boundary; state the user, task, bounded capability claim, and one visible demonstration or supplied record. A public URL, live demo, video, polished interface, or prior packet is not required.
- Include one human process decision, one directly observed or source-supported claim with its evidence route and limitation, and one security, privacy, safety, or human-control decision with evidence and a next test or stop condition.
- Include an AI-use disclosure or no-AI statement: tool/person, type of help, what you changed or rejected, how you checked it, and who remains responsible. Do not submit a full chat, private code archive, account screen, or unnecessary identity evidence.
- Summarize one peer or reviewer feedback item without naming the person; record Accept, Test, Defer, or Reject; show the resulting bounded revision or justified no-change decision; end with one limitation and next step. If a peer is unavailable, use the fixed Study Sprint dossier comment, structured self-review, or instructor review. Private course reflection is separate unless the LMS explicitly requests observable reflection evidence.
Core sources and optional extensions.
The class deck contains the required explanation. These links support verification, deeper reading, or alternate access.
Course complete
Keep the final artifact, evidence trail, assistance disclosure, known limitation, and next test together so the work remains understandable after the presentation.