MAKE IT YOURS. KEEP IT HONEST.
Room to experiment. A few clear rules. These are the working rules for OffScript’s first edition; final event details and submission instructions will be shared before the event.
01 / Teams + building
- Teams consist of 1–4 high school students. Solo builders are welcome.
- The main project must be built during the event. Brainstorming beforehand is allowed.
- Existing libraries, frameworks, APIs, models, and boilerplate are allowed.
- Significant pre-existing work must be disclosed. Clearly explain what your team built during OffScript.
02 / Honest work
- No plagiarism. Credit work, resources, and contributions accurately.
- Teams must honestly represent what they built, what works, and what does not.
- Never fabricate users, testing, functionality, or contributions.
- All participants must follow the Code of Conduct.
03 / Submissions + judging
- Submit before the announced deadline. The schedule is currently a draft.
- Judges may ask teams to explain and demonstrate their work.
- Judges evaluate the work actually built during OffScript.
- Organizer decisions regarding rule violations are final.
04 / AI policy
Use AI. Don’t hide behind it.
AI tools are allowed, including coding assistants, generative tools, APIs, and models. Using a tool does not remove your responsibility for the project.
- Disclose meaningful AI use. Identify the tools used and how they contributed to your code, assets, or functionality.
- Understand your project. Be prepared to explain its behavior, architecture, limitations, and your team’s contribution.
- Represent your work accurately. Distinguish your implementation from generated content and pre-existing tools.
- Show real functionality. Clearly label prototypes, simulations, and unimplemented features. Do not fabricate evidence or results.
If you’re unsure how to disclose something, ask the organizers.
LET’S TALKoffscripthackathon@gmail.com