COTRUGLITECH
Cotrugli Tech · AI Hackathon

Every hackathon has a rumour. This one has a receipt.

Somebody always suspects the result was decided before the pitches were heard. Usually there is no way to answer them — you can only ask them to trust the organisers. So we built the hackathon on infrastructure that answers instead: the criteria are committed before entries open, the judging panel is drawn where anyone can re-run the draw, and no score can be quietly changed after the fact.

Register interest →
Dates, team size, criteria and prizes for the next edition are being set. Ask and we will send them the moment they are fixed.
Don't trust us — verify.

How it runs

Three rounds. The AI narrows; people decide.

An AI reads every submission, and it reads all of them with the same attention — which is the one thing a human judge cannot honestly promise on the two-hundredth pitch of the week. What the AI produces is a ranking with its reasons written down.

It does not decide. Not because we distrust it, but because a decision needs someone who can be asked to answer for it, and software cannot be asked. So every cut carries a human signature, and the AI's reasoning sits beside that signature where you can read it.

ROUND 01

AI triage

Every entry read and ranked, with reasons recorded. The shortlist is a recommendation, and a panel signs the cut before it is real.

ROUND 02

Mentors and judges

Assigned people work with the teams that got through — alongside the AI, not replaced by it. Who advised whom, and when, is recorded rather than remembered.

ROUND 03

The panel decides

A drawn panel of people picks first, second and third. The AI advises. The signature is human, and it is the only thing that counts.

What a losing team can check

The interesting question is not who won. It is whether you can prove nobody moved the goalposts.

None of the following requires taking our word for it, and none of it requires trusting the judges. It is arithmetic anyone can re-run.

The rubric existed before you enteredThe criteria are sealed when entries open, and every decision carries a pointer to the exact version used. Changing them later cannot rewrite what an earlier decision meant.
Your submission is what you submittedSealed at the deadline. Nobody polished an entry afterwards, including us.
You were on time, provablyBeing late is a position in the record, not a reading off somebody's clock. "I sent it before the deadline" is settled by the record itself.
Nobody picked the panel that judged youThe final panel is drawn. Take the published inputs, re-run the draw yourself, and you get the same names we did.
Nobody rescored you afterwardsA decision is a new record, never an edit of an old one. A change is visible as a change.
You can read whyThe AI's reasoning is recorded and bound to what it judged. Altering the text after the fact breaks the binding, and the break is detectable.

What this does not claim

The boundaries are part of the design.

A hackathon that oversold its own fairness would be worse than one that never mentioned it. So, plainly:

We cannot prove the judges were rightOnly that the process was not tampered with. Whether your venture deserved to win is a human judgement, and it stays one.
The AI never decides anythingIt ranks and it explains. Every cut and every placing carries a human signature. There is no setting that changes this.
Verified is not the same as goodVerification proves a record is authentic and unaltered. It says nothing about the quality of what the record describes.
Being drawn is not being competentA reproducible draw proves nobody hand-picked your judges. It does not prove they were the right ones.

Lose, and still know it was fair.

Dates, team size, criteria and prizes for the next edition are being finalised. Tell us you are interested and we will send them as soon as they are set.

Register interest