Section

The Manifesto

Nine beliefs that organize this entire site. Each links to a deeper essay. Each is testable. Each has citations.

The Manifesto

Nine beliefs that organize this entire site. Each links to a deeper essay. Each is testable. Each has citations.

  1. Every hackathon must have a clear goal. A theme is not a goal. A vibe is not a goal. A goal is a stakeholder plus an outcome. → the goal

  2. Apples to apples — by problem, by track, or by abstracted rubric. Comparing a doctor-appointment app to a satellite orbit modeler is malpractice. Single-problem, explicit tracks, or one uniform rubric pitched above the domain. → fair judging

  3. Problem statements are an artifact, not an afterthought. Murby's three-part test: clear, actionable, tied to impact. With a real stakeholder behind every statement. → problem statements

  4. AI lowered the floor, AI raised the ceiling. The technical moat at the median collapsed. Taste, problem selection, and demo craft are now the differentiators. → AI era

  5. There are ten working formats, not two. Single-problem, themed multi-track, sponsor-bounty, government civic, university season, internal corporate, platform ecosystem, code sprint, game jam, blind replication sprint. → format taxonomy

  6. Open innovation requires a frame. "Build anything" produces incoherent judging. UN SDGs, civic problems, sponsor problem areas — pick a frame. → the frame

  7. Ringers are fine. Mislabeling is not. Open events that include funded teams are not bugs. Student events that don't exclude funded teams are. → no ringers without disclosure

  8. Storytelling is part of the work. "Show, don't tell" is engineering, not marketing. Demo craft and narrative are not optional. → storytelling is not optional

  9. When there is no ground truth, convergence is the proof. Some hackathons make claims the world cannot verify on judgment day. Integrity comes from independent teams converging on the same answer using methodologically distinct paths on a shared dataset. The embargo is the demo day. → integrity through convergence

v0 outline. The full essays (600–1200 words each, three or more cited primary sources per essay) are written in Phase 2 Days 11–17.

All principles (9)

  1. Principle 1

    Every Hackathon Must Have a Clear Goal

    A theme is not a goal. A vibe is not a goal. A goal is a stakeholder plus an outcome, and most hackathons that disappoint their participants disappoint them because they were never designed against either.

  2. Principle 2

    Apples to Apples — by Problem, by Track, or by Abstracted Rubric

    Comparing a doctor-appointment app to a satellite orbit modeler is malpractice. The systemic answer takes one of three forms: single-problem competitions, explicit tracks, or a single uniform rubric pitched one level above the problem domain.

  3. Principle 3

    Problem Statements Are an Artifact, Not an Afterthought

    A good problem statement is a real artifact — written in advance, owned by a real stakeholder, and pre-tested before publication. The Book recognizes two valid architectures for getting problem statements into participants' hands, and the discipline holds across both.

  4. Principle 4

    AI Lowered the Floor, AI Raised the Ceiling

    AI tools have collapsed the technical floor of hackathons and raised the ceiling. Taste, problem selection, system design, UX craft, and demo storytelling are now the differentiators.

  5. Principle 5

    There Are Ten Working Formats, Not Two

    Discussions of hackathons collapse into a binary — open innovation versus problem-statement driven — and the conversation gets stuck. The actual ecosystem contains ten working format archetypes, each with distinct rules of engagement and failure modes.

  6. Principle 6

    Open Innovation Requires a Frame

    Build anything without a frame produces incoherent judging and a participant experience that feels random. Themes, civic problem areas, sponsor problem sets, and the UN Sustainable Development Goals are all valid frames. Pure open innovation is not.

  7. Principle 7

    Ringers Are Fine, Mislabeling Is Not

    The ringer team — a funded startup, a hardware-rich team, a group with pre-existing work — is a documented and persistent presence in open hackathons. The underlying problem is not ringers. It is mislabeling. The fix is a clear three-class taxonomy that lets events say what they actually are.

  8. Principle 8

    Storytelling Is Part of the Work

    The Book argues, against the hacker-culture instinct that the work should speak for itself, that demo craft and narrative are not optional add-ons. They are part of the work, and in the AI era where foundation models are commoditized and prototypes ubiquitous, they are the most reliably differentiating skill a participant can bring.

  9. Principle 9

    When There Is No Ground Truth, Convergence Is the Proof

    Some hackathons make claims the world cannot verify on judgment day. For those, the integrity of the result has to be argued through structural means — convergence across independent teams using methodologically distinct paths on a shared dataset.