# Burn Your Code — Official Rules (In-Person Hackathon)

## 1) Overview & Key Facts

- **Event Name:** Burn Your Code (the “Hackathon”)

- **Organizer/Host:** Burning Heroes Founders Association (BHFA) in partnership with **Entrepreneur First (EF)**

- **Date & Time:** **October 4, 2025, 9:00 AM – 7:00 PM PT**

- **Venue:** Folsom 501, San Francisco, CA

- **Format:** In-person only

- **Theme:** Radical builds; ship a bold demo

- **Website / Registration:** **https://luma.com/oiialrj7**

- **Submission Method:** Live demo + repo link ([GitHub/GitLab/Devpost/Form link])

- **Contact for Rule/CoC Questions:** **Fayeeza Shaikh — fayeeza.shaikh@joinef.com**

## 2) Eligibility

- **Age:** 18+ (minors must not participate unless Organizer explicitly permits with a signed parental/guardian consent acceptable to Organizer and venue).

- **Residency:** Open to individuals legally permitted to be in the U.S. during the event; void where prohibited.

- **Teams:** 1–5 people per team (solo allowed).

- **Conflicts:** Judges, their employees/contractors, or anyone with insider access to judging decisions may not compete for prizes. Mentors may advise teams but cannot judge teams they mentored.

- **Restrictions:** Government-sanctioned countries/entities/individuals may be excluded. Organizer may disqualify anyone violating these Rules or the Code of Conduct.

## 3) Registration & Attendance

- Register before capacity is reached. Onsite check-in required with photo ID.

- If you leave the venue for an extended period, you may return (subject to capacity and security).

- **Dress code (optional, for fun):** Wear something that stands out—neon, fur, sequins, etc.

## 4) Building Rules (What You Can Make)

- **Start Time:** All coding/design for your submission must occur **after the kickoff** on event day.  

  - You **may** bring prior art, libraries, prompts, datasets, boilerplates, and your own APIs.  

  - You **must** build **new functionality** during the event that is central to your submission.

- **Permitted Tech:** Any language, framework, model, SDK, or API. Sponsor prize tracks may require their specific API/SDK (see Prize Terms).

- **Data & Content Rights:** Use only assets/data you have the legal right to use (open-source with proper licenses, your originals, or properly licensed third-party assets). No unlawful, infringing, or unsafe content.

- **Hardware:** Personal devices are allowed. Any loaner devices must be returned as instructed.

## 5) Submission Requirements

To be eligible for judging/prizes, submit by the deadline announced at kickoff and on signage:

- **Live Demo:** 3–4 minutes on stage (Organizer may timebox).  

- **Repo/Link:** Public GitHub/GitLab repo or an accessible link (include build/run instructions).  

- **Readme:** What it does, how to run, which APIs/models you used, and what was built during the event.  

- **Optional Video/GIF:** ≤ 2 minutes (helpful for social sharing/judging).  

- **Access:** Provide demo creds/test accounts if needed (use dummy data, not personal secrets).  

- **One Submission per Team.** Individuals cannot submit for multiple teams.

Organizer may reject incomplete or inaccessible submissions.

## 6) Judging & Awards

### Judging Criteria (all tracks)

1. **Radical Idea** — Bold, surprising, “impossible-until-it-works.”  

2. **Technical Execution** — Real shipping quality (bonus: deployed repo, TestFlight/App Store build, working web app).  

3. **Demo & Virality** — Clear, compelling demo people want to share on X/Twitter.

Judges score independently; highest combined scores win. Tie-breakers at Organizer’s discretion.

### Prize Tracks & Nominations

- **Overall Winner** — **$500 cash**  

- **Top-1% Builder** — Up to 5 recipients: limited **400gsm “Burn Like a Hero” hoodies**  

- **Best use of Apify** — **$1,000 cash** (must integrate Apify meaningfully)  

- **🎥 Best Generative Video Product (Higgsfield Award)** — **$500 cash** (must use Higgsfield API)  

- **Rork Award (Best Vibecoded Mobile Product)** — Rork swag + annual membership + X feature + 1-1 mentorship by an a16z speedrun-backed startup  

- **🔊 Voice (VAPI)** — **Prize TBA** (must use VAPI in a meaningful way)  

- **Omi Track** — **Omi devices** for track winners (build an app/feature for Omi Apps Marketplace)  

- **Collectible Stickers** — Up to 50 demoing team members for extraordinary results

**Prize Terms:**  

- Each track may have additional verification to confirm required API/SDK usage.  

- Non-cash rewards have no cash alternative and are non-transferable.  

- Taxes and any fees are the sole responsibility of winners. Winners may need to complete a W-9/W-8BEN.  

- Organizer may substitute a prize of equal/greater value if unavailable, or withhold/modify prizes if necessary.

## 7) Schedule (subject to change)

- **9:00 AM** — Check-in & Tea Ceremony  

- **10:00 AM** — Kickoff & Team Formation  

- **10:30 AM – 5:00 PM** — Build time & mentor sessions  

- **1:00 PM** — Lunch (Slavic food)  

- **2:00–2:30–3:00 PM** — Sound Healing / Focus sessions  

- **5:00 – 7:00 PM** — Final demos & judging  

- **7:00 PM** — Awards & closing

## 8) Mentors & Support

Mentors from OpenAI, Anthropic, Google, Vercel, 21st.dev, Rork, and others may advise. Advice is optional and non-binding; teams make their own decisions.

## 9) Ownership & Licenses

- **You own your project/IP.**  

- By submitting, you grant Organizer and Sponsors a **non-exclusive, worldwide, royalty-free license** to display your team name, project name, logos, screenshots, short clips, and demo excerpts for event marketing, recaps, and future hackathon promotion (crediting you).  

- Sponsor-track APIs/SDKs remain under their respective licenses/ToS. You are responsible for compliance.

## 10) Privacy

- Organizer collects basic registration and submission info for event operations.  

- Sponsor outreach: **opt-in only** (collect explicit consent during check-in or submission form).

## 11) Safety, Security & Venue Rules

- Follow all posted venue rules and staff instructions.  

- **No open flames, weapons, or hazardous materials.**  

- No illegal drugs. Alcohol, if present, is served only by venue/caterer and only to 21+ with valid ID.  

- Respect quiet areas and shared spaces; keep aisles/exits clear.

## 12) Publicity & Media

- The event is photographed/recorded. See Code of Conduct for photography consent norms and opt-out process.

## 13) Disqualification

Organizer may warn or disqualify teams for: rule violations, plagiarism, falsified demos, unsafe behavior, or Code of Conduct violations. Severe cases may be reported to venue security or law enforcement.

## 14) Changes & Force Majeure

Organizer may modify schedule, judging, or prizes if needed for safety/fairness/availability, and will communicate material changes promptly. If the event cannot run as planned due to causes beyond Organizer’s control, Organizer may cancel, reschedule, or adjust format.

## 15) Liability Release

To the maximum extent permitted by law, participants release Organizer, venue, and sponsors from claims arising from participation, except for claims caused by Organizer’s gross negligence or willful misconduct.

## 16) Governing Law & Disputes

These Rules are governed by the laws of the State of California, without regard to conflicts of laws. Venue for disputes shall be in **San Francisco, CA**. Where prohibited, these Rules are void.

---

# Code of Conduct (In-Person)

**Applicability:** All participants, attendees, volunteers, mentors, judges, sponsors, vendors, and staff (“Participants”) at **Burn Your Code** must abide by this Code of Conduct (CoC) at the venue and related social events, online channels, and during any Hackathon-related communications.

## Our Commitment

We are dedicated to a **safe, inclusive, harassment-free** environment for everyone, regardless of gender, gender identity/expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, nationality, religion, political views, prior hackathon experience, computing experience, or chosen tech stack.

We **do not tolerate harassment** in any form. Sexual language and imagery are not appropriate in talks, demos, workshops, hacks, or social media tied to the Hackathon.

## Prohibited Conduct (non-exhaustive)

- Offensive verbal comments or imagery related to protected characteristics above.  

- Harassment, intimidation, stalking, doxxing, sustained disruption of sessions.  

- Inappropriate physical contact; unwelcome sexual attention.  

- Non-consensual photography/recording in contexts of expected privacy (bathrooms, rest areas).  

- Advocating for, or encouraging, any of the above behaviors.

## Photography & Recording

- Photography and filming are part of the event; **opt-out is respected**.  

- **Opt-out mechanism:** Participants may request a **“no-photos” indicator** (e.g., special lanyard/sticker) at check-in. If someone indicates “no photos,” do not photograph or record them.  

- Always ask before close-ups. Comply immediately with any request to stop.

## Reporting & Response

- If you experience or witness a CoC issue, **contact staff immediately**:  

  - **On-site:** find anyone with a STAFF badge  

  - **Email:** **fayeeza.shaikh@joinef.com (in case of emergency)**  

- Staff can help with: safe escorts, separating parties, contacting venue security or law enforcement, and other support.  

- **Enforcement:** Organizer may take any action deemed appropriate, including verbal warning, removal from the venue without refund, disqualification from prizes, or contacting authorities.

## Inclusion & Accessibility

- Request reasonable accommodations at **fayeeza.shaikh@joinef.com** before or during the event; we’ll make good-faith efforts to assist.

## Responsibility of Sponsors & Partners

- Sponsor materials, booths, and staff **must not** use sexualized imagery, attire, or create a sexualized environment. The same standards apply to swag, demos, and stage content.

## Scope

This CoC applies at the venue, workshops, mentor sessions, demo stage, after-events officially associated with the Hackathon, and official online channels.

**By attending, you agree to follow this Code of Conduct.**