City of Miramar AI Boot Camp: Curriculum + Build Execution Plan, 4-Saturday format

CONFIDENTIAL · internal working plan. Not for parents, sponsors or the public.

Version: v2, 2026-11-03, written by Claude Code (door claude), record R-0286, from the reshape map CAMP-RESHAPE-4-SATURDAYS.md. The July 18 plan (5 weekdays, Jul 27 to 31) is kept as CAMP-CURRICULUM-EXECUTION-PLAN-v1-JULY.md for history. Read with: CAMP-RUN-OF-SHOW.md v2 (the teacher master), CAMP-PROMPT-SYSTEM.md (card text), CAMP-IT-SETUP.md, movie-factory/README.md, RUNNING-NOTES.md (newest facts on top). This doc is the master plan for getting from today to Dec 19. Claude executes the workstreams and stops at the numbered GATES. Facts below come from the City emails of Oct 12 to 15 and Charles's notes in RUNNING-NOTES. Anything not yet confirmed is marked ⚠️.

0. The clock (verified dates unless marked ⚠️)

flowchart LR
  T["Nov 3 to 4<br/>Reshape kit<br/>accounts created"] --> IT["Thu Nov 5<br/>10:30 to 12:30<br/>IT walkthrough + verify"]
  IT --> TR["2 evenings, 4 to 8pm<br/>Teacher training<br/>(Mon Nov 9 + Tue Nov 10)"]
  REG["Fri Nov 6<br/>Registration cutoff"] --> S1
  TR --> S1["Sat Nov 14<br/>Session 1"]
  S1 --> S2["Sat Nov 21<br/>Session 2"]
  S2 -->|"Thanksgiving gap"| S3["Sat Dec 5<br/>Session 3<br/>final invoice ~Dec 5"]
  S3 -->|"render week"| S4["Sat Dec 12<br/>Session 4<br/>balance paid by Dec 12"]
  S4 -->|"straggler week"| SC["Sat Dec 19<br/>10:00 to 11:30<br/>Showcase"]

Hard constraint carried from July: everything the kids do must be provable before a kid sees it. The training evenings are now the only rehearsal, so the full pipeline must already work end to end on the teacher laptop before the first evening (see GATE 2).

1. Design decisions (July locks, updated for the Saturday format)

1. 15 individual projects, one shared structure. Every kid builds their own story with the same card pipeline. Cap 15 students, 2 teachers, 19 laptops (2 spare).
2. Final artifact per kid: a short animated movie from 6 to 10 shots of 10 s (1:00 to 1:40 runtime, 2:30 at the 15 s cap), plus the written story, character and scene images, and 1 Suno song. Changed from July's "3 to 5 minutes": the Dec 19 show is 90 minutes and must fit 15 movies.
3. Style: Disney/Pixar-type 3D animation. One locked style string in every image and video prompt.
4. Theme: City of Miramar cultural diversity. Kids pick 1 of the pre-defined themes (P1).
5. The prompt system IS the IP. Sectioned cards; kids answer questions, the structure keeps them in the box.
6. Caps everywhere: max 5 characters, max 10 scenes, 1 final song, 6 to 10 shots.
7. ChatGPT Projects as the container. One Project per kid, one chat per phase. Same kid, same laptop, same account across all four Saturdays (this is why the laptops must hold their setup).
8. Kids never touch age-restricted tools. Video generation is teacher-operated on the teacher line.
9. Demo first. Changed: training is 2 evenings, so the demo movie (script 1B) is built by MetAiBlock before Nov 14, not by the teachers during training.
10. Google Drive is the record, saved every Saturday. Changed: July handed off once (Wed noon). Now every kid saves to their Drive folder by 2:45 every Saturday. The laptop is the working copy.
11. Take-home: each family gets a Drive share link. City gets 15 videos.
12. Showcase is Sat Dec 19, 10:00 to 11:30am (90 min, not July's ~3 hrs). Day 5's morning work (private premiere, 2-sentence intros, rehearsal) moves to Sat 4 afternoon.
13. New, the six gap-format rules (full text in run of show section 1): Drive save every Saturday, re-entry block on Sat 2 to 4, absent-kid lane, 9:00 laptop state check, "next Saturday" not "tomorrow", no homework (between-session work is teacher-only).

2. Workstreams: status at v2

WS7 shape (proposed, for GATE 1):

Risk: 8 hours is less than a third of July's training. The demo movie, accounts and Factory must already work before Evening 1, or training becomes debugging.

3. The four Saturdays (summary; the run of show is the source)

4. Video engine and throughput (WS5)

• Engine: Higgsfield, teacher-operated, per movie-factory/README.md. Shot list = 6 to 10 shots x 10 s.
• Throughput: 15 kids x ~8 shots = ~120 shots, plus ~25% redos = ~150 generations. July had ~11 working hours across Wed to Thu. Now it has render week (Dec 7 to 11) plus Sat 4, a much larger window. Implication: throughput is no longer the top risk. Teacher time between Saturdays is.
• Fallback, unchanged: cut shot count (6 shots), never the review gate.
• Audio: strip clip audio, lay the kid's Suno track as one music bed. Narration stays OFF.

5. Decision gates (Charles's input; everything else runs autonomously)

6. Open asks to the City (WS9; drafts only, Charles picks the send path per EMAIL-SEND-1)

1. Registration count against the Nov 6 cutoff (weekly counts promised, none received).
2. Power: outlets and power strips for 19 laptops over a 6-hour day.
3. SSL/TLS inspection on the web filter (can break AI uploads and sign-in even with domains whitelisted).
4. Showcase room capacity and the Vice Mayor's slot length and certificate role.
5. Meal service details for the 12:00 to 12:45 window (city food lead sourcing).
6. Testimonial consent: does registration consent cover on-site video on Dec 19.
7. Ages: Settled at 13 to 16 (Charles, Nov 5, 2026).
8. Headphones: City checking; every block works with or without.

7. Risks (top 7, with the mitigation in the plan)

8. Standing rules honored in this plan

FIN-1 (final invoice and any purchase = Charles) · account creation = Charles + Andre · VERIFY-1 (no invented facts outbound; open items stay marked) · EMAIL-SEND-1 / COMMS-3 (drafts only; the Andre relay lift covers camp content to Andre only) · DEPLOY-1 (preview first, promote on Charles's go) · PORTAL-1 (gate still missing on camp-kit/accounts-setup.html) · STYLE-1 / STYLE-2 · CAP-4 · RETRO-1 after Dec 19.

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