FinePrint: an agent that checks your hackathon entry against the rules it reads

FinePrint is a tool designed to help hackathon participants ensure they are following the rules of the competition. The rules for a hackathon can sometimes be conflicting, and a single missed line can lead to a project being disqualified. FinePrint simplifies this process by reading a Sanity Knowledge Base built from the official rules and proposing facts with exact quotes from user questions. It then calls a typed checker over structured requirement records.

The tool displays the rules it read, the facts it accepted, and every tool call it made, allowing the user to see exactly what the requirements are and what the results are. FinePrint can find specific sentences related to entry periods, but it cannot determine which conditions block development or which conditions are still allowed. When there are discrepancies between official pages, FinePrint marks the issue as "Rules unclear" and provides a precise question to ask the organizer.

FinePrint checks 19 Sanity requirements and 18 GIBC requirements, comparing events to keep team size and development date consistent across both. It labels any imported events as "Imported from zero-origin.devpost.com, not reviewed" and keeps them separate from the Sanity dataset. Saved reports retain the requirements and sources used at the time of the check, and when a new curated pack is published, FinePrint identifies changes in requirements and follows source references to affected findings.

To use FinePrint, simply open a review desk, enter the team size and development date, and ask FinePrint for a review. If there are any issues, the tool will indicate whether they are supported, blocked, missing a fact, unclear, or not applicable. Users can also change facts and see which findings are affected. FinePrint can check any public rules page, and its requirements are mapped to a fixed fact vocabulary, ensuring accuracy and consistency.