High school students first
The first edition is being designed primarily for high school students across Hangzhou.
03 / Hackathon / First editionWorking plan / No dates confirmed
Two days.One team.Ship somethingReal.
A cross-school AI product hackathon for high school students, planned for Hangzhou. The format below is a working plan — not a confirmed schedule.
- Format
- Two-day AI build
- Location
- Hangzhou, CN
- Window
- Spring 2027 / planned
- Registration
- Not open
- Dates
- Not confirmed
- Venue
- Not confirmed
- Eligibility
- In development
- Registration
- Not open
This page describes an event in development. It is deliberately specific about what is not yet known.
01 / What is a hackathonDefinition, not a promise
A short,intensive build.
A hackathon is a short, intensive build. Teams start with a problem, make decisions under a deadline and leave with a working prototype and evidence of what they learned.
It is not a lecture, a course or a slideshow. The point is to make something a person can try.
01
Build, don't describe.
A working path matters more than a polished deck. The demo is the argument.
02
Show the work.
Explain the decisions, the dead ends and what changed your mind along the way.
03
Leave with feedback.
Every team should leave with a specific next step, whether or not the prototype worked.
02 / Who this is forEligibility still in development
Curiousstudents,first.
Planning target / Not confirmed
- Participants
- 50–100
- Days
- 2
- People per team
- 2–4
Planning range for the first edition. Capacity will be confirmed only after the venue, safety and approvals are settled.
Cross-school by design
Teams should be able to form across schools. Final eligibility and school scope are still being defined.
Beginners with a reason
You do not need a finished idea. You need to want to make a product, not only watch one being made.
More than engineers
Designers, researchers, writers and organisers make products better. The room should include them.
03 / How teams workDraft team model
Small teams.Different skills.One product.
Teams are planned at 2–4 people. One person can hold more than one role; the point is that the product gets more than one perspective before the deadline.
01
Product
What are we making?
02
Build
Does it run?
03
Design
Can someone use it?
04
Story
Can someone understand it?
- Team size
2–4 people
Planning figure, not a confirmed rule.
- Roles
Product, build, design, story
One person can hold more than one role.
- Matching
Solo participants may be matched
Subject to final rules and available teams.
- Contribution
Everyone explains their part
The demo should make individual contribution visible.
- Fairness
Pre-built code must be disclosed
Reusing public libraries is allowed; presenting old work as new is not.
- Workload
Two daytime days
No overnight build is planned.
04 / The two daysDraft run of show
A shape forthe two days.
A strict build, shaped around daylight. Exact times, check-in process and guardian requirements will be published with the final rules and the confirmed venue.
No overnight build
Day 01Build
- 01
Arrive
Check-in, safety briefing, team formation and the opening.
- 02
Define
Problem, user, scope. Decide what you will not build.
- 03
Build
Get the first working path running end to end.
- 04
Checkpoint
Risks, blockers and the remaining plan, with mentors.
- 05
Close
Back up, check devices and sign out. The room closes.
Day 02Ship
- 01
Reopen
Network and repository check. Restore the last working version.
- 02
Test
Real feedback, failure cases and debugging. Cut scope if needed.
- 03
Finish
Protect the core user path. No new features after the freeze.
- 04
Freeze
Repository, README, demo, AI usage disclosure and backup.
- 05
Show
A short product demo, followed by judges' questions.
05 / What you shipMinimum bar / working draft
A workingfirstversion.
Not a completed MVP
Slides, a video or a static design.
A prototype has to do something. The demo can be small; it cannot be imaginary.
MVP minimum
01
One interactive function
It takes an input and returns an output someone can see.
02
AI in a real role
You can explain where the model does the work and why it is needed.
03
A repeatable path
Someone else can follow the setup and use it without you.
04
Honest failure behavior
Handle the obvious failure case — or demonstrate it clearly.
Submission checklist
- Repository or inspectable source package
- README: problem, user, features, how to run
- Runnable demo — live first, recorded backup
- AI usage disclosure: models, APIs, data, templates
- Evidence of at least one real test or user response
- Credits and permission to show the work
The final submission list will be published with the rules.
06 / Judging and recognitionProposed rubric / not final
How the workwill be read.
A proposed rubric, published here so teams can see what matters before they build. Final rules, judges and recognition may change.
Also assessed
Individual contribution, a declared use of pre-built code and respect for the rules. Judges with a conflict of interest must step away from that team.
Problem and user
25%A specific user, a real need, evidence of response.
Function and completeness
30%The MVP runs on the day. The main path is intact.
Technical judgement
20%Where AI is needed, how it fails, what was traded away.
Originality and creativity
15%A distinct approach, not an API wrapper with a logo.
Communication and reflection
10%Clear demo, honest limits, a credible next step.
Recognition format will be published with the final rules. Award structure depends on regulatory review. No certificate, prize or ranking is confirmed on this page.
07 / Safety and fairnessNon-negotiable before the event
The non-negotiables.
A high-school event cannot run on enthusiasm instead of responsibility. These conditions come before the schedule, the sponsors or the demo.
01
Two daytime days
No overnight build. Participants leave the venue at the end of each day.
02
Guardian consent
Participants under 18 will need guardian consent and a clear sign-in / sign-out process.
03
Code of conduct
A published standard for behaviour, reporting and consequences — for everyone in the room.
04
AI tools checked
Age-appropriate, lawful tools only. AI usage must be disclosed in the submission.
05
Data and images
Minimum collection, restricted access and explicit permission for photographs.
06
Technical backup
Two network paths, a charging plan and an offline demo backup for every team.
Position on official status
HackMeld is not presented as an official national competition. Cross-school scope, competition status, awards and recognition will be reviewed with the relevant local authorities and adult safeguarding leads before any public claim is made. We will not sell certificates or imply an endorsement that does not exist.
08 / Hackathon questionsThe honest answers
The answersso far.
No question is answered with a claim we cannot support. If something is not settled, it says so.
01Is HackMeld an official national competition?
No. HackMeld is a student-founded initiative in Hangzhou. It is not presented as an official national competition, and no affiliation with a school, government body or competition list is implied. Cross-school scope, competition status and awards will be reviewed before any public claim is made.
02When and where is the first edition?
The first edition is planned for spring 2027 in Hangzhou. Dates and venue are not confirmed. They will be published only after written confirmation, along with the rules and registration process.
03Do I need a team?
No. Teams are planned at 2–4 people, and solo participants may be matched with a team, subject to the final rules. Coming with a team is welcome, but it is not a requirement for expressing interest.
04Do I need to know how to code?
Not necessarily. You do need to want to participate in building a product, not only watch one being made. Designers, researchers, writers and organisers are part of the room. Final eligibility and selection criteria are still being defined.
05Is it free?
Not confirmed. Any participation cost, travel expectations and what the event provides will be published with the registration details. Do not assume a cost or a subsidy until it appears on this site.
06Will there be prizes?
Not confirmed. Recognition format will be published with the final rules and depends on regulatory review. HackMeld will not promise certificates, prizes or rankings before those decisions are made.
07Can I use AI tools?
Yes, within the published tool list and age-appropriate terms. AI usage must be disclosed: which models, APIs, data and third-party templates were used. Pre-built code must be declared. The event rewards work created during the build window, not a polished project made in advance.
08What about parents and guardians?
Participants under 18 will need guardian consent, emergency contact details and a clear sign-in / sign-out process. Specific requirements will be published before registration opens. There is no overnight component planned.
09 / Be thereFirst edition in planning
Be in thefirst build.
Registration is not open. Read the plan, check what is confirmed, and come back when the rules and dates are real.
No sign-up form is live. When registration opens, the confirmed link will be published here first.