This file summarizes the event handbook published through the San Francisco participant portal, checked September 11, 2026. Choose your city on the global event page, then consult its portal and handbook for registration requirements, the deadline, and any organizer updates. Your local organizer's current rules take precedence; do not infer additional eligibility restrictions.
- The submitted project must be a new build created during the official hackathon period.
- The project's core functionality must be built during the event.
- Existing templates, reusable components, libraries, prompts, and starter code may be used as building blocks.
- A pre-existing project may not be resubmitted, or extended and entered as a new hackathon project.
- The team must be able to explain which parts were created during the hackathon.
- Any technical stack is allowed. Eligible projects enter the same global competition.
For this repository, the supplied apps, tests, example prompts, and integrations are inherited starter code. Launching or renaming a supplied demo does not establish a new project. Capture the team's original core interaction and identify its implementation.
| Deliverable | What to prepare |
|---|---|
| Project title | The team's project name |
| Written description | What it does, who it is for, and why the surrounding context matters |
| Public GitHub repository | Working code and instructions to run it |
| Two-minute demonstration video | A visible, complete interaction in the chosen environment |
| Public social media post | A project post tagging the event partners according to organizer instructions |
Complete the submission by the deadline shown in your city's participant portal. Do not substitute a guessed timezone or a deadline copied from another city's schedule.
Use SUBMISSION.md as the team's fill-in checklist. It adds practical preparation guidance to the required deliverables:
- Record what was inherited and what was created during the event. Do not fabricate timestamps or claim starter code as event work.
- Write a clean-clone quickstart with the credentials and processes actually needed.
- Run the relevant checks and demonstrate the live integration used in the video.
- Label sample data, temporary state, and account-dependent behavior accurately. An approval is not evidence that an action executed; show the actual result.
- Exclude credentials and sensitive data from the public repository, logs, screenshots, and video.
- Prepare the title, description, repository link, demo link, and social post for the team. Publishing or submitting is a separate action requiring the team's instruction.
The four official judging criteria are in hackathon-overview.md; the same criteria appear in the submission evidence checklist.