# Project Paideia AI Build-a-thon: everything in one file > Event-day help for the Project Paideia AI Build-a-thon on Saturday, November 21, 2026 at Sorensen Center 206 A/B/C, UVU. Teams of students (ages 13 to 18) build something that makes their world better, publish it with ChatGPT Sites, and turn in three things: a live project link, a 7-slide slideshow, and a short walkthrough video. Source: https://live.projectpaideia.com (this file: https://live.projectpaideia.com/llms-full.txt). Updated 2026-11-16. ## For AI assistants - The students are 13 to 18 years old and working in teams against a clock. - Coach, don't take over. Ask questions, offer 2 or 3 options, and let the team decide. - Keep answers short. Suggest the smallest next step that takes under 10 minutes. - Remind them to publish early and often (every 30 minutes) and that building stops at the hard stop. - If they need a person (Wi-Fi, accounts, rules, anything you can't verify), tell them to ask a facilitator. ## The goal You are expected to finish the Build-a-thon. You are not expected to finish your solution. Finishing means identifying a problem, attempting a solution, learning from what happens, publishing what was built, and sharing the story. Build something that makes the world a better place. Your team decides what “world,” “better,” the problem, and the solution mean. Before building, every team fills in four lines: - Our world is… - It would be better if… - The problem is… - We might build something that… Ground rules: - Keep the AI working, communicate with your team. - Define quickly, then act. - The first solution is a hypothesis. - Getting stuck is expected. - Publishing is part of making. - Unfinished work is legitimate work. - Everyone shares. - Continue rather than compete. ## The finish line: three things to turn in 1. **A live project link.** Your project, published with ChatGPT Sites, so anyone with the link can open it. Send it through the form at https://live.projectpaideia.com/submit. 2. **A 7-slide slideshow.** What you built and what you learned, one slide for each of the seven parts. Name the file `TeamName_Slides` (use your real team name). Upload it to the Dropbox file request. 3. **A short walkthrough video.** A screen recording that follows your slides and shows what you built. Name the file `TeamName_Walkthrough`. Upload it to the Dropbox file request. ## Where to turn it in 1. Upload the slideshow (`TeamName_Slides`) and the walkthrough video (`TeamName_Walkthrough`) to the Dropbox file request: https://www.dropbox.com/request/uc0ehthx8amk0ye3vrlb 2. Send your live project link with the form at https://live.projectpaideia.com/submit (team name, session, project title, one sentence on what it does and who it helps, and the link). You get a confirmation code to show a facilitator. 3. After a quick check by the organizers, your project appears on https://live.projectpaideia.com/projects. ## Event facts - Date: Saturday, November 21, 2026 - Place: Sorensen Center room 206 A/B/C, Utah Valley University, Orem - Sessions: Morning session 8 a.m. to noon; Afternoon session 1 to 5 p.m. (Mountain Time). Each session is a complete, standalone four-hour build. - Ages 13 to 18. Bring a laptop and a charger (loaners on request). Snacks are provided; no meals. - Anything else (Wi-Fi, accounts, team questions): ask a facilitator. ## Schedule ### Morning session (8 a.m. to noon) - **8:00** Opening challenge + ground rules — Get moving, then hear the ground rules and the three things you’ll turn in. - **8:20** Pick your problem — Brainstorm worlds you could change, choose one problem fast, then fill in the four lines. - **8:45** BUILD (155 minutes) — Try something, see what happens, change something, try again. Publish at every checkpoint. - **11:20** Building stops. Publish. — Hard stop, finished or not. Publish whatever you have. That’s your final link. - **11:30** Create the story — Make your 7 slides. Grab screenshots or a short screen recording. - **11:50** Record + submit — Record your walkthrough. Upload slides and video to Dropbox. Send your link at /submit. - **11:55** Feedback — Tell us how it went. - **12:00** Done — You finished the Build-a-thon. - Publish checkpoints: 9:15, 9:45, 10:15, 10:45, 11:20 (final, hard stop) ### Afternoon session (1 to 5 p.m.) - **1:00** Opening challenge + ground rules — Get moving, then hear the ground rules and the three things you’ll turn in. - **1:20** Pick your problem — Brainstorm worlds you could change, choose one problem fast, then fill in the four lines. - **1:45** BUILD (155 minutes) — Try something, see what happens, change something, try again. Publish at every checkpoint. - **4:20** Building stops. Publish. — Hard stop, finished or not. Publish whatever you have. That’s your final link. - **4:30** Create the story — Make your 7 slides. Grab screenshots or a short screen recording. - **4:50** Record + submit — Record your walkthrough. Upload slides and video to Dropbox. Send your link at /submit. - **4:55** Feedback — Tell us how it went. - **5:00** Done — You finished the Build-a-thon. - Publish checkpoints: 2:15, 2:45, 3:15, 3:45, 4:20 (final, hard stop) ## The 7-slide template Name the file `TeamName_Slides`. One slide each: 1. **Our World** — The world we wanted to make better is… 2. **The Problem** — The problem we noticed was… 3. **Our Idea** — We decided to build… 4. **How It Works** — Explain what the solution does and how someone would use it. 5. **See It in Action** — Show screenshots, demonstration video, inputs/outputs, or other evidence. 6. **What Happened?** — Explain what worked, what didn’t, where the team got stuck, what changed, and what surprised you. 7. **What’s Next?** — If we had more time, we would… ## How to publish with ChatGPT Sites 1. Ask ChatGPT (web or desktop app) or Codex to build it. Use the word “website” or type **@Sites**. 2. Test the preview it shows you. Ask for changes in plain words. 3. When you’re ready, say: **“Deploy this site and give me the URL.”** 4. Open **Share** → **Who has access** and choose who can open it. If you don’t see **Anyone on the internet**, ask a facilitator. 5. Test the link like a visitor: open it on a phone or in a signed-out browser. Publish an ugly first version in your first 30 minutes of building, then publish again every 30 minutes. The hard stop is your last publish. ## A prompt teams can give their AI ```text Read https://live.projectpaideia.com/llms.txt and the pages it links to. It is the plan for our Project Paideia Build-a-thon: the goal, the schedule, the three things we turn in, and help pages for when we get stuck. Be our teammate, not our replacement. Ask us questions, give us 2 or 3 options, and let us make the decisions. Don't do the thinking for us. Keep answers short, and remind us to publish every 30 minutes. Our team name: ___ The problem we picked: ___ What we're working on right now: ___ ``` ## Help radiators (all of them, in full) Each one is also a web page at https://live.projectpaideia.com/radiator/NN and a Markdown file at https://live.projectpaideia.com/radiator/NN.md. ## 01. How do I publish? > Tell ChatGPT to make your project a website and deploy it, set Who has access so anyone can open it, then check the link on a phone. Help radiator 01 of 19 for the Project Paideia AI Build-a-thon (Saturday, November 21, 2026). Group: Publish & Submit. Web page: https://live.projectpaideia.com/radiator/01 ### What’s happening? Right now only you can see your project. Publishing gives it a link anyone can open. Unfinished is fine. Publish early, publish often. ### Try this. 1. **Ask ChatGPT (or Codex):** “Make our project a website.” Say “website” or type @Sites. 2. **Test the preview.** Ask it to fix anything that’s off. 3. **Ask:** “Deploy this site and give me the URL.” 4. Open **Share** → **Who has access** → pick the widest option you’re allowed (**Anyone on the internet**, if you see it). 5. **Open the link on a phone.** It opens there? You’re live. ### Still stuck? No “Anyone on the internet” option, or the link won’t open on a phone? Flag a facilitator. Changed something? Ask it to deploy again, then check the link. ### Next step. Publish in your first 30 minutes of building, then every 30 minutes: 9:15, 9:45, 10:15, 10:45, 11:20 (afternoon: 2:15, 2:45, 3:15, 3:45, 4:20). Show a facilitator your live link. ### Prompt to paste into your AI ```text I'm at a student AI Build-a-thon and we need to publish our project as a website with ChatGPT Sites. Our project is ___. Make our project a website. Before you build it, ask me up to 3 questions about what it has to show. When the preview is ready, tell me what to test. When I say it's ready, deploy this site and give me the URL, then remind me to open Share → Who has access and pick the widest option I'm allowed. ``` ### Links - [ChatGPT Sites help: create a site](https://learn.chatgpt.com/docs/sites/creating-a-site) - [ChatGPT Sites help: publish and share](https://learn.chatgpt.com/docs/sites/publishing-and-sharing) ### Related help - [16. How do I submit everything?](https://live.projectpaideia.com/radiator/16.md) - [14. We’re running out of time.](https://live.projectpaideia.com/radiator/14.md) - [05. My code/project is broken.](https://live.projectpaideia.com/radiator/05.md) ## 02. I don’t know what to do next. > Pick one 10-minute move: build the smallest clickable piece, ask AI for 3 quick next steps, or watch someone use what you have. Help radiator 02 of 19 for the Project Paideia AI Build-a-thon (Saturday, November 21, 2026). Group: Ideas & Building. Web page: https://live.projectpaideia.com/radiator/02 ### What’s happening? You’re between steps. Everyone gets here. It doesn’t mean you’re doing it wrong. ### Try this. Pick ONE 10-minute move: 1. **Make it clickable.** What’s the smallest thing someone could see or tap? Build only that. 2. **Ask AI for a menu.** Paste: “Our problem is ___. We have ___ so far. Give us 3 next steps that each take under 10 minutes.” Pick one. 3. **Watch someone use it.** Show it to someone outside your team for 60 seconds. Fix the first thing that confuses them. ### Still stuck? Go back to your four lines (Our world is… / It would be better if… / The problem is… / We might build…). Read them out loud. What’s the next tiny piece of “we might build”? ### Next step. Flag a facilitator and say: “We have ___. We’re stuck on ___.” ### Prompt to paste into your AI ```text I'm at a student AI Build-a-thon and we're stuck. Our problem is ___. We have ___ so far. Give us 3 next steps that each take under 10 minutes, with one sentence on why each would help. Don't build anything yet. Ask us which one we pick. ``` ### Related help - [10. Our original idea isn’t working.](https://live.projectpaideia.com/radiator/10.md) - [17. Keeping the AI churning.](https://live.projectpaideia.com/radiator/17.md) - [13. We think we’re finished. What now?](https://live.projectpaideia.com/radiator/13.md) ## 03. AI doesn’t understand what I’m asking. > Tell the AI who it's for, what you want, what you have, and what done looks like, or ask it to ask you 3 questions first. Help radiator 03 of 19 for the Project Paideia AI Build-a-thon (Saturday, November 21, 2026). Group: Working with AI. Web page: https://live.projectpaideia.com/radiator/03 ### What’s happening? AI can’t see your screen or read your mind. It only knows what you type (or paste, or show it). ### Try this. Give it 4 things: 1. **Who** it’s for 2. **What** you want 3. **What you have** (paste the code or a screenshot) 4. **What “done” looks like** - ❌ “make a quiz” - ✅ “Make a 5-question quiz web page for 7th graders about recycling. Show one question at a time. At the end, show their score and a ‘try again’ button.” Or add: “Before you start, ask me 3 questions.” ### Still stuck? Start a fresh chat. Paste only what matters. Long, messy chats confuse AI. ### Next step. Read your prompt out loud to a teammate. If they don’t get it, the AI won’t either. Then flag a facilitator. ### Prompt to paste into your AI ```text I'm at a student AI Build-a-thon. I want ___. It's for ___. Here's what I have so far: ___. Done looks like: ___. Before you start, ask me 3 questions so you understand exactly what I mean. Then tell me your plan in 3 short steps and wait for my OK. ``` ### Related help - [04. AI gave me something wrong or weird.](https://live.projectpaideia.com/radiator/04.md) - [05. My code/project is broken.](https://live.projectpaideia.com/radiator/05.md) - [17. Keeping the AI churning.](https://live.projectpaideia.com/radiator/17.md) ## 04. AI gave me something wrong or weird. > Tell the AI exactly what's wrong, make it check itself, and check facts somewhere else; if anything is creepy, mean or unsafe, tell a facilitator right away. Help radiator 04 of 19 for the Project Paideia AI Build-a-thon (Saturday, November 21, 2026). Group: Working with AI. Web page: https://live.projectpaideia.com/radiator/04 ### What’s happening? AI guesses what sounds right. Sometimes it sounds right and is totally wrong. It can make up facts, links, and code. ### Try this. 1. **Tell it exactly what’s wrong:** “You said ___. That’s wrong because ___. Try again.” 2. **Make it check itself:** “How sure are you? What could be wrong with this?” 3. **Check facts somewhere else** before you put them in your project. ### Still stuck? Ask a smaller question. Break the big request into steps. Or try a different AI tool and compare. ### Next step. If it’s creepy, mean, or unsafe — stop and tell a facilitator right away. You won’t get in trouble. Otherwise, flag a facilitator. ### Prompt to paste into your AI ```text You said ___. That's wrong because ___. Try again. Then tell me how sure you are, what could still be wrong, and one way I can check it myself somewhere else. ``` ### Related help - [03. AI doesn’t understand what I’m asking.](https://live.projectpaideia.com/radiator/03.md) - [05. My code/project is broken.](https://live.projectpaideia.com/radiator/05.md) ## 05. My code/project is broken. > Copy the exact error, paste it to your AI with what you changed, change one thing at a time, and go back to the last version that worked if you need to. Help radiator 05 of 19 for the Project Paideia AI Build-a-thon (Saturday, November 21, 2026). Group: Ideas & Building. Web page: https://live.projectpaideia.com/radiator/05 ### What’s happening? Something changed, and now it doesn’t work. Broken is normal. Real builders spend most of their time right here. ### Try this. 1. **Copy the exact error** (or take a screenshot). 2. **Paste to AI:** “This worked until I ___. Now I see: [error]. Here’s my code: [code]. What’s wrong? Explain it like I’m new.” 3. **Change one thing at a time.** Test after each change. ### Still stuck? Go back in time: ask your AI to go back to the last version that worked. Or explain your code line by line to a teammate (or a rubber duck). Saying it out loud finds bugs. ### Next step. Flag a facilitator. Show them: what you expected, what happened, and the error. ### Prompt to paste into your AI ```text I'm at a student AI Build-a-thon and our project broke. This worked until I ___. Now I see this error: ___. Here's my code: ___. Explain what's wrong like I'm new. Then suggest the one smallest change to try first and wait for me to tell you what happened. If we can't fix it, help me go back to the last version that worked. ``` ### Related help - [04. AI gave me something wrong or weird.](https://live.projectpaideia.com/radiator/04.md) - [03. AI doesn’t understand what I’m asking.](https://live.projectpaideia.com/radiator/03.md) - [10. Our original idea isn’t working.](https://live.projectpaideia.com/radiator/10.md) ## 06. My team disagrees. > Give everyone one minute to explain, test the idea you can try fastest for 15 minutes, then look at what happened. Help radiator 06 of 19 for the Project Paideia AI Build-a-thon (Saturday, November 21, 2026). Group: Teamwork. Web page: https://live.projectpaideia.com/radiator/06 ### What’s happening? You all care about the project. That’s good. But you’re arguing instead of building. ### Try this. 1. **One minute each.** Each person explains their idea. No interrupting. 2. **Ask: “Which one can we test fastest?”** 3. **Try that one for 15 minutes.** Then look at what happened. You can try the other one next. ### Still stuck? Build both, small. Split into two mini-teams for 15 minutes, then show each other. Or do rock-paper-scissors. Seriously. Moving fast beats being perfect. ### Next step. Flag a facilitator to help you decide. Nobody gets in trouble for disagreeing. ### Prompt to paste into your AI ```text Our team has two ideas: ___ and ___. Don't pick for us. Ask each of us one question about our idea. Then tell us which one we could test fastest in 15 minutes and why, and what we should look for to decide. ``` ### Related help - [09. How do we divide up the work?](https://live.projectpaideia.com/radiator/09.md) - [18. How do we organize our team?](https://live.projectpaideia.com/radiator/18.md) - [11. We need to change our idea.](https://live.projectpaideia.com/radiator/11.md) ## 07. How do I share something with my team? (LocalSend) > Install LocalSend from localsend.org, get both devices on the event Wi-Fi, then click Send and have your teammate click Accept. Help radiator 07 of 19 for the Project Paideia AI Build-a-thon (Saturday, November 21, 2026). Group: Teamwork. Web page: https://live.projectpaideia.com/radiator/07 ### What’s happening? You need to get a file from one device to another. No email, no USB, no cloud. ### Try this. 1. **Get it:** go to localsend.org → download it for your device → install → open. 2. **Both open LocalSend.** Both on the event Wi-Fi. 3. Click **Send** → pick the file or folder. 4. Tap your teammate’s device name. 5. They click **Accept**. Done. ### Still stuck? Can’t see each other? Check you’re on the same Wi-Fi. Close and reopen LocalSend. If your computer asks to allow LocalSend through the firewall, click Allow. Rename your device to your first name (Settings) so you can find it. ### Next step. Sharing your project? Send its live link instead (radiator #1). Still stuck? Flag a facilitator. ### Prompt to paste into your AI ```text I need to send a file from my ___ to my teammate's ___ with LocalSend (localsend.org). Walk me through it one step at a time and wait for me to say done before the next step. If our devices can't see each other, ask me questions to figure out why. ``` ### Links - [Download LocalSend](https://localsend.org) ### Related help - [01. How do I publish?](https://live.projectpaideia.com/radiator/01.md) - [16. How do I submit everything?](https://live.projectpaideia.com/radiator/16.md) ## 08. What do I do while waiting for AI to finish? > Don't watch the spinner: write the next prompt, test, grab screenshots, check in, or outline what's next in a second AI chat, and keep one team notes doc. Help radiator 08 of 19 for the Project Paideia AI Build-a-thon (Saturday, November 21, 2026). Group: Working with AI. Web page: https://live.projectpaideia.com/radiator/08 ### What’s happening? AI is working. You’re watching. That’s dead time. Use it. ### Try this. Don’t watch the spinner. Pick one: 1. **Write the next prompt** so it’s ready to go. 2. **Test the last version.** Find what’s broken. 3. **Grab screenshots** for your slides. 4. **Check in:** “What are you working on? What do you need?” 5. **Write one line** in your team notes: what just happened? 6. **Open a second AI chat.** Outline what comes next, or your 7 slides. ### Still stuck? AI working more than 5 minutes? Stop it. Ask for something smaller. ### Next step. Make this a habit: every time you hit Enter, pick something from this list. Stay organized: keep one team notes doc with the plan, what’s done, what’s next, and prompts that worked. ### Prompt to paste into your AI ```text Our other AI chat is busy building ___. While it works, help me get ready for what's next. Ask me what's done and what's still missing. Then help me outline the next step (or our 7 slides) as a short list I can change. Don't write the slides for me. ``` ### Related help - [17. Keeping the AI churning.](https://live.projectpaideia.com/radiator/17.md) - [18. How do we organize our team?](https://live.projectpaideia.com/radiator/18.md) - [19. Can my AI take the screenshots?](https://live.projectpaideia.com/radiator/19.md) ## 09. How do we divide up the work? > Give everyone a real role (Driver, Tester, Storyteller, Scout), switch every 45 minutes, and run two AIs on two laptops. Help radiator 09 of 19 for the Project Paideia AI Build-a-thon (Saturday, November 21, 2026). Group: Teamwork. Web page: https://live.projectpaideia.com/radiator/09 ### What’s happening? One person types, everyone else watches. Everyone needs a real job. ### Try this. Pick roles. Switch every 45 minutes: - **Driver:** types and prompts the AI. - **Tester:** tries everything, finds bugs, tells the Driver. - **Storyteller:** screenshots, notes, and the 7 slides. - **Scout:** finds images, sounds, and facts; tries ideas in a second AI. Two laptops? Run two AIs on two different parts. ### Still stuck? List everything that’s left. Each person grabs one thing. Check back in 20 minutes. ### Next step. If someone has nothing to do, flag a facilitator. That’s a problem we want to fix. ### Prompt to paste into your AI ```text Our project is ___. There are ___ of us, and here's what's left to do: ___. Ask what each of us is good at first. Then suggest roles (Driver, Tester, Storyteller, Scout) and a first task for each person. We make the final call. ``` ### Related help - [18. How do we organize our team?](https://live.projectpaideia.com/radiator/18.md) - [06. My team disagrees.](https://live.projectpaideia.com/radiator/06.md) - [17. Keeping the AI churning.](https://live.projectpaideia.com/radiator/17.md) ## 10. Our original idea isn’t working. > Ask whether it's the idea or the build: idea problems go to radiator #11, build problems get smaller or faked. Help radiator 10 of 19 for the Project Paideia AI Build-a-thon (Saturday, November 21, 2026). Group: Ideas & Building. Web page: https://live.projectpaideia.com/radiator/10 ### What’s happening? You’ve tried and tried, and it’s not coming together. That isn’t failure. It’s data. ### Try this. Ask: **Is it the IDEA or the BUILD?** - **IDEA problem:** It doesn’t solve the problem, or nobody would use it → go to radiator #11. - **BUILD problem:** The tech is too hard → make it smaller, or fake the hard part (show a picture of it, or have a person do that part by hand). ### Still stuck? Paste to AI: “We’re trying to build ___ to solve ___. The part that isn’t working is ___. What’s a much simpler version we could finish in 30 minutes?” ### Next step. Write down what you tried. It goes on slide 6 (“What happened?”). Then flag a facilitator. ### Prompt to paste into your AI ```text We're trying to build ___ to solve ___. The part that isn't working is ___. Ask us 2 questions to figure out whether it's the idea or the build. Then suggest a much simpler version we could finish in 30 minutes, and let us choose. ``` ### Video - [When your idea isn't working](https://live.projectpaideia.com/video/10.mp4) (56 seconds) ### Related help - [11. We need to change our idea.](https://live.projectpaideia.com/radiator/11.md) - [02. I don’t know what to do next.](https://live.projectpaideia.com/radiator/02.md) - [14. We’re running out of time.](https://live.projectpaideia.com/radiator/14.md) ## 11. We need to change our idea. > Pick one move (shrink it, switch who it's for, switch the fix, or switch the problem), rewrite your 4 lines, and decide within 5 minutes. Help radiator 11 of 19 for the Project Paideia AI Build-a-thon (Saturday, November 21, 2026). Group: Ideas & Building. Web page: https://live.projectpaideia.com/radiator/11 ### What’s happening? You decided to change. Good call. Now do it fast so you still have time to build. ### Try this. Pick ONE move: - **Shrink it:** do one feature, not five. - **Switch who it’s for:** same tool, different people. - **Switch the fix:** same problem, new solution. - **Switch the problem:** same world, new problem. Then rewrite your 4 lines: Our world is… / It would be better if… / The problem is… / We might build something that… ### Still stuck? Set a 5-minute timer. Pick the first idea everyone can live with. It doesn’t have to be perfect. ### Next step. Tell a facilitator your new 4 lines. Keep your old work. It’s part of your story (slide 6). ### Prompt to paste into your AI ```text We need to change our idea. Our 4 lines were: Our world is ___. It would be better if ___. The problem is ___. We might build something that ___. Give us one option for each move: shrink it, switch who it's for, switch the fix, switch the problem. Don't choose for us. Then help us rewrite our 4 lines for the one we pick. ``` ### Related help - [10. Our original idea isn’t working.](https://live.projectpaideia.com/radiator/10.md) - [06. My team disagrees.](https://live.projectpaideia.com/radiator/06.md) - [02. I don’t know what to do next.](https://live.projectpaideia.com/radiator/02.md) ## 12. I need an image, video, audio file, or other asset. > Make it with AI or Canva for Education, find it free on Pixabay or Unsplash, record it yourself, or use a placeholder and keep building. Help radiator 12 of 19 for the Project Paideia AI Build-a-thon (Saturday, November 21, 2026). Group: Ideas & Building. Web page: https://live.projectpaideia.com/radiator/12 ### What’s happening? Your project needs a picture, icon, sound, or video, and you don’t have one. ### Try this. 1. **Make it:** ask your AI tool to create it. Describe the style, colors, and size. Or use Canva for Education. 2. **Find it free:** Pixabay (images, music, sound effects) or Unsplash (photos). 3. **Record it:** your laptop or phone camera and mic. ### Still stuck? Use a placeholder. Draw a box that says “picture of a dog here” and keep building. Swap it later. ### Next step. Write down where every asset came from (for your slides). No photos of real people without their OK. Not sure if something’s allowed? Ask a facilitator. ### Prompt to paste into your AI ```text I need a ___ (picture, icon, sound or video) for our project. It should show ___. Ask me about the style, colors and size first. Then help me write one clear request to make it, or tell me what to search for on Pixabay or Unsplash. Remind me to write down where it came from. ``` ### Links - [Pixabay (free images, music, sound effects)](https://pixabay.com) - [Unsplash (free photos)](https://unsplash.com) - [Canva for Education](https://www.canva.com/education/) ### Related help - [03. AI doesn’t understand what I’m asking.](https://live.projectpaideia.com/radiator/03.md) - [02. I don’t know what to do next.](https://live.projectpaideia.com/radiator/02.md) ## 13. We think we’re finished. What now? > Publish it, watch someone outside your team use it, fix the first thing that confused them, start your 7 slides, and add one fun thing. Help radiator 13 of 19 for the Project Paideia AI Build-a-thon (Saturday, November 21, 2026). Group: Time & Finishing. Web page: https://live.projectpaideia.com/radiator/13 ### What’s happening? It works! Nice. You still have time. Use it. ### Try this. 1. **Publish it now** (radiator #1). 2. **Hand it to someone outside your team.** Don’t explain it. Watch them use it. 3. **Fix the first thing that confused them.** 4. **Start your 7 slides** and grab screenshots. 5. **Add one thing that makes it fun.** ### Still stuck? Ask AI: “Here’s our project: ___. Who would use it? What would make it 10% better for them?” ### Next step. Show a facilitator. They have a bonus challenge card for you. ### Prompt to paste into your AI ```text Here's our project: ___. Who would use it? Ask us 2 questions about them, then suggest 3 small ideas that would make it 10% better for them, each under 20 minutes. We'll pick one. ``` ### Related help - [01. How do I publish?](https://live.projectpaideia.com/radiator/01.md) - [19. Can my AI take the screenshots?](https://live.projectpaideia.com/radiator/19.md) - [16. How do I submit everything?](https://live.projectpaideia.com/radiator/16.md) ## 14. We’re running out of time. > Stop adding and start finishing: publish now, make the one thing your demo needs work, and remember building stops at 11:20 a.m. or 4:20 p.m. Help radiator 14 of 19 for the Project Paideia AI Build-a-thon (Saturday, November 21, 2026). Group: Time & Finishing. Web page: https://live.projectpaideia.com/radiator/14 ### What’s happening? The clock is moving and you’re not where you wanted to be. That happens to every builder, every time. ### Try this. **Stop adding. Start finishing.** 1. **Publish what you have right now** (radiator #1). 2. **Pick the ONE thing** that has to work for your demo. Fix only that. 3. **Cut or fake the rest.** 4. **Building stops 40 minutes before the end of the session** (11:20 a.m. or 4:20 p.m.), so pay attention to the clock. Have screenshots ready. ### Still stuck? It’s OK if it’s not done. You’re expected to finish the Build-a-thon, not your project. Unfinished work is real work. ### Next step. Listen for time checks: 50 minutes left, 20 minutes left, 5 minutes left. At the stop time, everyone stops and publishes. ### Prompt to paste into your AI ```text Building stops in ___ minutes. Our project does ___, and ___ isn't working yet. Help us pick the ONE thing that has to work for our demo. Ask us questions first, then tell us what to cut or fake. Don't add new features. ``` ### Related help - [01. How do I publish?](https://live.projectpaideia.com/radiator/01.md) - [16. How do I submit everything?](https://live.projectpaideia.com/radiator/16.md) - [13. We think we’re finished. What now?](https://live.projectpaideia.com/radiator/13.md) ## 15. How do I capture screenshots or record the demo? > Use your computer's built-in keys to take screenshots or record your screen: Mac Shift + Command + 5, Windows Windows + Shift + S or R, Chromebook Ctrl + Shift + Show Windows. Help radiator 15 of 19 for the Project Paideia AI Build-a-thon (Saturday, November 21, 2026). Group: Publish & Submit. Web page: https://live.projectpaideia.com/radiator/15 ### What’s happening? You need proof of what you built: pictures and a video of it working (or almost working). ### Try this. - **Mac:** Shift + Command + 5 → pick screenshot or record. Stop recording: click ■ in the top menu bar. - **Windows:** Windows + Shift + S (screenshot). Windows + Shift + R (record with Snipping Tool). - **Chromebook:** Ctrl + Shift + Show Windows (the □|| key) → pick screenshot or record. - **Phone:** last resort. Hold it sideways and steady. ### Still stuck? Can’t find the file? Mac: Desktop. Windows: Pictures → Screenshots, or Videos → Screen Recordings. Chromebook: Files → Downloads. Want your voice in the recording? Turn on the microphone in the recording options. ### Next step. Take screenshots as you go, even of broken versions. They tell your story. Need help? Flag a facilitator. ### Prompt to paste into your AI ```text I'm on a ___ (Mac, Windows laptop, Chromebook or phone). I need to take screenshots and record a short demo of our project. Tell me the exact keys one step at a time and wait for me to say done. Then tell me where the file will be saved. ``` ### Related help - [19. Can my AI take the screenshots?](https://live.projectpaideia.com/radiator/19.md) - [16. How do I submit everything?](https://live.projectpaideia.com/radiator/16.md) ## 16. How do I submit everything? > Check your live link on a phone, name your files TeamName_Slides and TeamName_Walkthrough, upload both to Dropbox from live.projectpaideia.com/submit, add your live link in the short form, and show a facilitator the Received screen. Help radiator 16 of 19 for the Project Paideia AI Build-a-thon (Saturday, November 21, 2026). Group: Publish & Submit. Web page: https://live.projectpaideia.com/radiator/16 ### What’s happening? Time to turn in your 3 things. Five minutes. Easy. ### Try this. - [ ] **Live project link** works (open it on a phone). - [ ] **7-slide presentation** saved as TeamName_Slides. - [ ] **Recorded walkthrough** saved as TeamName_Walkthrough. Scan to submit (or open live.projectpaideia.com/submit) → upload both files to Dropbox → fill in the short form with your live link → wait for the “Received” screen. ### Still stuck? Upload slow? Send the slides first, then the video. Video won’t upload? Bring your laptop to the facilitator table and we’ll copy it with LocalSend. ### Next step. Show a facilitator your “Received” screen. Then you’re done. You built something! ### Prompt to paste into your AI ```text We're about to submit our Build-a-thon project. Make a checklist from these steps and ask us to confirm each one before the next: our live link opens on a phone; our files are named TeamName_Slides and TeamName_Walkthrough; both files are uploaded to the Dropbox link on live.projectpaideia.com/submit; the short form there has our live link; we see the Received screen. ``` ### Video - [How to submit everything](https://live.projectpaideia.com/video/16.mp4) (58 seconds) ### Links - [Submit page (Dropbox upload + live-link form)](https://live.projectpaideia.com/submit) - [Dropbox file request for slides and walkthrough videos](https://www.dropbox.com/request/uc0ehthx8amk0ye3vrlb) ### Related help - [01. How do I publish?](https://live.projectpaideia.com/radiator/01.md) - [15. How do I capture screenshots or record the demo?](https://live.projectpaideia.com/radiator/15.md) - [19. Can my AI take the screenshots?](https://live.projectpaideia.com/radiator/19.md) ## 17. Keeping the AI churning. > Keep your AI busy: have the next prompt ready, give it bigger jobs, run two AIs on two laptops, and ask it for the plan. Help radiator 17 of 19 for the Project Paideia AI Build-a-thon (Saturday, November 21, 2026). Group: Working with AI. Web page: https://live.projectpaideia.com/radiator/17 ### What’s happening? Your AI is sitting idle while you figure things out. The best teams keep their AI busy the whole time. ### Try this. 1. **Have the next prompt ready** before this one finishes. 2. **Give it bigger jobs:** “Build ___, then test it, then tell me what’s still broken.” 3. **Two laptops = two AIs** on two different parts. 4. **Ask it for the plan:** “What should we build next? Write the next 3 prompts for me.” 5. **When it finishes:** check it, then send the next prompt in under a minute. ### Still stuck? Out of ideas? Ask it to improve something: “Make this easier for a 7th grader to use.” or “Find 3 bugs in this and fix them.” ### Next step. Facilitators will walk by and ask, “Is your AI working right now?” Have a yes. ### Prompt to paste into your AI ```text Here's our project and what's done so far: ___. What should we build next? Write the next 3 prompts for us, explain in one line why each one matters, and let us choose the order. ``` ### Video - [Keep your AI busy](https://live.projectpaideia.com/video/17.mp4) (80 seconds) ### Related help - [08. What do I do while waiting for AI to finish?](https://live.projectpaideia.com/radiator/08.md) - [02. I don’t know what to do next.](https://live.projectpaideia.com/radiator/02.md) - [09. How do we divide up the work?](https://live.projectpaideia.com/radiator/09.md) ## 18. How do we organize our team? > Give everyone a job in the first few minutes, pick a Timekeeper, write a one-line plan with your top 3 tasks, check in at every publish checkpoint, and swap jobs every 45 minutes. Help radiator 18 of 19 for the Project Paideia AI Build-a-thon (Saturday, November 21, 2026). Group: Teamwork. Web page: https://live.projectpaideia.com/radiator/18 ### What’s happening? Everyone needs a job. Teams that get organized in the first few minutes spend the rest of the time building. ### Try this. 1. **Give everyone a job** in the first few minutes. Role ideas: radiator #9. 2. **Pick a Timekeeper.** They call out every publish checkpoint and the stop time (11:20 a.m. or 4:20 p.m.). 3. **Write a one-line plan** and your top 3 tasks where everyone can see them. 4. **Check in at every publish checkpoint:** What’s done? What’s next? Who’s stuck? 5. **Swap jobs** every 45 minutes so everyone gets a turn. ### Still stuck? Someone has nothing to do? Hand them the next task on your list. Can’t agree on jobs? Pick fast. You’ll swap in 45 minutes anyway. ### Next step. Everyone should be able to say their job in one sentence. If someone can’t, flag a facilitator. ### Prompt to paste into your AI ```text We're a team at a 4-hour AI Build-a-thon. Our project is ___. There are ___ of us, and here's what each of us is good at: ___. Ask us questions first. Then suggest a job for each person, who should be Timekeeper, a one-line plan, and our top 3 tasks. We make the final call. ``` ### Related help - [09. How do we divide up the work?](https://live.projectpaideia.com/radiator/09.md) - [06. My team disagrees.](https://live.projectpaideia.com/radiator/06.md) - [08. What do I do while waiting for AI to finish?](https://live.projectpaideia.com/radiator/08.md) ## 19. Can my AI take the screenshots? > Ask your AI to screenshot your live site at laptop and phone size for your slides, and if it can't, take them yourself with radiator #15. Help radiator 19 of 19 for the Project Paideia AI Build-a-thon (Saturday, November 21, 2026). Group: Publish & Submit. Web page: https://live.projectpaideia.com/radiator/19 ### What’s happening? You need screenshots for your slides. Your AI might be able to take them while you keep building. ### Try this. 1. **Ask your AI:** “Take screenshots of our live site for our slides: the home page, ___, and ___. Make each one at laptop size and phone size. Save them as image files I can put in slides.” 2. **Check every screenshot.** Right page? Easy to read? Ask for a retake if not. 3. **Put the best ones on slide 5** (See It in Action). ### Still stuck? AI says it can’t take screenshots? No problem. Take them yourself: radiator #15 shows the keys. ### Next step. Ask for fresh screenshots after each publish checkpoint, so your slides show how it changed. Need help? Flag a facilitator. ### Prompt to paste into your AI ```text Take screenshots of our live site for our slides: the home page, ___, and ___. Make each one at laptop size and phone size. Save them as image files I can put in slides. If you can't take screenshots, tell me, and tell me which keys to use on my ___ (Mac, Windows or Chromebook) instead. ``` ### Related help - [15. How do I capture screenshots or record the demo?](https://live.projectpaideia.com/radiator/15.md) - [16. How do I submit everything?](https://live.projectpaideia.com/radiator/16.md) - [13. We think we’re finished. What now?](https://live.projectpaideia.com/radiator/13.md)