# Project Paideia AI Build-a-thon: build day

> 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.

Saturday, November 21, 2026 · Sorensen Center room 206 A/B/C, Utah Valley University, Orem · Morning session 8 a.m. to noon · Afternoon session 1 to 5 p.m.

## 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.

## 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 slides

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…

## 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.

## Stuck? Help radiators

### Publish & Submit

- [01. How do I publish?](https://live.projectpaideia.com/radiator/01.md): 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.
- [15. How do I capture screenshots or record the demo?](https://live.projectpaideia.com/radiator/15.md): 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.
- [16. How do I submit everything?](https://live.projectpaideia.com/radiator/16.md): 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.
- [19. Can my AI take the screenshots?](https://live.projectpaideia.com/radiator/19.md): 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.

### Ideas & Building

- [02. I don’t know what to do next.](https://live.projectpaideia.com/radiator/02.md): Pick one 10-minute move: build the smallest clickable piece, ask AI for 3 quick next steps, or watch someone use what you have.
- [05. My code/project is broken.](https://live.projectpaideia.com/radiator/05.md): 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.
- [10. Our original idea isn’t working.](https://live.projectpaideia.com/radiator/10.md): Ask whether it's the idea or the build: idea problems go to radiator #11, build problems get smaller or faked.
- [11. We need to change our idea.](https://live.projectpaideia.com/radiator/11.md): 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.
- [12. I need an image, video, audio file, or other asset.](https://live.projectpaideia.com/radiator/12.md): 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.

### Working with AI

- [03. AI doesn’t understand what I’m asking.](https://live.projectpaideia.com/radiator/03.md): 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.
- [04. AI gave me something wrong or weird.](https://live.projectpaideia.com/radiator/04.md): 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.
- [08. What do I do while waiting for AI to finish?](https://live.projectpaideia.com/radiator/08.md): 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.
- [17. Keeping the AI churning.](https://live.projectpaideia.com/radiator/17.md): 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.

### Teamwork

- [06. My team disagrees.](https://live.projectpaideia.com/radiator/06.md): Give everyone one minute to explain, test the idea you can try fastest for 15 minutes, then look at what happened.
- [07. How do I share something with my team? (LocalSend)](https://live.projectpaideia.com/radiator/07.md): Install LocalSend from localsend.org, get both devices on the event Wi-Fi, then click Send and have your teammate click Accept.
- [09. How do we divide up the work?](https://live.projectpaideia.com/radiator/09.md): Give everyone a real role (Driver, Tester, Storyteller, Scout), switch every 45 minutes, and run two AIs on two laptops.
- [18. How do we organize our team?](https://live.projectpaideia.com/radiator/18.md): 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.

### Time & Finishing

- [13. We think we’re finished. What now?](https://live.projectpaideia.com/radiator/13.md): 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.
- [14. We’re running out of time.](https://live.projectpaideia.com/radiator/14.md): 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.

## Give your AI the plan

```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: ___
```

More: [llms.txt](https://live.projectpaideia.com/llms.txt) · [llms-full.txt](https://live.projectpaideia.com/llms-full.txt) · [Projects](https://live.projectpaideia.com/projects) · [Submit](https://live.projectpaideia.com/submit)
