InfiniSynapse Vibe Coding Hackathon 2026

Hackathon Judging: Scenario, Build, and Novelty

Hackathon judging uses scenario value at 40%, technical completeness at 35%, and innovation at 25%. William Zhu is the confirmed judge for InfiniSynapse.

By InfiniSynapse · Last updated October 2, 2026

1st Global Edition

Vibe CodingHackathon

Online 2026

Oct 10–31, 2026 · Pacific Time

Free · Global

$900 / $600 / $300

From the event pageOpen this section

Prize pool

$3,000

PlaceAwardSeats
1st$9001
2nd$6002
3rd$3003

Repository stars are not part of the score.

TL;DR

Hackathon judging for the InfiniSynapse Vibe Coding Hackathon 2026 uses three published weights. Scenario value is 40%. Technical completeness is 35%. Innovation is 25%. William Zhu, Co-founder of InfiniSynapse, is the confirmed judge. GitHub stars are not scored. The event is online and free. The build window runs from October 10, 2026, at 12:00 AM through October 31, 2026, at 11:59 PM Pacific Time. In that window Pacific Time is PDT, UTC−7. The open is 07:00 UTC on October 10. The close is 06:59 UTC on November 1.

Hackathon judging looks at a working web, mobile, or desktop app. Slide-only pitches, notebooks without an app, fake JSON standing in for a workflow, and a generic chat box on a spreadsheet are outside the rewarded set. Six tracks are starting points for one registration: Education, Retail & Replenishment, Hit-product Analysis, SMB Operations, Growth for Operators, and Open Industry. The cash pool is $3,000: one prize of $900, two of $600, and three of $300. Payout timing, tax handling, judging dates, and a winner announcement date are not published. The event page has not published age, region, or team-size rules. A submission deadline separate from the build window is not published. Capacity is not published. Register only on Luma. Hackathon judging does not add a second score for popularity.

William Zhu, Co-founder of InfiniSynapse and confirmed judge
Confirmed judge, William Zhu

What the score actually weighs

Hackathon judging on this page is a weighted rubric, not a mood and not a star count. A rubric in the academic sense is a set of criteria and weights set down before the work is reviewed. That page explains the word. It is not the event rulebook. The rulebook here is the three percentages. Read them before you spend the window polishing a feature the weights do not ask for.

The three slices have to be visible in the thing a reviewer opens. A strong story in a side document does not move a slice whose evidence is missing from the app. Hackathon judging can only score what a person can try.

Scenario value at 40 percent

Scenario value is the largest slice. It asks whether a named operator has a situation a reviewer can recognize. A store buyer, a course coordinator, or a small-team owner should see their week on the first screen. Hackathon judging gives this slice 40% because a clever screen with no real situation is a demo of software, not a demo of a decision.

Name the person and the question in plain words. "Which courses lose learners before they finish?" is a scenario. "Which SKUs are about to stock out?" is a scenario. "What should we watch?" with no channel, no period, and no next move is not. The difference shows up on the first click, before any model output. Hackathon judging can tell those apart without a long preface.

Put the operator's noun on the screen: course, SKU, order, or channel. If a stranger can only say "it analyzes data," the scenario is still missing. Hackathon judging treats that vague label as unfinished.

Technical completeness at 35 percent

Technical completeness is 35%. The app has to run, and the path from input to result has to be visible. A reviewer should see the fields, the result, and the recommended action without opening your notes.

A path a reviewer can retrace

Show what went in. For replenishment, on-hand units, recent sales, and supplier lead time are enough to rank stockout risk. For a course screen, enrollment, attendance or completion, and assessment results are enough to show which class loses learners. If a field is synthetic, say so on the screen. Hackathon judging treats a hidden column as a gap, because a reviewer cannot try a number they cannot see.

The OWASP Top 10 is a public list of common web risks. This event does not require an OWASP audit or a security certificate. It does expect the app a reviewer opens to behave like a real client: inputs you can change, a result that follows those inputs, and no canned file pretending to be a live path. Completeness is that path. Hackathon judging does not award the 35% for a screenshot of a path you described elsewhere.

Change one input and let the result move. Hackathon judging treats a frozen rank, after a lead time edit, as an incomplete path.

A client that opens

Web, mobile, or desktop all qualify. One client is enough. Pick the surface the operator already uses. The Vibe Coding Guide is the product guide for the build. Hackathon judging still scores the app you can open, not the guide you read.

Google's site reliability table of contents maps how running systems are discussed in public. You are not being asked to implement that book. If the reviewer cannot start the app, the 35% has nothing to attach to.

Innovation at 25 percent

Innovation is 25%. It asks whether the approach adds something beyond a stock layout with a generic sentence on top. A sharper cut of the same operator question can be enough: a ranking the person did not have, a comparison across two periods, or a reason code next to the recommendation. Hackathon judging does not require a new model architecture. It requires a choice a template did not already make.

A reason code is a short label tied to a figure on screen, such as lead time longer than sales cover. A slogan with no figure under it does not fill the 25%. Hackathon judging can see the difference.

Tie-break rules are not published. If two apps sit close, you cannot look up a fourth weight. Build so each of the three slices is obvious on its own. Hackathon judging stays inside those three numbers.

What never enters the score

Read the exclusions before you optimize the wrong artifact. The event page publishes the same bar: a working, data-backed app for a real small-business workflow. Stars, slides, and a chat box do not collect the 40, the 35, or the 25.

Stars on a repository

GitHub stars are not part of hackathon judging. A popular repository does not add points, and a quiet one does not subtract them. William Zhu, Co-founder of InfiniSynapse, keeps a public engineering profile on GitHub. Stars on that profile, or on yours, are still outside the score. Spend the window on the operator action, the data path, and a build a reviewer can open.

If you want the same weights restated as a way to aim a build, read how to win a hackathon on the published rubric. The cash attached to those weights is listed with the prize seats. Neither page adds a star term. Hackathon judging stays at 40, 35, and 25.

Slide decks, notebooks, and canned files

A deck can explain the operator. It cannot replace the app. A notebook can explore rows. The rewarded form still needs an application around that work. Static JSON that pretends to be a live workflow is outside the brief. So is a generic chat window dropped on a CSV with no named user, no stated question, and no next step. Hackathon judging has no partial-credit line published for those forms. If the file a reviewer opens is only slides, the rubric has no app to score.

A notebook can stay in your process. The entry itself still needs a client someone else can try. A chat box on a CSV, with no named operator and no next verb, is the form the brief leaves out.

Who applies the rubric

One judge is confirmed. A full judge list and biographies beyond that confirmation are not the subject of this page.

The confirmed judge

William Zhu, Co-founder of InfiniSynapse, is the confirmed judge. Hackathon judging runs through that confirmation. Additional judges, a panel size, and a scoring form are not published. Do not invent a committee, a vote, or a public comment period.

What is still unpublished

The event page has not published age, region, or team-size rules. Judging dates are not published. A winner announcement date is not published. Payout timing and tax handling are not published. Required submission materials, a file format, repository requirements, and an official submit link are not published. There is no submit button on the event page until an entry point is live. Those blanks are not secret rules you can infer. Hackathon judging does not let you fill them in by guessing.

One registration, one window

Register only at the official Luma listing. This page does not publish a Discord invite. There is no second registration form. Entry is free. The window opens October 10, 2026, at 12:00 AM Pacific Time and closes October 31, 2026, at 11:59 PM Pacific Time. A submission deadline separate from that window is not published. Hackathon judging uses the app you can show from inside that window. Capacity is not published, so a seat count on the prize table is not a cap on who may register.

Free tickets on the current listing open on October 10, the same day the window starts. An earlier open date is not published. Clock the close in Pacific Time. The last minute is 06:59 UTC on November 1.

InfiniSynapse Vibe Coding Hackathon 2026 hero — online global event to build industry know-how apps on the InfiniSynapse platform.
InfiniSynapse opens a global online hackathon for developers who will ship industry apps on its platform.

How a demo earns the points

Walk the three weights when you rehearse. A reviewer should point at the scenario, the path, and the novel choice without your narration. Move setup labels onto the first screen.

Name the operator and the week

Pick one track as the scene. The six names are starting points, not six contests. Hackathon judging accepts any one of them. The table below is the operator each name points at.

The week matters as much as the role. "This week's reorder" is a scenario. "Inventory in general" is a topic. Bind the question to a period the operator already uses: this week, this cohort, this promotion, this pay period. Hackathon judging can recognize a period. It cannot score a topic that never becomes a decision.

Fields, result, and the next verb

End on a verb the operator can do this week: reorder, contact, reassign, feature, or watch. A chart with no recommended move leaves the 40% thin, even when the chart is correct. Put the figure the verb rests on next to the verb. Hackathon judging can see completeness when the same screen holds the fields and the action.

Keep one verb in the first line. "Reorder these three SKUs before Friday, because cover is shorter than lead time" hands the decision over. "Consider several areas" hands it back.

An illustrative store direction

This is an illustrative direction, not a customer case study, and it does not promise a product capability beyond the public docs. Question: what is about to stock out this week? Input: inventory on hand, recent unit sales, and lead time, labeled synthetic if you built the file. Output: SKUs ranked by stockout risk, with a suggested order priority. A reviewer changes one lead time and sees the rank move. That movement is the completeness check. The recognizable store week is the scenario. The reason code beside the priority, if a plain sort would not have produced it, is the innovation. Hackathon judging can score all three from that one screen.

A course list can use the same shape: attendance and completion in, courses ordered by drop-off out, and one follow-up the reviewer can open. That too is an illustrative direction, not a case study.

Tracks and prize seats beside the rubric

The weights do not change by track. The cash does not change the weights. Read both so you do not build toward a prize rule that was never published.

Six starting points

TrackOperatorWhat the 40% should recognize
EducationSchool or training providerWhere to intervene, which course to change, or how to assign people and seats
Retail & ReplenishmentStore operatorReorder now, wait, or raise a SKU's priority
Hit-product AnalysisMerchandiserRestock, feature, or watch a product that jumped
SMB OperationsSmall-business operatorThe next operational move the numbers support
Growth for OperatorsSmall teamThe channel or step worth the next week of effort
Open IndustryAn operator you can nameA concrete next step that person repeats

Education can use enrollment, attendance or completion, and assessment results. Retail can use on-hand units, recent sales, and lead time. Hit-product work can use sales over time plus price or promotion flags you may use. Operations can use orders, costs, and sales for one period. Growth can use channel visits, conversion, and repeat activity. Open Industry asks you to name the user, the data, the analysis, and the action. Hackathon judging still applies 40%, 35%, and 25%.

Use data you may use, or label a synthetic set on the screen. The event page has not published a shared dataset. Hackathon judging cannot treat an unlabeled file as a live path.

Cash seats that do not change the weights

The pool is $3,000. One first prize is $900, two second prizes are $600 each, and three third prizes are $300 each. Six seats, one pool. The dollars are not a fourth scoring axis. A reviewer does not add points because a prize is large, and does not subtract points because a prize is smaller. Hackathon judging remains the three weights. Payout timing is not published, so do not plan a pay date the page does not give.

PlaceAwardSeats
First$9001
Second$6002
Third$3003

Tax handling is not published. This page is not tax guidance. Wait for official payout terms. The money facts you can cite now are the six amounts and the $3,000 total.

InfiniSynapse Vibe Coding Hackathon 2026 hero — online global event to build industry know-how apps on the InfiniSynapse platform.
InfiniSynapse opens a global online hackathon for developers who will ship industry apps on its platform.

Questions about the score

Does a quiet repository lose points?

No. GitHub stars are outside the score. A repository with no stars is not a penalty, and a repository with many stars is not a bonus. Hackathon judging looks at the working app, the scenario, the path, and the novel choice.

Is a notebook with charts scored?

Charts can help you find the pattern. The rewarded artifact is still an app. A notebook with no application around it is listed among the forms this event does not reward. Put the chart where the operator can act on it. Hackathon judging needs that client before the 35% can land.

Do the weights have a published tie-break?

Tie-break rules are not published. There is no fourth percentage on the event page. If you need a way to choose between two features, choose the one that makes the scenario easier to recognize or the path easier to retrace. Hackathon judging will not consult a rule you cannot read.

Are judging dates on the event page?

Judging dates are not published. A winner announcement date is not published. The dates you can plan against are the build window: October 10, 2026, 12:00 AM through October 31, 2026, 11:59 PM Pacific Time. Hackathon judging does not publish a review calendar beside that window.

Where is registration?

Register only on the Luma listing linked from the event page. Entry is free. This page does not publish a Discord invite. Age, region, and team size are not published on the event page. Those blanks do not change hackathon judging.