Lab 12 — Your Product Showcase

START HERE · YOUR LAB FILES

Open these resources

Each card opens the supplied file. Keep these alongside the lab; open the same paths in your downloaded course folder when using your AI.

Underlined filenames throughout the steps are clickable. A file you create yourself links to saving instructions, not a nonexistent download.

On this page

SESSION 12 / 8-minute demo + 4-minute discussion / within a 2-hour session

Present working software and the genuine evidence of how you built, checked and improved it.

Evidence target

Your existing product and indexed handoff, eight-minute demo and four-minute discussion with Jared.

Start the activity ↓Review the deliverables Lesson plan Slides

Before you start · recall, then check

Without reading your AI chat, explain one important decision you changed after observing evidence. Then point to the original artifact that supports your account.

Use about two minutes of the existing arrival/discussion time. Try in your own words, then check the source with a partner or coach. This is ungraded practice, not a new submission.

Need a hand? A supported route

Rehearse your approved journey with synthetic data and keep an offline fallback. Reuse existing artifacts instead of making a second portfolio. Arrange follow-up for behavior you cannot demonstrate; completion and certification are separate decisions.

Mac / Linux / Windows help · How to ask for useful help

Time: prepare during course-long homework; eight-minute individual demo plus four minutes with Jared in your assigned Session 12 slot. Team: your own product; disclose peer/AI assistance.

Quick start

First action: Open your own product's reviewed release and existing evidence index.

Finish with: An eight-minute demo and four-minute discussion of your actual project.

Step-by-step help for Session 12 — smaller steps, checkpoints and troubleshooting. Saving and asking for help.

Mac / Linux / Windows

Use the platform guide. Demonstrate on your supported workstation, identify tested and untested OS/browser combinations, and provide portable Markdown/CSV/images. A browser presentation is sufficient; desktop slide software and paid hosting are not required.

Your mission

Present the product you began in Session 02 to Jared Cluff. Show useful, visually appealing working software and how you built it responsibly using AI. This project supplies the skills-certification assessment: no separate student exam, hidden scenario or surprise live coding task. Course completion and AIQAA certification are separate awards.

Prepare your handoff

Use the project rubric and your approved assessment agreement to index evidence. Reuse your existing project artifacts; do not create a second portfolio. Missing evidence is unverified, not a pass; specific gaps get follow-up, not a separate certification test.

Use the showcase template. Link your own public repo, tagged release and exact commit; approved scope; milestone index; feature/fix PRs and substantive human feedback; test charter and reproduced regression; visual/accessibility iterations; data/business artifacts; recovery evidence; AI workflow/cost record; setup and limitations. Do not move application code into the lab-submissions repo.

Present in eight minutes

One minute: audience, problem and three core features.
Three minutes: main journey, saved result, useful error/recovery and responsive/keyboard behavior.
Two minutes: trace a real issue → branch → PR → feedback → fix → release chain, show meaningful regression evidence and point to earlier/intermediate history already reviewed with the instructor.
One minute: small-model use, an AI correction, budget and a business decision.
One minute: release, known limits, setup and next improvement.

Then discuss your actual decisions with Jared for four minutes. You may use your notes and project evidence. AI helped you build it; you should be able to explain what it does and how you verified it.

Be ready when the network is not

Rehearse from clean synthetic data. Keep a local copy and screenshots or a short recording. If working behavior cannot be demonstrated, arrange a follow-up; do not pretend a recording establishes unobserved functionality. Close private tabs, notifications and credential-bearing terminals.

Where work goes

Your own product repo is the source of truth. Share its full URL and the reviewed release with the instructor through the private cohort channel. An optional Session 12 index/summary packet may use the existing submission workflow; no certificate, real name, private feedback or application upload belongs there. Its text-only bot cannot follow links, execute your app or decide completion.

After your presentation

Jared privately records two decisions. The Certificate of Course Completion recognizes finished learning activities and your presentation, even if product quality needs more work. Labalicious Certified AIQAA requires demonstrated product quality, development over time, GitHub understanding and the other published skill areas. You can be course complete while certification remains not yet demonstrated. Receive specific feedback and return with improvements. No numeric average, automated award or separate examination.

The old simulator cards are optional rehearsal exercises, not the final product assignment.

Leave with a next step

Use the existing closing/debrief time: explain one claim you verified, one limit and your next action. Reuse the lab’s artifacts; this adds no separate worksheet or graded test.

Your own product repository is the source of truth. Share its reviewed version through the instructor-approved channel.

Product Studio roadmap · Sharing and review guide

Opening the next session does not mark this one complete. Progress tracking is optional and does not award a credential.