devpost-reconlisted

# Reading a Devpost hackathon The rules page is not where most of the decisive information lives. ## Page anatomy | Page | What only it has | |---|---| | `/` | Prizes and tracks with cash values, the judging panel, participant count, the criteria in summary | | `/rules` | Dates with timezones, eligibility exclusions, submission requirements, tie-breaking, bonus mechanics, IP terms | | `/resources` | Sponsor and partner sections, and the FAQ | | `/updates` | Host clarifications posted after launch — **these outrank the original rules text** | | `/project-gallery` | Nothing, during a live hackathon. See below. | ## The two places requirements hide **Partner and sponsor sections on `/resources`.** These read like documentation and function like requirements. A sponsor listing the exact span attributes their dashboard expects has just told you what a judge will check for. Extract them with a verbatim quote — a finding that can be traced to the host's own words is the one that survives an argument. **The FAQ.** Hosts routinely put rubric language there that never appears on the rules page: what will score poorly, what a diagram should contain, how AI-assisted code will be treated. Capture it in `host_guidance` verbatim. ## The gallery is empty and that is not a bug Devpost project galleries stay **empty until winners are announced**. During the submission period you cannot see how many people entered a track, so per-track crowding is unobservable. Record `gallery_available