City of Miramar AI Boot Camp: Master Run-of-Show (WS1), 4-Saturday format

CONFIDENTIAL · internal, teacher-facing. Not for parents, sponsors or the public.

Camp: four Saturdays, Nov 14, Nov 21, Dec 5, Dec 12, 2026 · 9:00am to 3:00pm · Ansin Sports Complex camp room. Showcase: Saturday Dec 19, 10:00 to 11:30am, Ansin multi-purpose room, Vice Mayor speaking, certificates. Who: 15 students, ages 13 to 16 (settled by Charles, Nov 5) · Teacher A + Teacher B (both Broward-certified, Level 2 background-checked). Read with: CAMP-RESHAPE-4-SATURDAYS.md (the map this follows), CAMP-PROMPT-SYSTEM.md (exact card text, P0 to P6 and the FIX CARDS), CAMP-CURRICULUM-EXECUTION-PLAN.md, CAMP-IT-SETUP.md (laptops must hold their setup Nov 5 to Dec 19), movie-factory/ runbook. Version: v2, 2026-11-03, reshaped from v1 (July 27 to 31 weekday format, kept as CAMP-RUN-OF-SHOW-v1-JULY.md). Card sequence updated to prompt system v2 (P3 + P3B sheets, P4A locations, P4B storyboard frames, F8).

This is the document a teacher delivers the camp from. Every block names its prompt card by ID. The full card text lives in CAMP-PROMPT-SYSTEM.md only. Never retype a card from memory.

0. The shape of the camp

flowchart LR
  S1["Sat 1 · Nov 14<br/>Build your story<br/>01-story.txt saved"] -->|"1 week"| S2["Sat 2 · Nov 21<br/>Characters, locations,<br/>storyboard frames"]
  S2 -->|"2 weeks (Thanksgiving)"| S3["Sat 3 · Dec 5<br/>Song + package<br/>Factory opens<br/>presentations 1 to 8"]
  S3 -->|"render week<br/>(teacher line)"| S4["Sat 4 · Dec 12<br/>Review gate + stitch<br/>presentations 9 to 15<br/>private premiere + rehearsal"]
  S4 -->|"straggler week<br/>(teacher line)"| SC["Sat Dec 19 · 10:00 to 11:30<br/>Family showcase<br/>certificates"]

1. The Saturday frame (every session)

Room rules posted every Saturday: the AI Rules of the Room poster (CAMP-Poster-AI-Rules.html) on the wall before 9:00. The room is shared during the week, so it goes up and comes down each session.

Laptops between Saturdays: they stay with Parks, set aside, signed in, unchanged (no re-imaging, wipe, profile reset or return to the general pool, Nov 5 to Dec 19). Close lids at 2:50; never sign a kid out of an account.

The six gap-format rules (new since July; apply every Saturday)

1. End every Saturday with a Drive save (2:35 block). Covers a reset or swapped laptop.
2. Open Saturdays 2 to 4 with a re-entry block. Re-login check, reopen the right Project and chat, one-minute "where my movie is" share with a partner. 15 min on Sat 2 and Sat 4; 30 min on Sat 3 (after the Thanksgiving gap).
3. Absent-kid lane. A kid who misses a Saturday is never dropped. Teacher B runs a catch-up lane the next Saturday with the same cards (per-Saturday rules below). Teacher A may queue an extra Factory slot.
4. Laptop state check at 9:00 (in the frame above).
5. "Tomorrow" becomes "next Saturday". Every wrap script previews the next session by date.
6. Factory between sessions is teacher-only work. Kids never need to be online between Saturdays.

2. SATURDAY 1 (Nov 14): "Build your story"

The win: every kid leaves with 01-story.txt saved (STORY + SCENE TABLE + LOCATION LIST, P2E), on the laptop AND in Drive. In July, P2E could slip to the next morning. With a week gap, it cannot: the story must be safe before kids go home.

Sat 1 time-block table

Sat 1 overflow rule (the story must be saved before 2:45):

• A kid who has not locked P2E by 2:35: teacher has them paste P2E now with their beats as they stand, accept the first full draft, and save it. Edits happen in the Sat 2 re-entry block.
• A kid who has not locked P2D by 2:15: teacher saves the HERO CARD, CHARACTER LIST, WORLD CARD and whatever beats exist into 01-story.txt as a draft, uploads it, and marks the kid for the Sat 2 catch-up lane (P2D + P2E first, 30 to 45 min, before P3-START).
• Risk: P2E had about an hour in July (Day 2 morning) and has 20 minutes here. It assembles already-locked blocks, so it is fast, but watch it at the Nov training evenings and in the first live run. If the room is slow at 1:15, cut the partner read first, never the Drive save.

Script 1A: Sat 1 welcome + rapport (9:15, verbatim)

"Good morning! Welcome to the City of Miramar AI Boot Camp. I'm [Teacher A first name], and this is [Teacher B first name]. For four Saturdays, this room is a movie studio. And you are the directors.

But first, I need to know who's in my studio. When I point to you: your first name, and one piece of tech or one game you love. I'll go first. I'm [name], and I'm ridiculous about [teacher's real answer]."

[GO AROUND THE ROOM. Repeat every kid's name back. React to every answer for real: "Roblox? Which world?" "You edit videos? On what app?" Write nothing; just learn names. 10 to 12 minutes.]

"Okay. Gamers, raise your hand. Artists, drawers, doodlers? Music people, who's got a playlist for everything? Storytellers, who has an idea for a movie or a game already in their head?

Look around. That's a whole movie studio in one room. Writers, artists, musicians, directors.

Here's the deal. No tests. No grades. No wrong answers. There are only two rules in this room, and I'll show you both in a few minutes. Your job is to make something so good your family loses their mind at the showcase on December 19. That's the whole assignment."

Script 1B: "Why you're here" preview (9:45, verbatim)

"So what are you actually making? Let me show you, because telling you won't do it.

This movie was made with this exact process. Same tools, same steps, same cards you're about to use."

[PLAY THE DEMO MOVIE ON THE PROJECTOR. Full length. Let it land.]

"That is what you're building. Your story. Your characters. Your own theme song, a real song you can play in the car. Your movie, on the big screen, with your family watching.

Here's the plan. Today you write your story. Next Saturday, November 21, your characters and your world get faces. Then a short break for Thanksgiving. On December 5 you make your song and the movie factory starts up. On December 12 your movie is finished, and we watch all fifteen together. And on December 19, the showcase, for your families.

One question before we start. Who here has already used AI? ChatGPT, Snapchat AI, anything?"

[HANDS GO UP. Acknowledge it.]

"Right. Most of you. So this isn't about meeting AI. It's about learning to be the boss of it. And that starts with the most important 45 minutes of the whole camp. Right now."

Script 1C: The AI safety + governance talk (10:00 to 10:45, FULL delivery script)

Teacher setup: kids away from laptops (lids closed). Poster on the wall. This is a conversation, not a lecture. The [ASK] moments are real questions; wait for real answers. Timing marks keep you honest.

(0:00) Opening: what AI actually is.

"Forty-five minutes. This is the one serious block of the camp, and I promise it's not boring, because at the end of it I'm going to melt your brains a little.

First question. [ASK] What do you think AI actually is? Shout it out."

[TAKE 3 TO 4 ANSWERS. No wrong answers yet.]

"All decent answers. Here's mine: AI is a tool. That's it. The most powerful tool you've ever picked up, but a tool. Like a power drill. A power drill can build a house. It can also make a hole in something you love. The drill doesn't know the difference. The person holding it does.

Here, you're the person holding it. So we're going to talk about how to hold it right."

(0:05) It's a tool, not a friend. Feelings go to humans.

"Here's the first thing, and it might sound weird: the AI is going to be NICE to you. Really nice. It'll say your ideas are great. It'll remember what you told it. It can start to feel like a friend.

It is not your friend. It's not a person. It doesn't actually know you, and it doesn't actually care about you, because it can't. It's a very good prediction machine wearing a friendly voice.

[ASK] Why do you think I'm making a big deal out of this?"

[TAKE 2 ANSWERS. Guide toward: because people forget.]

"Because some people, even adults, start treating it like a friend or like a therapist. They tell it their problems, their secrets, their feelings. Here's the rule, and it's a rule for life, not just this camp: feelings go to humans. If something is bothering you, that goes to a real person. A parent, a teacher, a friend, a counselor. Me. The AI is for building things. Humans are for the real stuff. Everybody good with that? Say it with me: feelings go to humans."

(0:11) Privacy: what never goes in the box.

"Rule two. There are things that NEVER get typed into an AI. Ever. Here's the list, and it's on the poster every Saturday:

Your full name. First name only, always. Your address. Your school. Your phone number. Any password. Anything about where you'll be and when.

[ASK] Why? Why does it matter what I type into a chat box?"

[TAKE ANSWERS. Guide toward: you don't control where it goes.]

"Because once you type it, it's not yours anymore. You don't know where it's stored or who sees it. Same reason you don't shout your address in a game lobby. In this room, in the story you write, in the songs, everywhere: first names only. The AI in your project already knows this rule. If you slip and type something personal, it's going to remind you. That's not it being annoying. That's it doing its job."

(0:17) If it gets weird, tell your teacher. Same rule as your games.

"Rule three, and this is the exact same rule you already know from online games. [ASK] In Roblox or Fortnite, if some random person starts saying weird stuff to you, what are you supposed to do?"

[ANSWER: block, report, tell an adult.]

"Exactly. You don't argue with them. You don't handle it alone. You report it and tell an adult. Same rule here, exactly. If the AI ever says something that feels weird, off, creepy, or wrong, you don't argue with it. You don't keep going to see what happens. You raise your hand and say: 'Hey, this got weird.' That's it. You will never, ever be in trouble for showing me a weird AI answer. You'd actually be helping me. It's a machine. Sometimes machines glitch. You're the report button."

(0:22) What we make and don't make here.

"Now, the creative rules. Short list.

No real people. Not your friends, not your teachers, not celebrities, not anybody who actually exists. Your characters are invented. Here's why: putting real people into AI stories and images without their okay isn't fair to them, and it can genuinely hurt someone. Invented characters are also just better; you control everything about them.

Everything we make is school-safe. If you couldn't show it to your principal AND your grandmother, it doesn't get made. Now, before you groan: cartoon action is totally fine. Chases, battles, a villain, explosions, a dragon knocking over a building? Fine. This is a Pixar-style movie, and Pixar movies have villains and danger. What we don't do is gore, real-world weapons stuff, or scary-for-no-reason.

[ASK] Quick check. A villain traps the hero in a collapsing temple: yes or no? [YES.] A scene where a character gets hurt and there's blood everywhere: yes or no? [NO.] You've got it. It's honestly the same line the movies you watch already follow."

(0:28) Why some tools are 18-plus, and why I run the video machine.

"One more rule, and I want to explain the why, because you're old enough for the why.

Some AI tools have age rules. Some are 13-plus with permission, which is why your parents signed forms. And some are 18-plus, period. The video generation tool we use in December is one of those. That's not the city being strict; it's the tool's own rules, the same way movie ratings work.

So here's how we handle it: on December 5, the movie factory starts, and I drive it. Your story, your characters, your scenes, your song: all yours. The video machine: my hands, your movie, up on the projector where everyone can watch it happen. You'll see your clips, and you approve or reject every single one. You're still the director. I'm just the union crew."

(0:33) AI can be wrong. You are the boss.

"Last rule, maybe the most important one for the rest of your life.

AI sounds confident ALL the time. Even when it's completely wrong. It will tell you a wrong fact with the same confident voice it uses for a right one. It never says 'I'm not sure' unless you make it.

So the rule is: you are the boss. You check it. If something sounds off, question it. If it writes a story beat you don't like, change it. If it makes your hero look wrong, make it redo it. It works for you, not the other way around. The kids who get the most out of this camp are not the ones who accept whatever it spits out first. They're the ones who say: 'No. Again. Better.'

[ASK] Everybody: who's the boss? [THEY SAY: I AM.] Louder. [I AM.] Correct."

(0:36) The wow segment: what this tool can actually do.

"Okay. Rules done. You now know how to hold the drill. Now let me show you what the drill can build, because this is the part where your brain should melt a little."

[WOW REEL, on the projector, 6 to 7 minutes. Show, don't lecture. Suggested sequence, using material prepared before Nov 14:]

1. A photo-real AI image next to a real photo: "One of these isn't real. Vote." [Let them vote, reveal.]
2. A 10-second AI-generated video clip.
3. A full AI song (30 seconds of the demo movie's Suno track): "A machine wrote and performed this in 60 seconds."
4. Speed demo, live if WiFi allows: ask ChatGPT for a 4-line poem about Miramar in the voice of a pirate. "Three seconds. A whole poem."
5. The kicker: "People are using these exact tools right now to make ads, music, film scenes, and games. Professionals. And the tools you'll use here are the same ones."

"Here's the thing. Most adults have never done what you're about to do. By December you'll have written a story, designed a cast of characters, produced a song, and directed an animated movie. In four Saturdays. That's what happens when a good idea meets this tool and the person holding it knows what they're doing.

After the break: laptops open, and you meet your studio. Let's go."

(0:43) Buffer. Questions, then line up for the 10:45 bathroom break.

Sat 1 materials

• MetAiBlock sign-in/sign-out sheet (printed, on clipboard, at the door) + pen
• City's authorized pickup list + photo-ID check reminder card at the door (Sat 1 = every parent shows ID)
• 15 login cards (student account + password, laptop station number). Collected at 2:50 and kept by Teacher A between Saturdays.
• Name tents + markers (kept in the camp bin for all four Saturdays)
• AI Rules of the Room poster (on the wall before 9:00)
• Projector connected + tested; teacher laptop with the demo movie and song files LOCAL (not streaming)
• Wow-reel media saved locally on the teacher laptop
• Student deck loaded on every laptop (bookmark or desktop file)
• 2 spare laptops (of the 19) confirmed present and signed in to a spare student profile
• [power plan TBD]: chargers, outlets and power strips for 19 laptops over a 6-hour day (open item, see section 9)

Sat 1 early-finisher / stuck-kid tracks

• Early finisher (P2E locked before 2:15): polish the story (one round of edits), then become a "story consultant" for a kid who wants a listener. Never idle laptops on other sites.
• Stuck kid (no theme by 12:00): teacher picks 2 of the 4 themes and asks "this one or this one?" A forced binary always unsticks a 13-year-old.
• Stuck kid (frozen at hero questions): use the P0 behavior: tell the kid to type "give me 3 choices." The card system is built for this.
• Shy kid at partner-read: reads to a teacher instead. Never force the pair.

Sat 1 contingency box

3. SATURDAY 2 (Nov 21): "Bring it to life"

The win: every kid has characters/ (reference + sheet per character), locations/ and scenes/ (6 to 10 storyboard frames) saved and in Drive. This is the last session before a 2-week gap. Nothing leaves the room unsaved.

Sat 2 time-block table

Sat 2 overflow rule: the load is about 260 minutes of image work for a kid with 4 characters, 4 locations and 8 scenes, against about 215 minutes of block time. Expect stragglers. A kid with fewer than 6 frames at 2:35 saves what exists and finishes P4B in the Sat 3 finish lane (9:45 to 10:45 with Teacher B), capped at 6 frames.

Sat 2 materials

• Sign-in/out sheet + pickup list
• Printed pace card for teachers (25 min/character with sheet, 10 min/location, 15 min/frame, redo cap 2)
• Projector (for showing one good reference + sheet example at 9:40)
• Spare laptops charged
• USB drive (emergency file transport if Drive or WiFi misbehaves)

Sat 2 early-finisher / stuck-kid tracks

• Early finisher (all frames done): polish the weakest frame (1 extra redo allowed). Then help a neighbor check frame numbering. Do NOT start the song early: P5A needs a fresh chat on Dec 5 and the gap would orphan it.
• Stuck kid (behind at lunch): cut scene count toward the 6 minimum, not the character count. A 6-scene movie is complete; the cap exists for exactly this.
• Style drift (characters don't match): FIX CARD F4 pattern: re-anchor the chat with the locked blocks and the style line, regenerate. If a chat is truly polluted, start a fresh chat with P3-START and paste everything back in.
• Blocked generation: FIX CARD F8. Never more than 5 minutes fighting a block.
• Kid hates every generation: re-run the appearance questions; vague answers make vague images. Specifics fix it ("emerald green hoodie" beats "cool clothes").
• Absent on Sat 1, did the catch-up lane: reduced scope: hero + 1 sidekick (cap 2 characters), 2 locations, 6 frames. Reduced scope, complete movie.

Sat 2 contingency box

4. SATURDAY 3 (Dec 5): "Your soundtrack + the factory starts"

The win: all 15 Drive folders complete (P6 DELIVERED), the Factory running, presentations 1 to 8 done. The hard gate of the whole camp is P6 at 11:20. The render week depends on it.

Sat 3 time-block table

Script 3A: The "age rule" explanation (Sat 3, 12:45, verbatim)

"All fifteen folders are in. Which means it's time. The factory opens right now.

Quick reminder of something from our first Saturday. The video tool we're about to use is rated 18-plus. That's the tool's own rule, like a movie rating. I checked the rules, and here's what they mean for us: I drive, you direct. Not because you couldn't figure out the buttons. Honestly, some of you would figure them out faster than me. It's because following the rules IS the skill. Anyone can use a tool. Professionals use tools the right way. That's what being AI-literate actually means, and it's what makes your parents comfortable with all of this.

So here's how the factory works. It reads your folder from Drive: your story, your scene table, your characters, your locations, your storyboard frames, your song. It turns each frame into a short moving clip. Every clip shows up on the review screen with your name on it. And nothing, NOTHING, goes into your final movie until you look at it and say yes. If a clip is off, you flag it and the factory redoes it. You have full veto power. My hands, your movie.

The factory works all week while you're gone. Next Saturday your clips are waiting for you. Test pilot rules first, though: the demo movie goes through the machine before yours. Watch the screen."

Script 3B: Story presentation coaching (used Sat 3 + Sat 4, verbatim)

Setup (Teacher A says once, at 1:05 on Sat 3):

"While the factory renders, this room becomes a pitch room. Every director presents their story to the studio. That's us. Here's the format, four things, about two minutes, and I'll be right here:

One: say your title. Loud and proud. Two: introduce your hero. Name, and what they want. Three: tell us your message. What should we feel at the end? Four: read us your favorite part. Just a few lines, your best moment. Sell it.

Then we clap, because we're a supportive studio, and the next director is up. Who's first?"

Per-kid coaching lines (use as needed while they present):

• Before they start, quietly: "Title, hero, message, favorite part. You've got this."
• If they rush: "Wait. Say the title again like it's on a poster."
• If they mumble the reading: "Ooh, hold on, that part's good. Read it again, slower. Make us feel it."
• If they freeze: ask the four as questions: "What's it called? Who's your hero? What do they want? Now read me one good line."
• After every kid, every time: "Give it up for [name]!" Find one specific thing to praise: "That villain has an actual reason. That's better than half the movies out right now."

Sat 3 materials

• Sign-in/out sheet + pickup list
• Headphones if the city provided them (Suno block gets loud otherwise; low-volume rule ready either way)
• Teacher laptop: Factory pipeline tested, Drive access verified, movie-factory/ runbook open, INPUT-SPEC printed
• The Factory board (whiteboard or printed grid: 15 names × queued/rendering/review/approved/stitched). It must survive a week: printed grid, kept by Teacher A.
• Projector on the teacher laptop all afternoon
• Presentation order list (DELIVERED order from the morning)
• Finish-lane table + a printed list of who is on it (from the Sat 2 frame counts)

Sat 3 early-finisher / stuck-kid tracks

• Early finisher (song done, folder delivered early): prep the presentation (pick the favorite part to read), or start the comic bonus: arrange storyboard frames in order in the template doc.
• Stuck kid (hates both Suno takes): the fix is the style line, not the lyrics. Tweak style words once (per P5B), regenerate once, pick the better of the field. Ship it; done beats perfect, and the factory needs the song today.
• Stuck kid (upload fails): teacher moves the folder via USB to the teacher laptop and uploads on the teacher line. The kid still runs the P6 checklist; only transport changes.
• Presentation refusal: offer the duet option: teacher reads the favorite part aloud, kid does title + hero + message. Every kid presents in some form before Dec 19; Sat 3 and Sat 4 are the low-stakes rehearsal for the showcase.

Sat 3 contingency box

5. RENDER WEEK (Dec 7 to Dec 11, teacher line only)

Kids are not involved. No kid account is used.

Rule: the teacher never approves a clip for a kid during render week. Approval is the kid's, on Dec 12. The teacher may stitch a draft cut from all clips so the premiere has something to play. Open: who is paid for render-week hours (teacher or MetAiBlock) is not settled. See section 9.

6. SATURDAY 4 (Dec 12): "Movie day + private premiere"

The win: every clip reviewed by its director, every movie stitched, all 15 presented, all 15 watched together, 2-sentence intros written, showcase rehearsed.

Sat 4 time-block table

Sat 4 materials

• Sign-in/out sheet + pickup list
• Factory board (from the render week) + review station (second screen or dedicated laptop, per Factory runbook)
• Headphones at the review station if available
• Comic template doc ready in each kid's Drive folder (empty, panels pre-laid)
• Index cards + pens for intros; teacher folder to keep them
• Printed roster for the certificate spelling check
• Dec 19 parent reminder slips (time, room, arrive 9:30; no personal data on the slip). [printing TBD]

Sat 4 early-finisher / stuck-kid tracks

• Early finisher (movie stitched, comic started): finish the comic, or serve as review-station helper (calls kids up in order).
• Stuck kid (keeps flagging the same clip 3+ times): teacher decision point per the Factory runbook: accept best-of-three, or swap the clip for a slow push-in on the storyboard frame (a classic film move; looks intentional). The movie ships.
• Stuck kid (movie feels "wrong" overall): almost always the music bed timing; let them pick where the song starts. Small control, big satisfaction.
• Kid waiting on re-renders: presentations, comic, intro writing, helping a neighbor's caption lines. The room is never idle.

Sat 4 contingency box

7. STRAGGLER WEEK (Dec 14 to Dec 18, teacher line only)

8. SHOWCASE (Sat Dec 19): 10:00 to 11:30am, Ansin multi-purpose room

90 minutes, not July's 110. Movies are short enough to fit: the Factory builds 6 to 10 shots at 10 seconds each by default (movie-factory/shotlist_prompt.md, config.example.yaml; 15 s is the render hard cap), so a movie runs about 1:00 to 1:40 plus title and end cards, and 2:30 at the 15 s cap. With the 2-sentence intro and walk-up, each kid takes about 3 to 3.5 minutes. Do not raise clip length past 10 s without re-checking this table.

Showcase time-block table

Timing guard: if movies run long, the buffer goes first, then shorten the welcome. Certificates are never cut. Space: the multi-purpose room capacity is [room capacity TBD with city]. July expected 50 to 60 guests. If the room is too small, the two-seatings fallback is no longer workable inside 90 minutes; raise it with the city before Dec 12.

Script 5A: Showcase MC skeleton (Dec 19, 10:00, verbatim skeleton)

1. Welcome (about 3 min, then the Vice Mayor):

"Good morning, everybody! Welcome to the Ansin Sports Complex, and welcome to the first ever City of Miramar AI Boot Camp showcase. I'm [Teacher A name], and along with [Teacher B name], I've had the best seat in the house for four Saturdays. Parents, family, friends, honored guests from the City: thank you for being here. You are about to watch fifteen world premieres.

First, please welcome [Vice Mayor's name and title, exactly as the city confirms]."

[VICE MAYOR SPEAKS. Thank them by name after.]

2. Intro the camp (about 2 min):

"Let me tell you what happened in this room. On the first Saturday, these fifteen young people walked in as students. They learned how to use AI safely and responsibly: real rules, real skills. Then each of them wrote an original story. The next Saturday they designed their characters and their worlds. In December, every one of them produced their own theme song. A real song. And then our movie factory turned on, and by last Saturday, every single one of them had directed their own animated movie.

Nobody handed them these. They wrote them, designed them, directed them, and approved every single shot. Here's how this works: I'll call each director up, they'll introduce their movie in their own words, we watch it together, and you cheer like it's opening night. Because it is."

3. Kid-by-kid (repeat 15 times, about 3 to 3.5 min each including the movie):

"First up / Next up: the director of '[Movie Title]'. Come on up, [First Name]!"

[KID SAYS THEIR 2 SENTENCES. If they freeze, MC prompts: "Tell them what it's called. What are you proudest of?"]

"[One specific praise line: 'Wait till you see this villain.' / 'This soundtrack goes hard, I've had it stuck in my head since December 5.'] Roll it!"

[MOVIE PLAYS. Applause. Kid stays standing for it, then sits.]

4. Certificates (about 15 min):

"Every director here completed the full program: story, characters, soundtrack, and a finished film, plus the AI safety training they'll carry a lot longer than four Saturdays. When I call your name, come get what you earned. Parents, cameras up.

[Name by name, in showcase order. Handshake, certificate, photo moment, applause. Both teachers at the table.]

Ladies and gentlemen, one more time: the directors of the City of Miramar AI Boot Camp, class of 2026!"

5. Thanks + close (about 3 min):

"Before we let you go. This camp doesn't happen by accident. Thank you to the City of Miramar: the leadership, Parks and Recreation, and the whole team here at Ansin who gave us this room, these laptops, and this stage. [IF AND ONLY IF a sponsor is confirmed in writing: And thank you to our sponsor, [Sponsor Name].] Give them all a hand.

Parents: everything your child made, the movie, the song, the story, the artwork, and the comic, is coming to the email you registered with. Share it, post it, be loud about it. They earned it.

To our fifteen directors: this was just the start. This tool isn't going anywhere, and now you know how to hold it. Go make things. Thank you all, and good morning!"

Wording check before Dec 19: v1 said "completely free for every family." Registration now carries a fee ($25 resident / $30 non-resident per the city recap). The line is removed above. Do not reinstate it.

Showcase materials

• Sign-in/out sheet + pickup list (parents still sign out at the door)
• All 15 movies LOCAL on the teacher laptop + backup USB copy
• Showcase order list (2 copies: MC + playback)
• 15 certificates, names verified on Sat 4, in showcase order + a few blanks as spares
• The 15 intro cards (kept by the teacher since Sat 4)
• Testimonial capture setup (phone on tripod), only within the recording consent the city collected at registration ⚠️ confirm that consent covers this format
• Take-home Drive links prepared and matched to the city's parent email list

Showcase stuck-kid tracks

• Kid terrified to speak: the duet option: MC reads the 2 sentences, kid stands and takes the applause. Standing is non-negotiable; speaking is coached, not forced.
• Comic unfinished: ship the movie, song, story and images in the take-home; add the finished comic to the family Drive link the following week. The comic is a bonus in the run of show. ⚠️ The signed agreement promises it ("available to print or order"); see section 9.

Showcase contingency box

9. Deviation handling (when the AI goes sideways)

The system is built so deviations are cheap. Cards are small, output blocks are checkpointed, and every failure mode has a numbered fix. The teacher never argues with the model and never freelances a repair prompt.

Go to the FIX CARDS at the bottom of CAMP-PROMPT-SYSTEM.md and paste the matching one:

Escalation order when a fix card doesn't take: try the card once more in plainer words → F4 re-anchor → fresh chat with the kid's saved blocks → teacher judgment call, move the kid forward and log it for the post-session debrief. The checkpoints exist so format drift dies on Sat 1 instead of breaking the Factory on Sat 3.

10. Countdown checklist

Before Sat 1 (Nov 14):

• Demo movie + song + wow reel built (by MetAiBlock) and saved LOCAL on the teacher laptop
• 15 student accounts + Projects (P0 installed) + Drive folders created and tested on the 19 laptops
• Login cards printed; station numbers assigned
• Poster, sign-in sheet (Saturday dates), pickup list, photo-ID card ready

By Sat 4 (Dec 12):

• Certificates PRINTED (about 20: 15 + spares) and in the camp room [printer TBD]
• Roster names FINAL (registration list confirmed with the city), spelling checked by each kid on Sat 4
• City's answer on room capacity, Vice Mayor's role and running order locked
• Parent showcase invitation confirmed sent by the city

By Fri Dec 18:

• All 15 final movies stitched, LOCAL on the teacher laptop + backup USB, each played once with sound
• Drive links PREPARED: each family's take-home link matched to the registration email list (city holds the emails); links tested from a non-teacher account

Dec 19 close:

• Take-home links sent per the city's email list (send path per Charles)
• Sign-out sheets complete, all 5 sessions scanned for the record
• City handed its content package plan (15 videos)
• Room reset; 19 laptops returned per Parks instructions (the set-aside hold ends)

11. Placeholders and open items (do not resolve without a source)

City of Miramar × MetAiBlock · AI Boot Camp 2026 · Run-of-show v2 (4-Saturday format), 2026-11-03.