Michelle Blomberg

Students build an AI storyteller, the Teller, from one person’s consented archive, then interview it to tell that person’s story.

Module 0

Getting Started

Week 1 · 6 hours

Objectives

  • 0.1 Set up and verify every core course account, and record and share a short narrated test recording (Course Competency 8)
  • 0.2 Write and revise a prompt in Gemini, and evaluate its answer critically (Course Competency 8)

Technology Setup

Set up your accounts and download the course software in Week 1. The captioned AI and Setup video walks through each step. Post your Discord introduction by Wednesday at noon, Arizona time, so classmates can comment before the Thursday deadline.

Equipment: a Mac or Windows computer that can run Premiere Pro (see Adobe’s requirements: at least 8 GB of memory, 16 GB is better, and room for video files). A Chromebook, phone or tablet will not work. You also need headphones, a microphone (a phone headset works) and internet steady enough for video calls and uploads. All software is free through the college.

Technology Setup (10 points, Process Work)

This assignment measures Module Objective 0.1, which supports Course Competency 8.

You need a Mac or Windows computer. A Chromebook, phone or tablet will not work, because the course uses Adobe apps. If you need a computer, GCC lends Macs and PCs: request one with a Student Technology Request.

Set up these core accounts in Week 1. Apps used only in this course are set up in the module where you first use them.

ToolForHow to get it
CanvasAssignments and gradesLog in with your MEID (Maricopa Enterprise ID: the username and password for every Maricopa account). Problems? Contact the IT Service Desk.
Maricopa Google accountGmail, Drive, Docs, YouTube (unlisted videos), GeminiSign in with MEID@maricopa.edu
GeminiResearch, writing and feedback; never visual designgemini.google.com with your Maricopa account, never a personal account
Google SitesPublishing web pages and interactive worksites.google.com with your Maricopa account; nothing to install
Adobe Creative CloudThe district license for every design appadobe.com, signed in with your Maricopa email; install each app when a module first needs it
DiscordQuestions, critique and class communityJoin the GCC Digital Media Arts server at discord.gg/fyzAXNS4yF and open the AVC150 channel; app at discord.com/download
Gemini NotebookBuilding and interviewing your Teller, from Week 2notebook.google.com with your Maricopa account
A recorderShowing and explaining your work all termOBS Studio (free). Google Meet, Zoom, QuickTime or the Windows Snipping Tool also work. Sound work may use Audition, Reaper, Audacity or a phone voice memo. Screen-reader users: the recorder you already use.

Submit one Google Doc, Google Slides page or Miro board with:

  1. Proof that each core account works (screenshots, or a short written note for screen-reader users).
  2. A link to a 10-second test recording with your voice and something from your work, shared unlisted.
  3. Your Discord introduction (your name and how to say it, your program, one thing you want to learn, and two examples of past work with alt text or a description) and three comments on classmates’ introductions.

Grading (10 points): core accounts 4; test recording 3; Discord introduction 2; three comments 1.

AI: none; log “No AI used.”

Syllabus

Read the syllabus, linked as Syllabus in the Canvas course menu, then take the quiz.

Syllabus and Course Overview Quiz (5 points, Exercises)

Every question is answered in the syllabus. Questions include:

  1. When is work due, and what happens if it is late? (Noon, Arizona time, on Thursdays and Sundays. Work up to 24 hours late loses 10%; after that it is not accepted.)
  2. Where do private questions, course questions and critique go? (Private questions go to your instructor in the Canvas Inbox. Course questions and critique go in the course channel on the Digital Media Discord, or in the matching Canvas discussion if you cannot use Discord.)
  3. When is using AI in this course not cheating? (When the use is assigned, recorded in your AI-use log, and you are graded on your own thinking and work.)
  4. Which account must you use for Gemini, and why? (Your Maricopa account. Google states that what you enter there is not reviewed by people or used to train AI models.)
  1. What may a Teller do, and what may it never do? (It answers only from your archive and always says it is an AI. It speaks in the first person only with the narrator’s written agreement. An AI voice is labeled and never copies a real person.)

It ends with the AI-Use Agreement: keep the AI-use log, disclose AI use, follow the upload rule for a real narrator’s material, and never copy a real person’s voice or face.

Private question (0 points): Will you be under 18 at any point this semester? (Yes or No) This is not scored. It only decides which tool options you get, and only your instructor sees your answer.

AI Primer

This course uses Google Gemini in assignments. The rules for AI use and the AI-use log are in the AI section of the syllabus. Google’s own wording on how your Maricopa account protects your work: Gemini for Education and Google’s education FAQ.

AI Primer (10 points, Process Work)

What this is. Your first time using Gemini in this course, and it takes about an hour. No experience with AI is needed. Complete Technology Setup first.

What Gemini is. Gemini is an AI chat tool from Google. You type a request, called a prompt, and it writes an answer. It learned from an enormous amount of text written by people, so it can sound knowledgeable about almost anything. It does not know you, and it has never been where you have been.

Why this assignment. Some assignments in this course use Gemini for research and feedback. Before you use it for that, you will see for yourself what it does well, where it falls short, and what you bring that it cannot.

Your work stays yours. You use Gemini through your Maricopa account, so what you enter is not reviewed by people and is not used to train AI models. See AI in This Course for Google’s exact wording.

This assignment measures Module Objective 0.2, which supports Course Competency 8.

Part 1: Sign in

  1. Open Chrome and go to gemini.google.com.
  2. If you see Sign in in the top right corner, click it. Sign in with your Maricopa account: your MEID followed by @maricopa.edu, then your MEID password on the Maricopa sign-in page.
  3. Check the top right corner. It should show your Maricopa account. If it shows a personal Gmail account, click the picture and switch to your Maricopa account.

If Gemini does not open or says it is not available for your account (this can happen for students under 18), message your instructor in Canvas Inbox. You will receive an equal option with the same grade.

Part 2: Ask the question

  1. Click the box at the bottom that says Ask Gemini.
  2. Type Do I need to learn AI to get a good job in the digital media industry? and press Enter.
  3. Copy your prompt and Gemini’s answer into a Google Doc.

Part 3: Read it like a critic

  1. In your Doc, mark:
    • one point you agree with;
    • one point that sounds generic, overstated or like a sales pitch;
    • one question you would rather ask a working professional in the field.
  2. Gemini is made by Google, a company that sells AI. Write one sentence on how that might shape its answer.

Part 4: Give it better directions

A stronger prompt tells Gemini four things: a role (who it should act as), a task (what to do), context (who it is for and why) and a format (how the answer should look). Example: You are a hiring manager at a small design studio in Phoenix. List the skills you look for in a new junior designer, and say honestly where AI skills rank among them. I am a first-year community college student. Use a short ranked list.

  1. Rewrite your prompt using all four parts, and add one detail about yourself: the kind of work you want to do. Press Enter.
  2. Copy the new prompt and answer into your Doc. Write one sentence on how the answer changed.

Part 5: Reflect

  1. In four to six sentences: Did either answer change how you think about AI and your career? Where might a tool like this help you in your own work, and where would you not want to use it?

Part 6: Start your AI-use log

  1. At the bottom of your Doc, add a table with three columns: Tool, What I asked, and What I kept, changed or rejected. Add one row for this assignment. Every assignment in this course has a row like this, so your instructor can see how you used AI and what was your own.

Submit the link to your Google Doc.

Grading (10 points): critic’s mark-up 3; revised prompt with your own detail 3; reflection 2; AI-use log row 2.

Instructor notes
  • Before the term: create the course channel on the Digital Media Discord and put its invite link in Technology Setup and an announcement. Confirm the class is on the district Creative Cloud list.
  • Canvas: set the late policy as one 10% deduction in the 24-hour window, and the hard close as each item’s Available until date.
  • Week 1: post the captioned welcome announcement, reply to each Discord introduction, and message anyone without one after the Wednesday post.
  • Grade Technology Setup within 48 hours. Missing software gets a fix, not a deduction, on the first try. Watch for personal Google accounts.
  • In Week 1, privately ask each student about the tools, assistive technology and computer they use. Refer accommodations to Disability Resources and Services and computer needs to the Student Technology Request, and approve an equivalent recorder for anyone who needs one.
  • Note students under 18 (the private quiz question) and any blocked Gemini feature, and set up the equal option before it is needed.

Students under 18

Find out in Week 1: the Syllabus and Course Overview Quiz asks each student privately, as a 0-point question, “Will you be under 18 at any point this semester?” Ask every term.

ModuleStepWhat may not workAlternate assignment or software, same grade
Module 0Consent and Privacy: real-narrator pathA student under 18 arranging and running an interviewAn adult narrator; a parent or guardian co-signs the student’s side of the Consent Affirmation and Signed Agreement; you approve the narrator in the Pitch Package; interview in a public place or with another adult present
Module 0Technology SetupGemini Notebook test may be limited; uploading to YouTube may be limitedNote the limit in the setup document and message the instructor; share the test recording from Google Drive (new)
Module 1, Module 5, Module 10Practice Teller, Your Teller and Revised TellerGemini Notebook may be limitedA Teller the instructor runs from the student’s sources, or the Practice Archive path
Module 2Pitch Package: character pathTopic limits under 18 (no self-harm, sexual content or graphic violence); Gemini may block sources or answersBody image as media critique with your approval; otherwise switch topics or move to the narrator or self-interview path
Module 3Interview RehearsalGemini Live may be limitedType the practice, or practice with a classmate or family member
Module 0AI in This Course: any research stepDeep Research may be limitedGCC Library databases
Module 10Voice TestGemini Notebook audio tools (a labeled AI voice) may be limitedThe student’s own reading, or on-screen text

Video: Get to Know Your Instructor (about 5 minutes)

  • Name, how to say it, background in storytelling and digital media, and why this course uses a Teller.
  • How to reach you: Canvas Inbox, one business day; the five optional Studio Sessions.
  • A personal note: a story from your own family you would want kept.

Video: Getting Started in the Course (about 8 minutes)

  • The Teller is the main product; the recorded, edited interview is the finished story.
  • The two passes: the Practice Teller on the Practice Archive in Week 2, then the real Teller from Week 6.
  • The consent sequence (Weeks 3 to 5) and why nothing is uploaded before the Signed Agreement.
  • The deadline rhythm: Discord the day before, noon Thursday and Sunday, 24-hour late window at minus 10%.
  • Week 1 order: course information and AI in This Course, Technology Setup, then the AI Primer.

Video: AI and Setup (about 8 minutes)

  • Ask the demo Teller and the plain Gemini app the same question about the WPA life history.
  • Check both answers against the source on screen; show which one cites and which one invents.
  • A model predicts likely words; Gemini Notebook answers from sources but can still invent where the archive has gaps.
  • Canvas, the Maricopa Google account, Gemini Notebook with the Maricopa account, Discord.
  • Make and share a 10-second test recording.
  • Build the demo Teller (about 4 hours): one life history from the Library of Congress collection American Life Histories: Manuscripts from the Federal Writers’ Project, 1936 to 1940. Read the whole history first (some content is heavy), confirm its rights statement, add a content note. Load the transcription and catalog record into Gemini Notebook, write narrator-mode instructions that open with an AI disclosure, test 20 questions, share read-only.
  • Build the Practice Archive (about 13 hours), shared read-only: fictional narrator Ada Ruiz’s profile; five interview excerpts (about 9 minutes) read by a volunteer who signs the Signed Agreement, or a labeled AI voice; a Premiere Pro machine-draft transcript with three planted errors; five documents and letters; ten public-domain period photographs with credit lines; SAMPLE consent documents including a consent video; a question bank; a metadata sheet with three model rows; a model Practice Teller and its 90-second recorded interview. Label every text file as fictional. No AI images.
  • Templates: AI-use log, critique record, sample AI-use statement, voice guide, error audit log, conversation map, key art, recording checklist, case-study page, narrator review form.
  • Add alt text to every course image and run every page through the accessibility check before it opens.
  • Run five recorded Studio Sessions (Weeks 4, 6, 11, 12, 15); post days and times a week ahead.
  • Return each step’s feedback before the next step depends on it, usually by Wednesday at noon. Answer Canvas Inbox within one business day.
  • Before publishing: rebuild the Syllabus and Course Overview Quiz as a Canvas quiz; post the McCloud e-reserve link in Module 9; verify the Google Workspace for Education and Adobe for Education AI-training and retention statements in the Project Information Sheet and Signed Agreement against current terms; confirm which records the college keeps after a withdrawal (Part E); post your name and district email on the Canvas home page (the consent documents point narrators there).
  • Copy the Instructor Notes pages into the course unpublished; they hold the planted-problems answer key.

Competency map

CompetencyModulesEvidence
1. Overview of storytelling1Interviewing the Demo Teller
2. Voice, place and culture2, 14Pitch Package; Final Project criterion
3. Language, image and power0, 2, 7, 9, 14Pitch Package; The Grandfather Bot and Your Teller; Teller Portrait and Archive Cards; Final Project criterion
4. Principles and techniques of a personal story3, 4, 5, 7, 8, 14Interview Guide and Consent Affirmation; Interview Rehearsal; Visual Field Journal; The Interview and Video Consent; Signed Agreement, Transcript and Archive Inventory; Sources and First Instructions; Held-Out Questions; Dramatic Question and Map Thumbnails; Final Project criterion
5. Elements presented for peer review2, 6, 8, 10Story Circle: Whose Story, Which Teller?; Voice Guide; Voice Guide Workshop; Conversation Map Critique; Peer Interviews
6. Edit and finalize the story1, 5, 6, 7, 10, 12, 13, 14Project 1: The Practice Teller; First Test; Instructions v2 and Voice Test; Error Audit and Revision; Revised Teller; Paper Edit and Rough Cut; Final Cut: Titles, Captions and Credits; Final Project criterion
7. Storyboard with design principles8, 14Conversation Map; Final Project criterion
8. Graphics, video and sound0, 1, 9, 10, 11, 14Technology Setup; AI Primer; Project 1: The Practice Teller; Teller Portrait and Archive Cards; Voice Test; Recording Plan and Test; Final Project criterion
9. Produce a short digital story11, 12, 13, 14Key Art; The Recorded Interview; Paper Edit and Rough Cut; Final Cut: Titles, Captions and Credits; Final Project criterion
10. Archive the story1, 4, 5, 13, 14Practice Archive and Metadata; Signed Agreement, Transcript and Archive Inventory; Sources and First Instructions; The Archive Package; Final Project criterion
11. Present for peer review12, 14Narrator Review; Living Archive Showcase; Final Project criterion
Module 1

The Practice Teller

Week 2 · 10 hours

Objectives

  • 1.1 Organize and describe archive items with accurate metadata, specific alt text and a corrected transcript excerpt (Course Competency 10)
  • 1.2 Build a Teller in Gemini Notebook from an archive, write its instructions, and test and correct its answers (Course Competency 6)
  • 1.3 Record and caption a short interview with a Teller that draws out one moment of the story (Course Competency 8)
  • 1.4 Explain the difference between a story and a topic, using two of the demo Teller’s answers as examples (Course Competency 1)

Overview

This week you make the whole project once, in a small version. You use the Practice Archive: interviews, letters, documents and old photos about a fictitious narrator, Ada Ruiz. Her family settled at a farm workers’ camp near Glendale, and her mother sewed her a dress from flour sacks for a camp dance. You build a Practice Teller from it in Gemini Notebook, test it, and record a short interview with it. The archive has mistakes planted on purpose. Finding them is part of the work.

Start by interviewing the instructor’s demo Teller, built from a real 1930s life history that is now free to use, so you see what you will build.

The course idea comes from cartoonist Amy Kurzweil’s graphic memoir Artificial: A Love Story, in which her father builds a chatbot of her grandfather from his letters and writing, and she gets to know her grandfather by talking with it. She is a cartoonist, not an AI expert, so her way in is the same as yours: a story she cared about and a lot of questions.

Watch

One captioned instructor video: what a story is, a live interview with the demo Teller, then the archive and the Teller, with a guided lab on building and interviewing the Practice Teller.

Read

Projects Like This

Each of these projects follows the same steps as this course: collect an archive, build an AI that answers from it, then interview it. They are optional; choose any you like. Some of these stories deal with loss. In this course, every Teller is built with consent from the person whose story it is (or their family), or from public sources.

Practice

  • Ask the demo Teller five questions: two about facts, two that ask for a scene (“Take me to the day…”), and one the life history cannot answer. Note which answers cite a source, and what it says when it does not know. Use these notes for the Interviewing the Demo Teller discussion.

How to Build a Teller in Gemini Notebook

You build every Teller in this course the same way: the Practice Teller this week, and your real Teller in Module 5. Gemini Notebook (it was called NotebookLM) answers only from the sources you give it and shows where each answer came from. The instructor video in this module shows each screen. Google sometimes renames a button; if a label is different, look for the same idea.

  1. Sign in. Go to notebook.google.com and sign in with your Maricopa Google account (your MEID@maricopa.edu). Never use a personal account: the Maricopa account keeps your narrator’s material private and out of AI training.
  2. Make a notebook. Select Create new notebook. Name it so you can find it: “Teller: Practice Archive” this week, and “Teller: [your project title]” in Module 5.
  3. Add your sources. Select Add sources, then upload from Google Drive or your computer. Add the corrected transcript (a Google Doc), photographed letters and documents (PDF), photographs with their captions, and any short audio. With a real narrator, add only what the Signed Agreement clears for AI. This week, add the Practice Archive files from the course folder.
  4. Name every source. Rename each one so a citation makes sense, for example “Interview 1, corrected transcript” or “Letter to Wilma, 1938.”
  5. Check every source. Open each source in the Sources panel and make sure the words came through. If a handwritten page did not read well, type it up and add the typed copy as its own source.
  6. Write the instructions in a Google Doc first. Use the starter below. Keep the Doc: its version history is part of your grade.
  7. Give the Teller its instructions. In the Chat panel, open the chat settings (Configure chat), choose Custom, paste your instructions and select Save.
  8. Test it. Ask three questions: one the archive can answer, one it cannot, and one that asks for a scene (“Take me to the day…”). Select the small numbers in each answer to see the exact source passage it used.
  9. Fix and test again. If the Teller invents something, change one line of the instructions, save the Doc as a new version, paste the new instructions and ask the same question again.
  10. Share it for grading. Select Share and add your instructor’s Maricopa email. Keep access restricted: never “anyone with the link” for a real narrator.
  11. Log it. Add a row to your AI-use log: what you built, what you tested and what you changed.

Starter instructions (replace the brackets):

You are the Teller for [name or “the narrator”]’s story. Start your first answer with: “I am an AI built from an archive of [name]’s interviews and papers.” Answer only from the sources in this notebook, and cite them. Speak as [a narrator who knows this archive / [name], in the first person, as the Signed Agreement allows]. If the sources do not answer a question, say “The archive does not say,” and suggest a question it can answer. Never guess names, dates or feelings. Do not discuss [topics the narrator ruled out in the agreement]. Keep answers under 150 words unless asked for more.

Assessment

Practice Archive and Metadata (10 points, Process Work)

This assignment measures Module Objective 1.1, which supports Course Competency 10.

  1. Choose six items for your Practice Teller: two transcript excerpts, two documents and two images.
  2. Make the folder AVC150_Practice_Lastname with subfolders 01_Interview, 02_Images, 03_Documents and 07_Production. Copy the metadata starter sheet; three rows are filled in as models. Metadata is the record of each item: what it is, who made it, when, where, and what may be done with it.
  3. Fix the machine-draft transcript of excerpt E3 against its audio, and mark each change. (A machine draft is the text the software typed before any person checked it.)
  4. Fill in a metadata row for each item. Mark guessed dates “ca.” (about). Label each old photo “Period photograph,” then the collection name, then “Not the narrator’s family.” Write alt text for two images.

Submit: folder link, metadata sheet, corrected E3, AI-use log row, critique record. AI: Gemini may draft descriptions and alt text; check every name and date. Discord: one metadata row and its image in #practice-archive; three comments.

Grading (10 points): all required parts, complete 3; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication 2; critique: three comments that name a frame, timecode, question or line 1; AI-use log row 1.

Project 1: The Practice Teller (30 points, Projects)

This assignment measures Module Objectives 1.2 and 1.3, which support Course Competencies 6 and 8.

  1. Follow How to Build a Teller. Name the notebook “Practice Teller · Ada Ruiz” plus your name. Load your Practice Archive items and metadata sheet. Title any uncorrected excerpt “machine draft, uncorrected.” Never load the sample consent video.
  2. Write 120 to 200 words of instructions in your own words. Say who the Teller is; that it starts by saying it is an AI; its mode (narrator voice, because the sample agreement says no to first person); what it must never do, including the sample agreement’s limit; and what it says when the archive has no answer.
  3. Ask six questions from the question bank. Rate each answer accurate, partly accurate or fabricated, and note its citations. Fix at least two problems and ask again.
  4. Record a 60-second interview with your Practice Teller (the screen, and your voice asking) that draws out one moment of Ada’s story. Do not change the Teller’s answers. Fix the captions by hand.
  5. Fill in the AI-use statement and credit line. End with two sentences: which question drew out the story, and one thing you will do differently with a real person’s archive.
Project 1 rubric (30 points)
CriterionObjectivePoints
Archive: the Practice Archive items and metadata sheet are loaded, with machine drafts labeled “machine draft, uncorrected”1.24
Instructions: 120 to 200 words in your own words, covering who the Teller is, its AI disclosure, its mode, what it must never do and what it says when the archive has no answer1.24
Testing: six question-bank questions asked, each answer rated accurate, partly accurate or fabricated, with citations noted1.24
Fixes: at least two problems fixed and the questions asked again1.24
Recorded interview: the 60-second interview draws out one moment of Ada’s story and shows a turn in it1.34
Recording quality: clear audio, screen and your voice asking, and the Teller’s answers unchanged1.33
Labels and restriction: period photographs labeled and the sample agreement’s restriction followed1.22
Disclosure: the Teller’s AI disclosure, the AI-use statement and the credit line1.22
Accessibility: captions corrected by hand and alt text on every posted image1.33
Total30

Graded on what you wrote, tested and fixed. Discord: the recording in #project-1-mini; three comments, one on the questions asked.

Interviewing the Demo Teller (10 points, Exercises)

This assignment measures Module Objective 1.4, which supports Course Competency 1.

  • By Wednesday at noon, in #demo-teller, post screenshots of two of the demo Teller’s answers. In 100 to 150 words, use them to explain the difference between a story and a topic. Which of your questions drew out a story rather than a fact?
  • Name one moment when the Teller said it did not know, or should have.
  • By Thursday at noon, comment on three classmates’ posts with the question you would ask next.
  • Accessibility: alt text on the screenshots.

Grading (10 points): post: substance and visual evidence 3; accessibility 1; critique comments 4; vocabulary 1; clarity 1.

Instructor notes
  • Share the demo Teller read-only, with the life history’s catalog link and your content note. Students do not buy Artificial: the course uses Amy Kurzweil’s free video preview and the NPR interview. Showing a few pages from your own copy is optional.
  • Comment on every Interviewing the Demo Teller post by Friday; post a Monday summary of the questions that drew out the strongest stories. Watch for students who treat the demo Teller’s answers as the subject’s own words; point them to the citations.
  • The planted-problems answer key is kept only on the unpublished Instructor Notes: Module 1 page in Canvas.
  • Ask two held-out questions of at least five Practice Tellers; post a Monday summary of the most common invention and the instruction that fixed it. Return Project 1 feedback by the following Thursday with one thing to carry into the real Teller.
  • Watch for uncorrected machine drafts, fabricated dates, one-line instructions, a missing AI disclosure, and fluent answers taken as accurate.

Video: Building the Practice Teller (about 18 minutes)

  • A story versus a topic, with two examples.
  • Artificial and the course: the book’s story in brief and Amy Kurzweil’s video preview (pages from your own copy optional), then a live interview of the demo Teller.
  • Segment 1: metadata, file naming and alt text, and why a machine transcript is only a first draft.
  • Segment 2: writing Teller instructions from the starter, line by line.
  • Walk the How to Build a Teller steps on screen: create a notebook, load and rename sources, set the instructions in the chat settings.
  • Test with three questions, fix one invention, test again.
  • Record a short interview with OBS; show where captions get fixed.
Module 2

The Pitch and Consent

Week 3 · 8 hours

Objectives

  • 2.1 Present a story idea to peers for feedback, and respond to theirs in writing (Course Competency 5)
  • 2.2 Explain how voice, place and culture shape your story and your Teller in a pitch package (Course Competency 2)
  • 2.3 Explain in plain language how AI tools will process a narrator’s material and how the Teller will speak (Course Competency 3)

Overview

The real project begins. You choose whose story your Teller will hold, ask that person informally, and propose the project in a pitch package. You also choose the Teller’s mode. In narrator mode, the Teller knows the archive and speaks about the person. In first-person mode, it speaks as the person, like the grandfather bot in Artificial. First person needs the narrator’s written agreement. Both modes are graded the same, and every Teller says it is an AI.

You also choose one of three story paths. All three are graded the same.

PathWho the Teller speaks asConsent package
Real narrator (main path)The narrator, or a narrator voiceRequired
YourselfYou, in a self-interviewNot needed
Character or iconA fictional character, a brand figure (like Barbie), a place or object, or a historical figure in the public domain, built from public sourcesNot needed. You keep a source list (title, link, license or fair-use note) and a credit line instead.

How to choose: if a real person will share their own story with you, use the real narrator path. If the story is yours, use the yourself path. If you can know the figure only through public sources, use the character or icon path (the character path).

The character path has these rules:

  • Your instructor approves your figure and topic in the Pitch Package, before you build anything.
  • No living real person speaks in the first person. A living real person may only be described by a narrator voice. The Teller never quotes or imitates them.
  • The Teller still opens by saying it is an AI built from an archive of public sources.
  • A brand or trademarked character is unofficial student commentary. Use this credit line: “Unofficial student commentary; [character] is a trademark of [owner].” The finished piece stays Restricted on your portfolio site.
  • The story still needs your own angle. Write a short “Why this figure matters to me” statement, and build your interview questions from your own question about the figure.
  • Heavy topics, such as body image, eating disorders or violence, get a content note at the start of your recording. If a topic is hard for you, GCC Counseling Services can help.
  • Under 18? Self-harm, sexual content and graphic violence are not available as topics. Body image as media critique is allowed with your instructor’s approval. If Gemini blocks your sources or answers, message your instructor. You switch topics or use the narrator or self-interview path, with the same grade.
  • Everything else is the same on every path: the archive, sources loaded into Gemini Notebook, instructions, testing, the error audit, the recorded and edited interview, key art, the case study, and grading and points.

Watch

One captioned instructor video: voice, place, power and consent, with a demonstration of the narrator email and the information sheet.

Read

Practice

Story Circle is this week’s practice. It is graded as an exercise.

Assessment

Story Circle: Whose Story, Which Teller? (10 points, Exercises)

This assignment measures Module Objective 2.1, which supports Course Competency 5.

  • In #story-circle, post three loglines (one-sentence story summaries) for three possible Tellers. Add a quick sketch or phone photo for each. Mark the one you lean toward and the mode you would choose. Add up to 100 words of context.
  • Comment on three classmates’ posts: the first question you would ask their Teller, and which story it could tell best.
  • Accessibility: alt text on each quick study.

Grading (10 points): post: substance and visual evidence 3; accessibility 1; critique comments 4; vocabulary 1; clarity 1.

Pitch Package (10 points, Process Work)

This assignment measures Module Objectives 2.2 and 2.3, which support Course Competencies 2 and 3.

  1. Choose your path from the story paths table. Then choose your narrator, the person whose story it is: a family member, a community member you know, yourself (a self-interview), or a licensed public oral history plus a self-interview. On the character path, choose your figure and your topic.
  2. Real narrator path only. Talk with them informally. Give the one-minute explanation: what a Teller is; a 20- to 30-minute recorded interview, plus any photos or papers they want to share; that, if they agree, Google and Adobe AI tools would transcribe the interview and build a Teller that answers from their words; the two modes and the labeled AI voice; that nothing is uploaded until they sign; and that they can say no or change their mind. Write three or four sentences on how it went. Character path: instead, write a 100- to 150-word “Why this figure matters to me” statement. End it with the one question you most want to ask the figure. Your interview questions grow from that question.
  3. Write a logline (25 words or fewer) and a 150- to 200-word pitch, revised from the Story Circle. Name the Teller’s mode and the moment you hope the interview reaches.
  4. Make a moodboard of 6 to 8 images with sources (yours, your narrator’s with permission, licensed or public domain). Add a 50- to 80-word caption on color, type, light and feeling.
  5. In Canvas only: every person who will appear, one risk and your plan for it, and (real narrator path only) your narrator’s answers about AI, mode and voice. Character path: instead, a starter source list of at least five public sources (title, link, license or fair-use note), your credit line, and a one-line content note if your topic is heavy.

Submit: Canvas record, AI-use log row, critique record. AI: Gemini may offer story starters and tighten the logline and pitch. Discord: logline, pitch and moodboard in #pitch; three comments.

Grading (10 points): all required parts, complete 3; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication 2; critique: three comments that name a frame, timecode, question or line 1; AI-use log row 1.

Instructor notes
  • Prepare the narrator email template, the Project Information Sheet and the Consent Affirmation Google Form (required checkboxes, typed name, date, guardian section for a narrator under 18).
  • Return Pitch Package feedback the next instructional day after the close, approving or redirecting story, narrator and Teller mode. Students may not email a narrator before it.
  • Follow up privately on pitches involving a minor, a recent death, a community-held story or sensitive material.
  • Approve every character-path figure and topic in Pitch Package feedback, before the student builds. Check that no living real person speaks in the first person, that every source is public and on the source list, that brand characters carry the credit line and stay Restricted, and that heavy topics carry a content note. For students under 18: no self-harm, sexual content or graphic violence; body image as media critique only with your approval; if Gemini blocks their sources or answers, they switch topics or move to the narrator or self-interview path with no grade penalty.
  • Model character-path project: a student interviews Talking Barbie about her 6′7″ proportions and the prevalence of eating disorders. The archive holds Barbie’s history and eating-disorder research. The Teller opens with its AI disclosure, the recording opens with a content note, and the credits read “Unofficial student commentary; Barbie is a trademark of Mattel.”

Video: Voice, Power and Consent (about 12 minutes)

  • Voice, place and culture: a narrator’s own words, dialect and languages.
  • Language, image and power: whose story it is, who holds the camera, what a Teller speaking as a person claims.
  • Consent as craft: the two Teller modes and the labeled AI voice.
  • The three story paths, and the character path’s source list and credit line.
  • Fill in the email template and walk the AI section of the Project Information Sheet.
  • Model the one-minute explanation; warn that no narrator is emailed before Pitch Package approval.
Module 3

The Interview

Week 4 · 8 hours

Objectives

  • 3.1 Prepare an interview guide of open, scene-seeking questions (Course Competency 4)
  • 3.2 Apply scene-seeking questions and follow-ups in a rehearsed interview (Course Competency 4)
  • 3.3 Apply sensory detail and your own reference photographs to three field journal pages (a person, a place, a memory), each with a 40 to 60 word caption (Course Competency 4)

Overview

Your interview with the narrator is the main source for your Teller. A Teller can only tell what the archive holds. Questions that ask for scenes, places, objects and exact words give it the most to work with. This week you write your interview guide, send the information sheet, collect the Consent Affirmation, practice, and start your field journal (a sketchbook of the story’s people and places).

Watch

One captioned instructor video: the interview as listening. Optional live Studio Session: an interview clinic. It is recorded, and its day and time are posted in Announcements a week ahead.

Read

Practice

  • Rehearse the video consent script aloud once.

Assessment

Interview Guide and Consent Affirmation (10 points, Process Work)

This assignment measures Module Objective 3.1, which supports Course Competency 4.

  1. Ask Gemini to draft 20 questions. Cut them to 10 to 12 open questions that ask for scenes, from easy to deeper, each with one follow-up. End with “Is there anything I didn’t ask that I should have?” Ask nothing about immigration or legal status, legal cases or health.
  2. Send your narrator a 150- to 200-word email from the template. Attach the full Project Information Sheet (remove nothing) and the OHA participants page.
  3. Offer a 15-minute walk-through of the information sheet. Read the AI section, the Teller modes and the voice option together. Note their questions.
  4. Collect the signed Consent Affirmation. A guardian co-signs for a narrator under 18. (If you are under 18, see Consent and Privacy.) Schedule a 20- to 30-minute interview inside the interview window.

Character path: write the guide as questions for your Teller, built from the question in your “Why this figure matters to me” statement. The rule against health questions protects real narrators; you may ask about a public topic, such as body image, that your instructor approved at the pitch. Skip steps 2 to 4. Instead, grow your source list to at least 8 public sources. Submit the guide and source list in place of the email, notes and Consent Affirmation.

Submit (Canvas only): guide, email, walk-through notes, Consent Affirmation, interview day, AI-use log row, critique record. AI: Gemini drafts questions and may tighten the email; consent documents are never rewritten by AI. Discord: the guide only in #interview-guide; three comments, each suggesting a follow-up.

Grading (10 points): all required parts, complete 3; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication 2; critique: three comments that name a frame, timecode, question or line 1; AI-use log row 1.

Interview Rehearsal (10 points, Exercises)

This assignment measures Module Objective 3.2, which supports Course Competency 4.

  • In two sentences, describe a narrator for Gemini to play (no private details). Practice for about 10 minutes from your guide, out loud with Gemini Live or by typing. If Gemini Live is blocked on your account, type, or practice with a classmate or family member.
  • Submit in Canvas: the chat share link (or your notes), three changes to your guide, and your best follow-up question.

Grading (10 points): rehearsal and changes 4; accessibility 1; craft of the follow-up 2; writing 2; AI-use log row 1.

Visual Field Journal (10 points, Exercises)

This assignment measures Module Objective 3.3, which supports Course Competency 4.

  • Make three mostly visual pages (a person, a place, a memory) from sketches, collage and your own photos. The place page uses at least three photos you took. Keep these photos; you reuse them in The Interview and Video Consent.
  • Write a 40- to 60-word caption on each page about what you see, hear, smell or feel. Gemini may suggest prompts. No AI-made textures or images.
  • Submit the pages in Canvas, with alt text on each.

Grading (10 points): three pages and captions 4; alt text 1; visual craft 2; caption writing 2; AI-use log row 1.

Instructor notes
  • Run the Studio Session (30 minutes, recorded): interview clinic with a practice of the consent script.
  • Return Interview Guide feedback by Friday, confirming the Consent Affirmation is on file. That opens the interview window, which runs through Wednesday of Week 5; tell students the window in the feedback.
  • Watch for emails sent before Pitch Package feedback, information sheets with the AI section removed, yes-or-no questions, and questions on immigration or legal status, legal cases or health (not allowed).

Video: The Interview as Listening (about 15 minutes)

  • Questions that seek scenes, places, objects and exact words; easy to deeper.
  • The slate, room tone and reference photographs.
  • The video consent: framing, reading the script, stopping if a narrator hesitates, never uploading the file.
Module 4

Building the Archive

Week 5 · 8 hours

Objectives

  • 4.1 Record a consented interview with clean, usable audio, and gather visual reference from the story’s places (Course Competency 4)
  • 4.2 Organize a real story archive with a signed agreement, consistent names and folders, accurate metadata and alt text (Course Competency 10)
  • 4.3 Correct an AI transcript so that it preserves your narrator’s own words (Course Competency 4)

Overview

This week you record the interview and build the real archive. The interview starts with the video consent. Afterward your narrator signs the Signed Agreement. It says what you may do with each item, which mode the Teller may use, and whether a labeled AI voice may read its answers. Nothing goes into an AI tool until the agreement is signed with item 4 marked yes.

Watch

One captioned instructor video: from the Practice Archive to a real one, with a short demonstration of scanning, speech-to-text, redaction and the archive folder template.

Read

  • USC Shoah Foundation, Dimensions in Testimony (optional: the FAQ), and 10 minutes with an interactive testimony on IWitness. Every answer is the person’s real recorded words, given with consent.

Assessment

The Interview and Video Consent (10 points, Process Work)

This assignment measures Module Objective 4.1, which supports Course Competency 4.

  1. Check that the Consent Affirmation is on file.
  2. Record the video consent first. Say your slate (your name, the date and the place), then your narrator reads the consent script on camera, or answers “Yes, I agree” to each sentence. A guardian appears for a narrator under 18. If your narrator hesitates, stop and ask. Save the file as YYYY-MM-DD_consent_lastname.mp4 in 06_Consent, with a backup. Never upload it to any AI tool or Discord.
  3. Interview for 20 to 30 minutes. Record 30 seconds of room tone (the room with no one talking).
  4. End with “Is there anything you said that you would rather I not use?” Back up the recording in two places the same day.
  5. Within 24 hours, write a 100-word shoot log (notes on how the interview went) and give your narrator the Signed Agreement to read.

Character path: you have no consent video and no narrator interview. Instead, record a 5- to 10-minute audio reflection that answers three questions from your guide, with 30 seconds of room tone. Back it up the same day and write the shoot log. For the reference photos, shoot places or objects tied to your figure.

Submit (Canvas only): consent video, interview, room tone, shoot log, agreement status, AI-use log row, critique record. AI: none yet. Discord: three reference photos of the location in #reference (field journal photos are fine; no people without permission); three comments, one on light or framing.

Grading (10 points): all required parts, complete 3; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication 2; critique: three comments that name a frame, timecode, question or line 1; AI-use log row 1.

Signed Agreement, Transcript and Archive Inventory (10 points, Process Work; no critique)

This assignment measures Module Objectives 4.2 and 4.3, which support Course Competencies 10 and 4.

  1. Go through the Signed Agreement with your narrator item by item. Do not steer any answer. Collect the signatures. List what it allows and limits, including the Teller’s mode and voice.
  2. After it is signed, make a first-draft transcript (Premiere Pro speech to text, Gemini Notebook, or by hand). Before any more AI use, cut anything about immigration or legal status, legal cases or health; anything the narrator asked you not to use; and anything item 11 limits.
  3. Fix the 6 minutes you are most likely to use. Label the rest “machine draft, uncorrected.”
  4. Start from the archive folder template in Drive. Folders: 01_Interview, 02_Images, 03_Documents, 04_Audio, 05_Journal, 06_Consent (shared with your instructor only) and 07_Production. Add at least 8 items named YYYY-MM-DD_subject_description, scanned or photographed at high quality.
  5. Describe every item in the metadata sheet, including which agreement items cover it. You write alt text for the images in Sources and First Instructions.

Character path: in place of the Signed Agreement, finish your source list (title, link, license or fair-use note for every item) and add your credit line. Correct 6 minutes from your reflection or a public audio or video source. Keep the source list in 06_Consent, and name each item’s source in the metadata sheet in place of agreement items.

Submit (Canvas only): signed agreement, corrected excerpt, folder link, metadata sheet, AI-use log row. AI: only for items the agreement clears.

Grading (10 points): all required parts, complete 4; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication 2; AI-use log row 1.

Instructor notes
  • Prepare the Signed Agreement (with its schedule of materials), the shoot log and the archive folder template.
  • Check every agreement: blank items are no; item 4 governs AI; items 5, 6 and Part D govern the mode; item 13 governs an AI voice; item 11 limits carry into the Teller.
  • A student who reports a cancellation by Wednesday may submit The Interview and Video Consent the following Monday at noon with no deduction. Return Signed Agreement, Transcript and Archive Inventory feedback by Tuesday, confirming uploads may begin.
  • Watch for uploads before the agreement, the consent video uploaded anywhere, and interview audio posted to Discord.

Video: From Practice to Real Archive (about 12 minutes)

  • What changes with a real narrator: privacy, consent, the upload rule.
  • The Signed Agreement item by item: mode items 5 and 6, Part D, voice item 13, item 11 limits.
  • Scan or photograph an item at high quality; name it with the date pattern.
  • Speech to text only after the agreement; cut restricted material before more AI use.
  • Fill one metadata row and place files in the folder template.
Module 5

Your Teller

Week 6 · 8 hours

Objectives

  • 5.1 Select, title and load archive sources into Gemini Notebook as the agreement allows (Course Competency 10)
  • 5.2 Write first instructions that set the Teller’s role, mode, AI disclosure and limits (Course Competency 4)
  • 5.3 Test the Teller against its archive and rate each answer accurate, partly accurate or fabricated, with the source involved (Course Competency 6)

Overview

Your Teller is the first working version of your storyteller. It answers only from the sources you load, with citations, and follows the instructions you write in the notebook’s chat settings. Version 1 will make mistakes. This week you find the first ones.

Watch

One captioned instructor video: building Your Teller, with a guided lab from the Practice Teller to the real Teller. Optional live Studio Session: Teller troubleshooting. It is recorded, and its day and time are posted in Announcements a week ahead.

Read

Practice

The First Test is this week’s practice test.

Building steps: follow How to Build a Teller in Gemini Notebook in Module 1, now with your real, cleared archive.

Assessment

Sources and First Instructions (10 points, Process Work)

This assignment measures Module Objectives 5.1 and 5.2, which support Course Competencies 10 and 4.

  1. Make a Gemini Notebook. Load at least 8 items the agreement clears for AI: the corrected excerpt, captioned images with their metadata, your field journal pages and any approved documents. Title each source so a citation names it clearly. Write alt text for five images.
  2. In a Google Doc, write first instructions of 200 to 300 words: who the Teller is; that its first answer says it is an AI built from an archive; its mode and the agreement item that allows it (narrator mode, item 5; first person, item 6 or Part D); every item 11 limit; and what it says when the archive has no answer.
  3. Fill in the Teller Design Form: sources, mode and three limits.

Character path: load at least 8 items from your source list. In place of an agreement item, your instructions name the path and the figure, and the first answer says it is an AI built from an archive of public sources.

Submit: share link (instructor only), instructions as a Google Doc with version history, design form, alt text, AI-use log row, critique record. Discord: your instructions only, with private details removed, in #instructions; three comments, one on a limit that is missing.

Grading (10 points): all required parts, complete 3; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication 2; critique: three comments that name a frame, timecode, question or line 1; AI-use log row 1.

First Test (10 points, Process Work; no critique)

This assignment measures Module Objective 5.3, which supports Course Competency 6.

  1. Ask 15 questions: 8 the archive can answer, 4 it cannot, and 3 that ask for a scene.
  2. Rate each answer accurate, partly accurate or fabricated, and note whether it cited a source.
  3. Record 90 seconds of the Teller answering two questions, with corrected captions.

Submit (Canvas only): test log, recording, AI-use log row.

Grading (10 points): all required parts, complete 4; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication 2; AI-use log row 1.

Instructor notes
  • Prepare the Teller Design Form and the source checklist.
  • Run the Studio Session (one hour, recorded): Teller troubleshooting.
  • Ask three held-out questions of each Teller while grading the First Test. Check each Teller’s mode against the agreement; no item 11 material in any Teller.

Video: Building Your Teller (about 12 minutes)

  • Grounding: why a Teller answers from sources and still invents where the archive has gaps.
  • Choosing and titling sources so citations make sense.
  • Writing the first instructions with mode, AI disclosure and limits.
  • Repeat the How to Build a Teller steps with a cleared archive; load only items the agreement allows.
  • Run the 15-question first test and rate three answers on screen.
Module 6

Voice and Persona

Week 7 · 8 hours

Objectives

  • 6.1 Write a voice guide that defines how your Teller speaks, grounded in the narrator’s own words (Course Competency 5)
  • 6.2 Revise the Teller’s instructions so that its answers match the voice guide (Course Competency 6)
  • 6.3 Critique peers’ voice guides in writing (Course Competency 5)

Overview

A voice guide is a short document that tells a writer, or a machine, how a character speaks. Yours sets how the Teller sounds: its mode, its words and rhythm, phrases it borrows from the narrator, what it never says, and how it admits what it does not know. The voice guide and instructions are the main writing in this course.

Watch

One captioned instructor video: voice and persona, walking through the model voice guide.

Read

Practice

  • Pull ten phrases from your corrected transcript that sound most like your narrator.

Assessment

Voice Guide (10 points, Process Work)

This assignment measures Module Objective 6.1, which supports Course Competency 5.

  1. Write a 300- to 450-word voice guide in a Google Doc: the mode and why; three to five voice traits, each with a quote from the transcript; words and topics to avoid; how the Teller says it is an AI; how it answers a question the archive cannot answer; and two sample answers in the voice.
  2. In 50 to 80 words, explain how voice, place and culture shape the guide.

Character path: take the voice-trait quotes from your sources.

Submit: voice guide with version history, AI-use log row, critique record. AI: Gemini may give feedback on clarity; you write the guide. Discord: your Voice Guide Workshop post.

Grading (10 points): all required parts, complete 3; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication 2; critique: three comments that name a frame, timecode, question or line 1; AI-use log row 1.

Voice Guide Workshop (10 points, Exercises)

This assignment measures Module Objective 6.3, which supports Course Competency 5.

  • Post your voice guide in #voice-guide, with private details removed.
  • Review three classmates’ guides. Comment on one trait that is clear, and on one sample answer that does not match the guide. Point to the line.

Grading (10 points): post: substance and visual evidence 3; accessibility 1; critique comments 4; vocabulary 1; clarity 1.

Instructions v2 and Voice Test (10 points, Process Work)

This assignment measures Module Objective 6.2, which supports Course Competency 6.

  1. Revise the Teller’s instructions using your voice guide and Voice Guide Workshop comments.
  2. Ask five questions. Compare each answer with the guide and mark matches and misses.
  3. Write a 100- to 150-word revision note: what you changed in the instructions, and what the Teller still gets wrong about the voice.

Submit: instructions v2, voice test, revision note, AI-use log row, critique record. Discord: one answer from Your Teller and the same question answered by the Revised Teller, in #instructions-v2; three comments.

Grading (10 points): all required parts, complete 3; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication 2; critique: three comments that name a frame, timecode, question or line 1; AI-use log row 1.

Instructor notes
  • Prepare the voice guide template and a model voice guide for the demo Teller.
  • Comment on every voice guide in the Voice Guide Workshop. Link GCC writing tutoring. Watch for guides that list adjectives instead of showing sample answers, and first-person Tellers without item 6 or Part D.

Video: Voice and Persona (about 15 minutes)

  • Voice on the page: word choice, sentence rhythm, the narrator’s own phrases and languages.
  • First person and narrator mode, and what each one claims about the person.
  • Walk the model voice guide; turn one trait into an instruction a machine can follow.
Module 7

Testing the Teller

Week 8 · 8 hours

Objectives

  • 7.1 Write held-out questions that test a Teller where its archive is thin (Course Competency 4)
  • 7.2 Audit a Teller’s errors, classify them, and revise its sources and instructions (Course Competency 6)
  • 7.3 Describe how your Teller’s errors resemble or differ from the grandfather bot’s in Artificial, and what that means for who speaks for a person (Course Competency 3)

Overview

An error audit is a planned test of what a Teller gets wrong. Held-out questions are questions you write before you see any answers. They aim at gaps, conflicts and feelings the archive may not hold. You log every error, find its cause in the sources or instructions, fix it, and ask again. Kurzweil does the same when she weighs what the grandfather bot gets right and what it leaves out, such as his voice and his music.

Watch

One captioned instructor video: the error audit.

Read

Practice

  • Mid-semester survey (ungraded)

Assessment

Held-Out Questions (10 points, Process Work)

This assignment measures Module Objective 7.1, which supports Course Competency 4.

  1. Write 15 held-out questions before you ask any: at least 4 about gaps, 3 about conflicts between sources, 3 about feelings or reasons, and 2 that push the Teller past its limits.
  2. For five questions, add one sentence about something your narrator said or showed you that the archive does not hold. Use your memory and shoot log, not the notebook. Character path: use something you know about the figure that your archive does not hold.
  3. Trade five questions with a classmate and add theirs to your set.

Submit: question set, AI-use log row, critique record. Discord: your five traded questions in #held-out; three comments.

Grading (10 points): all required parts, complete 3; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication 2; critique: three comments that name a frame, timecode, question or line 1; AI-use log row 1.

Error Audit and Revision (10 points, Process Work; no critique)

This assignment measures Module Objective 7.2, which supports Course Competency 6.

  1. Ask all 20 questions. Log each in the error audit log: the answer, its rating, the error type and the source involved.
  2. Fix at least five errors by changing sources (a clearer title, a correction note, a removed machine draft) or instructions. Test each one again.
  3. Write a 150- to 200-word audit summary: the most common error, the fix that worked, and one error you could not fix, and why.

Submit (Canvas only): audit log, summary, revised instructions, AI-use log row.

Grading (10 points): all required parts, complete 4; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication 2; AI-use log row 1.

The Grandfather Bot and Your Teller (10 points, Exercises)

This assignment measures Module Objective 7.3, which supports Course Competency 3.

  • In #grandfather-bot, post one moment from Amy Kurzweil’s video preview or the NPR interview (a screenshot, or a short quote from the transcript) and one error from your audit, with names removed. In 100 to 200 words, answer: how is your Teller’s mistake like or unlike the grandfather bot’s? Who should decide what a storyteller may say about a person?
  • Write three comments using I noticed, I wondered, What if. Add alt text to any screenshot.

Grading (10 points): post: substance and visual evidence 3; accessibility 1; critique comments 4; vocabulary 1; clarity 1.

Instructor notes
  • Prepare the error audit log template (question, answer, rating, error type, source, fix, retest).
  • Ask five held-out questions of each Teller while grading Error Audit and Revision. Write each student a short mid-semester progress note.

Video: The Error Audit (about 12 minutes)

  • Segment 1: error types: invention, misattribution, wrong date or place, a smoothed-over conflict, a voice the narrator would not use, a claimed feeling the archive does not hold.
  • Segment 2: what Kurzweil says the grandfather bot gets right and leaves out, from the NPR interview.
  • Log one error from the demo Teller, fix it in the sources, and retest on screen.
Module 8

The Conversation Map

Week 9 · 8 hours

Objectives

  • 8.1 Identify the dramatic question and the turn your interview should reach (Course Competency 4)
  • 8.2 Use basic design principles to lay out and produce a conversation map that storyboards the path of questions, likely answers, branches, visuals and timing (Course Competency 7)
  • 8.3 Critique classmates’ conversation maps in writing (Course Competency 5)

Overview

The conversation map is the storyboard (a plan drawn as a series of frames) for your recorded interview. Each frame is one question: what you ask, the answer you expect and its source, the branch if the Teller answers differently, the visual on screen, and the planned time. A good map builds toward one moment and reaches a turn.

Watch

One captioned instructor video: the conversation map, with a demonstration from thumbnails to a finished map.

Read

Practice

  • Ask your Teller for every passage about your central moment, with citations. Note which questions reach it.

Assessment

Dramatic Question and Map Thumbnails (10 points, Process Work)

This assignment measures Module Objective 8.1, which supports Course Competency 4.

  1. In one sentence each, write your dramatic question (the one question the story makes the viewer want answered) and the turn (the moment the answer changes what came before).
  2. Draw 8 to 12 small sketches (thumbnails), by hand or on a tablet, for two different question paths.
  3. Choose one path and explain why in two or three sentences.

Submit: dramatic question, thumbnails, choice, AI-use log row, critique record. AI: Gemini may suggest other orders for your questions; you choose the path. Discord: #map-thumbnails; three comments, one on where the turn falls.

Grading (10 points): all required parts, complete 3; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication 2; critique: three comments that name a frame, timecode, question or line 1; AI-use log row 1.

Conversation Map (10 points, Process Work)

This assignment measures Module Objective 8.2, which supports Course Competency 7.

  1. Lay out 10 to 14 frames in the template. Each frame has: the question; the expected answer and its source; the branch; the on-screen visual (an archive item, or a visual you will make in Module 9); sound; and time. The total is 3 to 5 minutes.
  2. Use the same visual key (colors or shapes) for questions, answers, branches and visuals, with a clear reading order.

Submit: map as a tagged PDF with alt text, AI-use log row, critique record. AI: none for layout; every frame is yours. Discord: your Conversation Map Critique post.

Grading (10 points): all required parts, complete 3; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication 2; critique: three comments that name a frame, timecode, question or line 1; AI-use log row 1.

Conversation Map Critique (10 points, Exercises)

This assignment measures Module Objective 8.3, which supports Course Competency 5.

  • Post your conversation map in #conversation-map.
  • Review three classmates’ maps. Comment on the layout (name the frame number) and on whether the path reaches the turn.

Grading (10 points): post: substance and visual evidence 3; accessibility 1; critique comments 4; vocabulary 1; clarity 1.

Instructor notes
  • Prepare the conversation map template (InDesign, Illustrator and Google Slides) and a model map for the demo Teller.
  • Comment on every Dramatic Question and Map Thumbnails post before Friday. Review maps in the Conversation Map Critique and post a Monday summary on layout.
  • Watch for maps that are lists of questions with no branches, and paths with no turn.

Video: The Conversation Map (about 12 minutes)

  • The dramatic question and the turn, shown in the demo Teller interview.
  • Question paths: chronological, circular, braided, and kishōtenketsu (four parts that turn on a new fact, not a conflict).
  • Layout with design principles: hierarchy, alignment, contrast, flow, a consistent visual key.
  • Sketch two paths as thumbnails, choose one, and build it in the template.
  • Add a branch for an unexpected answer; check the total time.
Module 9

Visual Identity

Week 10 · 8 hours

Objectives

  • 9.1 Use Photoshop or Illustrator to build a Teller portrait from your own drawing, photography or type that does not imitate a real person’s likeness (Course Competency 8)
  • 9.2 Prepare illustrated archive cards at video resolution and label each change as “restoring” or “inventing” (Course Competency 8)
  • 9.3 Describe how a labeled AI image and a restored archival photograph differ in what each claims, using Content Credentials (Course Competency 3)

Overview

Your recorded interview needs pictures. This week you make the Teller’s visual identity: its portrait and the archive cards (archive items, cropped and captioned) that appear over its answers. The key art for the project comes in Module 11. You make every visual yourself from archive material and your own drawing and photos. No image is made by AI, and the Teller’s face never looks like the narrator.

Watch

One captioned instructor video: visual identity, with a demonstration of the portrait, archive cards, repair and labeling, and Content Credentials.

Read

Practice

  • Install Photoshop and Premiere Pro from Creative Cloud in one sitting (add Illustrator if you will draw in vector). Open each app once.

Assessment

Teller Portrait and Archive Cards (10 points, Process Work)

This assignment measures Module Objectives 9.1, 9.2 and 9.3, which support Course Competencies 8 and 3.

  1. Design the Teller’s portrait (square, 1080 x 1080 pixels) from your own drawing, collage, photos or type. Write 50 to 80 words on how it fits the voice guide.
  2. Make five or six archive cards at 1920 x 1080 pixels from items on your conversation map. Give each a caption and credit line.
  3. Repair at least one photo with Content-Aware Fill or the Spot Healing Brush. Log each change as restoring (fixing damage) or inventing (adding something new).
  4. Check the Content Credentials of one labeled AI image from your instructor’s set. In two or three sentences in your asset log, explain how it differs from your restored photo in what each one claims.

Character path: make your own version of the figure for the portrait. Do not copy official art, logos or packaging.

Submit: portrait, cards, asset log, AI-use log row, critique record. AI: repair tools only; nothing generated. Discord: the portrait and two cards (as your agreement allows) in #visual-identity; three comments, one on composition.

Grading (10 points): all required parts, complete 3; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication, including the Content Credentials note 2; critique: three comments that name a frame, timecode, question or line 1; AI-use log row 1.

Instructor notes
  • Prepare templates: Teller portrait (square) and archive card (16:9 with a caption area), and a small set of labeled AI images with Content Credentials for the Teller Portrait and Archive Cards comparison.
  • Post the McCloud e-reserve link before the module opens.
  • Comment on every Teller Portrait and Archive Cards post before Friday. Watch for portraits traced from a narrator’s photograph and images taken from search results.

Video: Visual Identity (about 12 minutes)

  • A face for the Teller that never looks like a real person: drawn, collaged, typographic or symbolic.
  • Archive cards: an archive item cropped and captioned at 1920 x 1080.
  • Restoring versus inventing: when a repair becomes an invention.
  • Build a portrait and one archive card from the templates.
  • Repair a photo with Content-Aware Fill and the Spot Healing Brush; log each change.
  • Open a labeled AI image’s Content Credentials and read what it claims.
Module 10

Voice and Peer Interviews

Week 11 · 8 hours

Objectives

  • 10.1 Record three Teller answers in the chosen voice with Audition or Adobe Podcast, labeled accurately as AI where it applies (Course Competency 8)
  • 10.2 Interview a classmate’s Teller and give written feedback on what it draws out and what it gets wrong (Course Competency 5)
  • 10.3 Revise your Teller from peer interviews into Revised Teller (Course Competency 6)

Overview

Your recorded interview needs a voice for the Teller’s answers. You may read them yourself or show them as on-screen text. If the agreement allows it, you may use a synthetic voice (an AI voice) from Gemini Notebook’s audio tools, labeled as AI on screen and in the credits. No voice is made to sound like the narrator or any real person. This week classmates also interview your Teller, and you revise it into Revised Teller.

Watch

One captioned instructor video: the Teller’s voice. Optional live Studio Session: peer interviews in pairs. It is recorded, and its day and time are posted in Announcements a week ahead.

Read

Practice

The Voice Test is this week’s voice practice.

Assessment

Voice Test (10 points, Process Work)

This assignment measures Module Objective 10.1, which supports Course Competency 8.

  1. Make three answers in your chosen voice: your own reading, on-screen text, or a labeled AI voice (only if item 13 is yes). Character path: a labeled AI voice needs no agreement, but it never sounds like an actor who voices the character.
  2. Clean the audio with Enhance Speech if needed. Write the on-screen label and credit line.
  3. In 80 to 120 words, explain why this voice fits the voice guide.

Submit: three captioned clips, label and credit line, rationale, AI-use log row, critique record. Discord: one clip in #voice-test; three comments.

Grading (10 points): all required parts, complete 3; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication 2; critique: three comments that name a frame, timecode, question or line 1; AI-use log row 1.

Peer Interviews (10 points, Exercises)

This assignment measures Module Objective 10.2, which supports Course Competency 5.

  • Interview two classmates’ Tellers for five minutes each, live in the Studio Session or with a shared notebook. Use three questions from their conversation map and two of your own.
  • In #peer-interviews, post for each Teller: the best answer you drew out, one error or claim that goes too far, and one fix. Use I noticed, I wondered, What if.

Grading (10 points): post: substance and visual evidence 3; accessibility 1; critique comments 4; vocabulary 1; clarity 1.

Revised Teller (10 points, Process Work; no critique)

This assignment measures Module Objective 10.3, which supports Course Competency 6.

  1. Revise sources and instructions using the peer interviews and your audit. Add each fix to the error audit log and test again.
  2. Run your full conversation map once. Mark where the answers changed the path.

Submit (Canvas only): updated audit log, instructions v3, marked map, AI-use log row.

Grading (10 points): all required parts, complete 4; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication 2; AI-use log row 1.

Instructor notes
  • Run the Studio Session (45 minutes, recorded): live peer interviews in pairs.
  • Check item 13 before any AI voice is used. Tellers about someone who has died are interviewed only by classmates who opt in. A Teller is shared only where item 2 allows class sharing; otherwise the student runs the questions and shares the recording.

Video: The Teller’s Voice (about 12 minutes)

  • Segment 1: the three voice choices (your reading, on-screen text, a labeled AI voice from Notebook’s audio tools); never a voice made to sound like the narrator.
  • Segment 2: how to interview someone else’s Teller: map questions, your own questions, noting an overreach.
  • Clean one clip with Enhance Speech and write the label and credit line.
Module 11

Recording the Interview

Week 12 · 8 hours

Objectives

  • 11.1 Set up screen and audio capture for a clean recording (Course Competency 8)
  • 11.2 Record a complete interview with your Teller that follows the conversation map and reaches the turn (Course Competency 9)
  • 11.3 Design key art with a clear type hierarchy and a tagline (Course Competency 9)

Overview

This week you record the final interview with your Teller. Follow your conversation map, listen to each answer, and follow up when the Teller opens something new. Never ask a question again to get a better answer, and never change an answer. The recording shows what the Teller really said. Aim for 10 to 15 minutes of raw recording, which you will edit down to 3 to 5. You also design the key art: a poster-style image for the project.

Watch

One captioned instructor video: recording the interview, with a key art segment. Optional live Studio Session: recording setup. It is recorded, and its day and time are posted in Announcements a week ahead.

Read

Practice

The Recording Plan and Test is this week’s practice recording.

Assessment

Recording Plan and Test (10 points, Process Work)

This assignment measures Module Objective 11.1, which supports Course Competency 8.

  1. Finish the map you will record from, with any Revised Teller changes.
  2. Fill in the recording checklist. Record a two-minute test: screen at 1920 x 1080, your voice on its own track, and the Teller’s voice or text clear.

Submit: final map, checklist, test clip, AI-use log row, critique record. Discord: 30 seconds of the test in #recording-test; three comments, one on audio.

Grading (10 points): all required parts, complete 3; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication 2; critique: three comments that name a frame, timecode, question or line 1; AI-use log row 1.

The Recorded Interview (10 points, Process Work; no critique)

This assignment measures Module Objective 11.2, which supports Course Competency 9.

  1. Record the whole interview from your map, 10 to 15 minutes, with no retakes. Character path: if your topic is heavy, open with your content note.
  2. Log the recording: each question, its timecode (the time it appears in the recording), and whether you used the answer, used part of it, or cut it.
  3. Save the recording and its log in 07_Production, with a backup the same day.

Submit (Canvas only): recording link, recording log, AI-use log row.

Grading (10 points): all required parts, complete 4; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication 2; AI-use log row 1.

Key Art (10 points, Process Work)

This assignment measures Module Objective 11.3, which supports Course Competency 9.

  1. Design key art (2:3 or 4:5) from the template, using the Teller’s portrait and archive material. Include the title, a tagline of 10 words or fewer, and a credit block (“A Teller by…,” the narrator credit as the agreement allows, and an AI line). Character path: use your credit line in place of the narrator credit.
  2. Design a matching 16:9 title card for the recording.
  3. Check type contrast with the WebAIM Contrast Checker.

Deliverable options: if you chose the story object or the 360 or VR presentation for the Final Project, submit its design (the cut file and a photographed test piece, or the scene layout) in place of the key art PNG, with alt text. Keep the title, tagline and credit block in the design. The title card is still required, and the grading is the same.

Submit: key art and title card PNGs with alt text, AI-use log row, critique record. Discord: #key-art; three comments, one on type hierarchy and one on the tagline.

Grading (10 points): all required parts, complete 3; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication 2; critique: three comments that name a frame, timecode, question or line 1; AI-use log row 1.

Instructor notes
  • Prepare the recording checklist (screen resolution, notifications off, a clean browser window, microphone level, file naming) and the key art template (2:3 and 4:5 with safe areas).
  • Run the Studio Session (45 minutes, recorded): recording setup for each computer. Confirm every student has a computer that runs Premiere Pro, a loaned device, or campus lab time.
  • Watch for retaken answers, private details visible on screen, microphones peaking, and key art with more than two typefaces.

Video: Recording the Interview (about 15 minutes)

  • Segment 1: interviewing on the record: follow the map, listen, follow up, never retake an answer to get a better one.
  • Segment 2: screen and audio capture in OBS with a separate voice track; run the recording checklist.
  • Key art: build one from the template with a title, tagline and credit block; check contrast.
Module 12

Editing the Story

Week 13 · 8 hours

Objectives

  • 12.1 Edit the recorded interview, archive cards, your visuals and sound into a timed 3 to 5 minute sequence in Premiere Pro (Course Competency 9)
  • 12.2 Cut an interview without changing the meaning of any answer, and mark every internal cut (Course Competency 6)
  • 12.3 Present a rough cut for peer review and request your narrator’s review in a professional email (Course Competency 11)

Overview

In the edit, the recorded interview becomes the story. A paper edit is your written plan for the cut, made from the recording log before you open the editor. A rough cut has every part in order and roughly timed: your questions, the Teller’s answers, archive cards, your visuals and sound. The rule: you may shorten the conversation, but never change what the Teller said, and viewers can always see where a cut is.

Watch

One captioned instructor video: editing the interview, with a demonstration from paper edit to rough cut in Premiere Pro.

Read

Practice

  • Open the Premiere Pro project template. (You installed Premiere Pro in Module 9.)

Assessment

Paper Edit and Rough Cut (10 points, Process Work)

This assignment measures Module Objectives 12.1 and 12.2, which support Course Competencies 9 and 6.

  1. Write the paper edit from your recording log: the questions and answers you will keep, in order, with timecodes and the visual for each.
  2. Cut a 3- to 5-minute rough cut in Premiere Pro: the screen recording; archive cards and your visuals over the answers; the title card; room tone and sound. Mark every cut inside an answer.
  3. Make captions with Speech to Text. Fix names and terms by hand.

Submit: paper edit, rough cut link, AI-use log row, critique record. AI: text-based editing, automatic captions and Enhance Speech are allowed and logged; you make every edit decision. Discord: post the rough cut as an unlisted link in #rough-cut if your agreement allows class sharing (on the character path, you may post it); if not, post two frames from the cut with notes. Three comments with timecodes, one on whether the turn lands.

Grading (10 points): all required parts, complete 3; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication 2; critique: three comments that name a frame, timecode, question or line 1; AI-use log row 1.

Narrator Review (10 points, Process Work; no critique)

This assignment measures Module Objective 12.3, which supports Course Competency 11.

  1. By Sunday at noon, send your narrator the rough cut as it is (you revise it in Final Cut) with the review form.
  2. Write a 100- to 150-word email: what you are sending, what feedback you need, a reply date of Wednesday, and this line: “You may still ask for changes or withdraw any item of our agreement.”

Character path: send the rough cut and review form to one reviewer you choose, such as a friend, family member or classmate. In the email, ask them to check one claim against your source list, and leave out the agreement line. Use their response in Final Cut.

Submit (Canvas only): a copy of the email and review form, AI-use log row.

Grading (10 points): all required parts, complete 4; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication 2; AI-use log row 1.

Instructor notes
  • Prepare the Premiere Pro project template (16:9 sequence, tracks labeled for screen, voice, Teller voice, archive cards and sound), the narrator review form and the review email template.
  • Screen every rough cut and record individual feedback by Wednesday of Week 14. Grade on structure, timing and mix, not polish.
  • Every narrator receives the rough cut with the line “You may still ask for changes or withdraw any item of our agreement.” Rough cuts are posted only where the agreement allows class sharing.

Video: Editing the Interview (about 12 minutes)

  • Segment 1: the paper edit from the recording log.
  • Segment 2: cutting without changing what was said: cut between answers; mark any cut inside an answer with a visual break.
  • Segment 3: archive cards and visuals over the answers, sound, room tone and timing.
  • Open the template, lay in the screen recording and voice track, add cards and the title card.
  • Use text-based editing and Speech to Text captions; fix names by hand.
Module 13

Finishing

Week 14 · 8 hours

Objectives

  • 13.1 Design titles and end credits that are legible and credit sources, including AI use (Course Competency 9)
  • 13.2 Finish and export a captioned recorded story that meets accessibility requirements and reflects the narrator’s review (Course Competency 6)
  • 13.3 Archive the story, the Teller and its sources on relevant technology (Course Competency 10)

Overview

This week you finish the recorded interview and package everything behind it. The archive package saves the narrator’s materials, the Teller’s sources and instructions, the audit log and the finished recording, so the story lasts longer than the tools that made it.

Watch

One captioned instructor video: finishing and archiving, with a demonstration of titles, captions, export and the archive package, and how to present your work. Your own rough cut feedback video arrives in Canvas on Wednesday.

Read

Assessment

Final Cut: Titles, Captions and Credits (10 points, Process Work)

This assignment measures Module Objectives 13.1 and 13.2, which support Course Competencies 9 and 6.

  1. Revise the rough cut using critique comments, instructor feedback and your narrator’s response. Record the narrator’s response on the review form.
  2. Finish the titles and end credits: the Teller’s AI label, any AI voice label, image and sound credits, and the AI credit line. Check contrast with the WebAIM Contrast Checker.
  3. Fix every caption by hand and export a caption file (SRT or VTT). Make sure anything important on screen is also spoken, or described in a transcript.
  4. Export the MP4 viewing master (the final video file) and upload an unlisted copy.

Submit: unlisted link, caption file, narrator review form, AI-use log row, critique record. Discord: the title sequence and a 30-second captioned section in #final-cut; three comments, one on type and one on caption readability.

Grading (10 points): all required parts, complete 3; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication 2; critique: three comments that name a frame, timecode, question or line 1; AI-use log row 1.

The Archive Package (10 points, Process Work; no critique)

This assignment measures Module Objective 13.3, which supports Course Competency 10.

Use the archive package checklist template in Drive.

  1. Long-lasting copies: WAV for audio, TIFF or PNG for images, PDF or plain text for documents and transcripts.
  2. The Teller’s record: source list, instructions v3, voice guide and error audit log, exported as PDF.
  3. The story: the MP4 viewing master, the caption file and the Premiere Pro project with original media.
  4. The Signed Agreement, narrator review record and licensing log in 06_Consent. Character path: your source list, credit line and reviewer’s form instead.
  5. A 3-2-1 backup: three copies, on two kinds of storage, one kept somewhere else.

Submit (Canvas only): folder link, a screenshot of your backup locations, AI-use log row.

Grading (10 points): all required parts, complete 4; accessibility: captions or transcript, alt text, headings 1; visual or production craft 2; writing and communication 2; AI-use log row 1.

Instructor notes
  • Release rough cut feedback Wednesday. Narrator Review sends the rough cut as is; Final Cut carries the revision from critique. A narrator who has not responded by Wednesday gets one documented follow-up; the agreement stands. Requests that would make the story untrue are talked through with the student.
  • Watch for uncorrected names in captions, credits without AI disclosure, and archive packages missing the recording or the Teller export.

Video: Finishing, Archiving and Presenting (about 12 minutes)

  • Segment 1: titles, end credits and AI disclosure: the Teller’s AI label, any AI voice label, credits following Archival Producers Alliance and MLA guidance.
  • Segment 2: captions, description of visual information, contrast; the archive package and a 3-2-1 backup.
  • Build an end credit block; export an SRT caption file and the MP4 master.
  • Fill the archive checklist and show three backup locations.
  • The curator’s statement: what the Teller gets right, where it fails, what a visitor should trust; walk the model case study.
  • The case-study page for employers: the recording at the center, process frames beside it.
Module 14

Showcase

Week 15 and finals · 8 hours

Objectives

  • 14.1 Present the Teller and the recorded story for peer review (Course Competency 11)
  • 14.2 Write a curator’s statement that evaluates what the Teller gets right and wrong (Course Competency 6)
  • 14.3 Archive the recorded story, the Teller and your AI decisions on a case-study page in Google Sites (Course Competency 10)

Overview

The Living Archive is your final project and your portfolio piece. A curator’s statement is the text next to a work in an exhibit that tells visitors what it is and how to read it. Yours explains what your Teller gets right, where it fails, and what a visitor should trust.

Watch

Rewatch the presenting section of the Module 13 video. The live showcase is this week’s Studio Session. It is recorded, and its day and time are posted in Announcements a week ahead.

Read

  • The model case study and the case-study Google Sites template, posted in this module

Practice

  • Course survey (ungraded)

Assessment

Living Archive Showcase (10 points, Exercises)

This assignment measures Module Objective 14.1, which supports Course Competency 11.

  • Show your Teller live in the showcase, or post a recorded demo in #showcase. Include your key art, the recorded story (as your agreement allows) and a draft of your curator’s statement.
  • Review three classmates’ projects. Share one question you asked their Teller and what it revealed, and one comment on design (layout, type or color).

Grading (10 points): post: substance and visual evidence 3; accessibility 1; critique comments 4; vocabulary 1; clarity 1.

Final Project: The Living Archive (30 points, Projects)

This assignment measures Module Objectives 14.2 and 14.3 and draws on evidence for Course Competencies 2, 3, 4, 6, 7, 8, 9, 10 and 11.

  1. The Teller (Modules 5 to 10): built in Gemini Notebook from your narrator’s consented archive, in the agreed mode, starting with its AI disclosure. Shared with your instructor only. Character path: built from your public-source archive.
  2. The recorded interview (Modules 11 to 13): 3 to 5 minutes, with titles, corrected captions, archive cards, your own visuals and sound. This recording is the archived story and your portfolio piece.
  3. The error audit and curator’s statement: the full audit log, and a 200- to 300-word statement with two screenshots and notes. Say what the Teller gets right and where it gets the narrator or the story wrong.
  4. Key art (Module 11).
  5. The archive package (Module 13).
  6. The case-study page in Google Sites, from the template (unlisted unless you choose otherwise). Put the recorded interview at the center. Then add the key art, the Teller’s portrait, three conversation map frames next to the matching moments in the recording, a voice guide excerpt, the curator’s statement and the AI-use statement. Write about 200 more words. Add captions and alt text to every image. You may add the Practice Teller as an optional practice section.
  7. Agreement item 12: carry out the end-of-semester plan. Send your narrator the archive copy if the agreement says so. Character path: skip this; keep your source list and credit line in the archive package.
  8. The full AI-use statement and credit line.

Grading (30 points): voice, place and culture in the Teller and the story 3; language, image and power: rights, consent, mode, labeled voice, AI disclosure 3; the Teller’s sources, instructions and voice guide 3; the error audit, revisions and curator’s statement 3; the conversation map’s design and path 3; graphics, video and sound: visual identity and the edit 3; the finished recorded story 3; the archive package and case-study page 3; presentation for peer review 3; accessibility: corrected captions, descriptive transcript or spoken description, alt text, the page checked with WAVE 3.

You are graded on what you made, tested and fixed, never on how smooth the Teller sounds. Check the case-study page with WAVE.

Deliverable options. The default deliverables above earn full marks. Through STEAMworks, you may replace one part of the default work with one of the options below. Each option takes the place of the work named in its row, within the same weeks, so it adds no hours to the course. Every option is graded with the same criteria, which grade the story and the design, not the machine.

OptionWhat you makeWhat it replacesLab need
DefaultThe key art and the recorded interview as described aboveNothingNone; the equal path for online students
Story objectA laser-cut or engraved piece in wood or acrylic, based on one item from your narrator’s archive, with an embedded NFC tag that plays a clip of 60 seconds or less from your recorded interview when a phone taps itThe key art (item 4); the title card is still requiredSTEAMworks laser cutter and safety orientation
Drone establishing footageUp to 30 seconds of aerial footage of places in your narrator’s story, used as establishing shots in the recorded interviewPart of your own visuals in the recorded interview (item 2)STEAMworks drone, flown under the flight rules below
360 or VR presentationThe story presented as a 360 scene or VR room, with the Teller’s portrait, archive cards and the recorded interview placed in the spaceThe key art (item 4); the title card is still requiredSTEAMworks XR lab
  • Choosing and booking. Choose an option by the Teller Portrait and Archive Cards deadline in Module 9. Book lab time through STEAMworks; the booking window is posted in Announcements in Week 1. Complete the STEAMworks safety orientation before your first lab session. STEAMworks supplies the materials (NFC tags, wood and acrylic).
  • Online students. The default path is equal in scope and grading, needs no lab and earns full marks. Online students who live near campus may book STEAMworks time like any other student.
  • Drone flight rules. Drones are flown only under the direct supervision of the instructor, who serves as the FAA Part 107 remote pilot in command and can take control at any time. The instructor handles airspace authorization. No flying over people. Students under 18 follow the same supervised path. Film a place only with the property owner’s permission and only as your Signed Agreement allows.
  • Consent and sharing. The story object uses only an archive item your Signed Agreement allows. The NFC clip opens an unlisted or restricted link, as your agreement allows, and never links the Teller.
  • AI. Gemini may help you write, such as a tag label or a scene caption; it never designs. No image, scene, footage or object in any option is made by AI.
  • On the case-study page. Show the option with photographs or a captioned walkthrough video, with alt text, so viewers who cannot hold the object or enter the scene receive the same story.

Add to Your Portfolio Site (ungraded, Week 15)

Your portfolio is a Google Site. At the end of every course, you add one or two of your best finished projects, not exercises.

  1. Open your portfolio site at sites.google.com with your Maricopa account. If you do not have one yet, start a new site and name it with your name.
  2. Add a page for each project. Insert screen-size images of the finished work and one or two process images.
  3. Add alt text to every image: select it, choose More, then Add alt text (Google’s accessibility help).
  4. Write two or three sentences for each project: the problem, your role and one design choice you would defend.
  5. Choose Publish at the top right, type a short web address, and choose Publish.
  6. Choose Share. Next to Published site, choose Restricted, so only people you add can see it. Add your instructor’s email. When you apply for a job, add the employer’s email.

Who can see it: Restricted is the default. You may switch to Public whenever you choose. If you see an option for Maricopa, it limits viewing to people with Maricopa accounts. If you make the site public, you can tick “Request public search engines to not display my site” in Publish settings. Google says this is a request, not a guarantee (Publish and share your site).

For this course: your case-study page can be one of your projects. Show the recorded story and the narrator’s material only as your Signed Agreement allows, keep the site Restricted unless your narrator agrees in writing to a public page, and never link the Teller. Character path: show the story with your credit line; a brand or trademarked character keeps the page Restricted.

Already have a Behance portfolio from another class? You may use it instead.

Take Your Work With You (ungraded, Week 15)

Your Maricopa Google account may close after you leave the college. Do this before the course ends, so you keep everything you made even if you stop out, transfer or graduate. It takes about 45 minutes.

  1. Save your files in one place. Make one Google Drive folder for this course. Put in it your MP4 master and SRT caption file, Premiere Pro project, portrait, archive cards, key art, conversation map, error audit log and curator’s statement and your AI-use log. Keep your narrator’s archive only as your Signed Agreement allows. Videos you posted to YouTube with your Maricopa account are not copied, so download your own YouTube videos into the folder too.
  2. Copy everything to a personal Google account. Make a personal Google account if you do not have one. First make your own copy (File, then Make a copy) of any file someone shared with you, because files you do not own are not copied. Then, signed in to your Maricopa account, open Google Takeout Transfer and copy your Drive and Gmail to your personal account (see Google’s help page). It can take up to a week, and the copies arrive unshared. If Transfer is not available on your account, use Google Takeout to download your Drive as .zip files and save them on your computer.
  3. Take your Teller with you, only as your agreement allows. Your Teller lives in Gemini Notebook on your Maricopa account and does not move to another account. Keep its instructions, voice guide and source list in your course folder; that is what rebuilds it. On the character path, you may rebuild it from your source list. Otherwise, rebuild it in a personal account only if your narrator’s Signed Agreement allows it, load only the items the agreement allows, and never share it publicly.
    • Know the privacy difference. Your Maricopa account keeps your Gemini work out of AI training (see AI in This Course). A personal account does not have the same protections, and Google may use your activity to improve its AI, depending on your settings. In your personal account, open Gemini, then Settings & help, then Activity (Gemini Apps Activity), and decide whether to turn off Keep Activity. Your narrator’s private material never goes into a personal account without their written yes.
  4. Move your Google Site. Takeout Transfer copies Drive, Gmail and Photos. Do not count on it to move your case-study page. First keep the content: put the site’s text in a Google Doc and its images in your course folder, then open each published page and save it as a PDF (File, then Print, then Save as PDF). Then try a direct copy: in the site editor, choose Share and add your personal email as an editor. Sign in with your personal account, open the site, and choose More (the three dots), then Make a copy. If sharing outside Maricopa is blocked, rebuild the site in your personal account at sites.google.com with the same content and publish it again. The web address changes, so update it on your resume and profiles.
  5. Protect your artwork online. No website can fully stop AI companies from copying public images. These steps make it harder and show the work is yours:
    • Post screen-size images, not your full-size print files.
    • Add your name and a copyright line (© Your Name) to the description or the image.
    • In Adobe apps or Adobe Content Authenticity, attach Content Credentials and choose “I request that generative AI models not train on or use my content.” It is a request, not a lock: Adobe Firefly honors it, and other AI companies may not (see Adobe’s help page).
    • Optional: Glaze, a free tool from a University of Chicago research team, adds hidden changes that make it harder for AI to copy your style. It works best on detailed artwork and is not a guarantee.
    • Keep your full-size master files private in your Drive folder. Your portfolio site shows only screen-size images and stays Restricted until you choose to make it public.
Instructor notes
  • Run the showcase as the Studio Session (90 minutes, recorded): each student demonstrates the Teller live with one audience question, then plays the recorded interview. A Teller about someone who has died, or one without class sharing, is shown by recording only.
  • Confirm each student carries out agreement item 12 (archive and Teller kept by default) and confirms it to the narrator in writing; no public Teller links. Grade the Final during finals week.
  • Deliverable options: post the STEAMworks booking window in Week 1, and confirm before Module 9 that the STEAMworks tags are phone-readable NFC (NTAG213, 215 or 216). For drone sessions, serve as remote pilot in command, obtain airspace authorization near campus before each flight, and keep the area clear of people.
  • Take Your Work With You is ungraded. Before this week, confirm with district IT that Google Takeout Transfer is on for student accounts; if it is off, students use the Takeout download.
  • Confirm with district IT which Google Sites publishing options students see (Restricted, Public or Maricopa only) and whether they can share a site outside Maricopa. If sharing outside Maricopa is blocked, point students to the rebuild path in Take Your Work With You.
  • Gemini Notebooks do not move with Takeout Transfer. A Teller may be rebuilt in a personal account only where the Signed Agreement allows it; check that each student’s folder holds the instructions, voice guide and source list.
  • In the live showcase, thank the narrators; restate item 12 and the no-public-Teller rule.
  • In the live showcase, remind students of the course survey.