skills/review-hackathon-rules/references/placeholder-rules.md

# Provisional Rules

Use this file as the draft source for the MVP fairness gate. It is intentionally provisional.

## Fairness Notice

Every participant should have access to the same essential information about eligibility, judging, required deliverables, deadlines, and submission expectations.

Do not present this draft as final legal copy.

## Eligibility

- Official eligibility requirements should be copied from Devpost before launch.
- Restricted jurisdictions should be copied from Devpost before launch.
- Age requirements should be copied from Devpost before launch.
- Team policy should be copied from Devpost before launch if teams are supported.

## Contest Dates

- Official start date and time should be copied from Devpost before launch.
- Official submission deadline should be copied from Devpost before launch.
- Official judging period should be copied from Devpost before launch.
- Official winner announcement date should be copied from Devpost before launch.

## What To Build

Draft MVP copy:

Build a new application with AI capabilities and ship it with Codex. The strongest entries should feel like products, not prompt wrappers. They should demonstrate a real user workflow, a credible problem choice, and a clear reason the application is better because of model capabilities.

## What To Submit

Draft MVP checklist:

- A short text write-up explaining how AI capabilities are central to the product
- A public product or demo link when available
- A public code repository link when required by the official event page
- A short demo video when required by the official event page
- Testing instructions when a judge needs setup context

## Judging Criteria

Provisional sample structure modeled on a Devpost-style hackathon. Replace with approved values before launch.

- Technical execution: official weight to be copied from Devpost before launch
- Potential impact: official weight to be copied from Devpost before launch
- Innovation and wow factor: official weight to be copied from Devpost before launch
- Presentation and demo quality: official weight to be copied from Devpost before launch

## Originality And Use Restrictions

- Projects should be new for the contest period or follow the official originality rule
- Participants must have the right to use any third-party assets, APIs, or data they include
- Submission materials must not contain prohibited, unlawful, hateful, or infringing content
- Testing access expectations should be stated clearly for judges

## Common Submission Blockers Later

Use this as practical guidance in the review screen.

- Eligibility details left unverified against the official Devpost page
- Required submission fields missing or only partially completed
- Demo, repo, or testing instructions not usable by judges
- Third-party assets, datasets, or integrations without clear usage rights
- Projects that mention AI but do not show why model capabilities are central to the product

## Questions And Escalation

- Official hackathon manager contact should be copied from Devpost or the event team before launch.
- Official support path should be copied from Devpost or the event team before launch.