FinePrint.
Path OneBuilt for the DEV x Sanity Challenge

A great project.
One overlooked rule.

Ask whether your hackathon project qualifies. FinePrint quotes your facts, checks each rule and shows the source.

Start a free reviewSee a recorded run
Ask FinePrint
Example scenario

I’m planning two entries in the same path.

Read the Knowledge Base outlineentry limits and prizessource authoritysubmissions/artifacts
Rules unclear

The status is unclear because the two official sources disagree on how many entries a participant may submit within one path. The FAQ states exactly one submission per path is allowed, while the contest rules state there is no limit on the number of entries during the entry period.

See the two sources

Recorded source explanation · September 20, 2026
Replay is an illustration. No live request is made here.

Rule and sourceIllustrative project
Entry eligibilityDevelopment startBlocked

The example started in August. The official entry period began September 18.

Entry development began2026-08-23
“development of your Entry was started during, and not prior to, the Entry Period”
General contest rulesCaptured 2026-09-20

The rules FinePrint checks today

Curated requirements
37
Events with dated sources
2
Regression scenarios passing
42/42
  • Team size
  • Age of every team member
  • Residency restrictions
  • DEV membership
  • Organizer affiliations
  • Existing project or new entry?
  • Development start
  • Credit for reused material
  • Substantial new work
  • Sanity Context + Knowledge Base
  • Path Two build requirements
  • Entries in the same path
  • A post for each path
  • Language for prize judging
  • Receiving prizes in both paths
  • Access for judges
  • Sanity project details
  • Published submission
  • Submission window
  • GIBC: Team size
  • GIBC: Student participation
  • GIBC: Minimum age
  • GIBC: Guardian permission
  • GIBC: Residency restrictions
  • GIBC: Organizer affiliations
  • GIBC: One submitting team
  • GIBC: Development start
  • GIBC: New entry
  • GIBC: Previous hackathon entry
  • GIBC: Open Invention prototype
  • GIBC: Source and setup
  • GIBC: Demo video
  • GIBC: Screenshots
  • GIBC: Devpost materials
  • GIBC: English materials
  • GIBC: AI coding disclosure
  • GIBC: Submission deadline

Requirement titles from the Sanity Challenge and GIBC V2 Open Invention packs. The scenarios are authored regression cases, not an accuracy study.

An answer is only useful if you can check it.

Your project facts are declarations. The rules are quotes. FinePrint keeps the two apart and shows how each finding was reached.

Two official sources. Two different answers.

FinePrint keeps both claims in view and gives you the question to ask the organizer.

Challenge brief & FAQ
“No, only one submission per path is allowed.”
Official source snapshot, 2026-09-20
Sanity contest rules
“There is no limit on the number of Entries you may submit during the Entry Period.”
Official source snapshot, 2026-09-20
Rules unclear

Which submission limit governs multiple entries in the same path: the FAQ limit or the event rules?

Every finding opens to its source.

See the fact that was used, the official wording and when it was captured.

Illustrative project, real rule text.

Change one fact. See what follows.

Reusing components and resubmitting an app are different situations.

What existed before the event?
Development beganAugust 23, 2026Unchanged
  • Existing project or new entry?Blocked
  • Development startBlocked
  • Credit for reused materialSupported

Illustrative facts, computed by FinePrint’s rule checker.

Same project. Different rulebooks.

A five-person team fits GIBC’s team-size rule and exceeds Sanity’s limit. These are recorded agent runs with their source reads.

Start a review, then compare events

Five people on the team.

Sanity · Path OneBlocked

Rule check · source pack 2026-09-20.1

Inspect source reads · 12.1s

Sanity Context entries retrieved in this run, linked to structured records:

sanity_challenge/entry_limits_and_prizes
  • Challenge brief & FAQ source
  • Receiving prizes in both paths requirement
  • Language for prize judging requirement
  • Sanity Context + Knowledge Base requirement
  • Path Two build requirements requirement
  • Entries in the same path requirement
sanity_challenge/eligibility
  • Residency restrictions requirement
  • Organizer affiliations requirement
  • Age of every team member requirement
  • DEV membership requirement
  • Team size requirement
Inspect 7 recorded steps
  1. Read Sanity Context outline7 entries in the outline
  2. Model round 1Selected Knowledge Base entries
  3. Read Knowledge Base entrysanity_challenge/eligibility2,554 characters
  4. Read Knowledge Base entrysanity_challenge/entry_limits_and_prizes3,876 characters
  5. Model round 2Requested a facts and rules check
  6. Check structured requirements19 requirements checked; 2 quoted facts accepted
  7. Model round 3Wrote the cited answer
GIBC V2 · Open InventionSupported

Rule check · source pack 2026-09-22.1

Inspect source reads · 9.2s

Sanity Context entries retrieved in this run, linked to structured records:

gibc_v2/eligibility
  • GIBC: Guardian permission requirement
  • GIBC: Student participation requirement
  • GIBC: Residency restrictions requirement
  • GIBC: Team size requirement
  • GIBC: Organizer affiliations requirement
  • GIBC: Minimum age requirement
gibc_v2/submission
  • GIBC: Submission deadline requirement
  • GIBC: Devpost materials requirement
  • GIBC: Screenshots requirement
  • GIBC: Demo video requirement
  • GIBC: Source and setup requirement
  • GIBC: English materials requirement
  • GIBC: AI coding disclosure requirement
  • GIBC: Open Invention prototype requirement
  • GIBC V2 overview source
  • GIBC V2 · Open Invention competition
  • GIBC V2 official rules source
Inspect 7 recorded steps
  1. Read Sanity Context outline7 entries in the outline
  2. Model round 1Selected Knowledge Base entries
  3. Read Knowledge Base entrygibc_v2/eligibility1,091 characters
  4. Read Knowledge Base entrygibc_v2/submission3,668 characters
  5. Model round 2Requested a facts and rules check
  6. Check structured requirements18 requirements checked; 2 quoted facts accepted
  7. Model round 3Wrote the cited answer

Recorded September 22, 2026 · no live request. Four authored questions, not an accuracy benchmark. These selected checks do not establish overall eligibility.

Bring the code. Find the evidence.

Review a public GitHub repository against Sanity or GIBC judging criteria. Each finding points to inspected lines. It helps you prepare; it does not predict a score.

Review your GitHub repository
  • Fixed commitThe default branch is pinned before any file is read.
  • 10 filesUp to 60,000 characters of readable text per review.
  • Line citationsCitations that do not match inspected lines are discarded.

Checking a different hackathon?

Paste its rules link. FinePrint imports the rules as a separate pack and labels it as imported. No one has reviewed it against the official pages, so treat every finding as a starting point.

Start a review
  • Sanity ChallengeCurated, captured 2026-09-20
  • GIBC V2 Open InventionCurated, captured 2026-09-22
  • A rules link you pasteImported, not reviewed

Before you rely on a report

Is a FinePrint report an eligibility decision?

No. A report shows which rules apply to the facts you declared and what supports each finding. Only the organizer decides eligibility. Unknown facts stay unknown.

Which events are covered?

Curated rule packs for the DEV Sanity Challenge and GIBC V2 Open Invention, each dated to when its official sources were captured. Other tracks and sponsor prize conditions are outside coverage.

Where is my review saved?

In this browser. No account is needed. Download a facts backup to move to another browser, or a Markdown report to keep the findings.

What does the AI see?

Ordinary rule checks do not use AI. When you ask a question, the question and the facts you include are sent to the model, which reads the Sanity Knowledge Base. A repository review sends the selected files. Your reviews are never written to the public dataset.

Before you hit submit, read the FinePrint.

Create a review. Keep the sources and your next steps together.

Start a free review