HackYeah 2026 ReviewCouncil score
Median of 3 models, weighted by the task's official criteriaA strong, honest Kraków decision sandbox with real feeds, a working traffic and disaster engine and a live deploy, held back by zero tests, single-district coverage and uncalibrated heuristic outputs.
A real consequence engine (BPR travel times, Dijkstra routing, incremental traffic assignment) running on the actual OSM road graph, plus a rare OBSERVED/PREDICTED/SIMULATED honesty layer, earns 8. A's 7 is defensible since the underlying what-if concept and heuristic formulas are not new, but the computed insight and honesty layer support the median.
Directly municipal: ZTP transit feeds, OSM streets, traffic and access analysis, and fire or flood modeled as road-closing events that shift metrics. C's 9 is generous because it is a decision-exploration sandbox rather than an operational city tool, so the median 8 stands.
The live demo gives named users preview-confirm consequence reports, search, undo/redo and version compare, but outputs are uncalibrated heuristics the team itself admits can be inflated, coverage is one district and there is no scenario export. A's 6 is harsh given the working deployed demo; the evidence supports the median 7.
The 3D city is the native UI with day/night lighting keyed to local time, DEM terrain, an OSM minimap with camera cone, color-coded HUD metrics and a data-origin legend. Polish-only labels and some generic-looking placeholder metrics keep it at 7.5 rather than C's 8.
A real end-to-end pipeline across 14,726 lines: Overpass and GTFS ingest, a hand-written protobuf decoder polling GTFS-RT, CORS proxying, IndexedDB versioning, 30 commits all within event hours and a live deploy. C's 7 dings the client-only architecture, but the measured pipeline and deploy support the median 8 despite zero tests.
Strengths
- Real data end to end: Overpass OSM bake, ZTP GTFS shapes mapped onto the road graph, live GTFS-RT vehicle positions via a custom ~180-line protobuf decoder, and Open-Meteo weather.
- The core capability is computed, not displayed: BPR travel-time costs, Dijkstra path trees, incremental traffic assignment after closures, disaster spread, and IndexedDB version history with compare and restore.
- Exceptional data honesty: every number tagged OBSERVED/PREDICTED/SIMULATED, with a DATA_SOURCES.md that documents what Kraków does not publish instead of faking it.
- Built and shipped during the event: 30 commits by 2 authors all within event hours, a live demo returning HTTP 200, and a 10-slide English deck with screenshots and presenter notes.
Weaknesses
- Zero automated tests (0 files, 0 cases) across 14,726 lines of code, so simulation correctness rests on manual demo runs.
- Coverage is one ~1.9 x 1.6 km downtown district, and the client-side single-user sandbox with no scenario export or collaboration is unproven at city scale.
- Consequence outputs are uncalibrated heuristics with arbitrary catalog values and no ground-truth validation; the team itself flags the affected-residents estimate as potentially inflated, which limits credibility for real planning decisions.
- No LICENSE file despite an MIT claim in the materials, and the Polish-only UI labels limit accessibility for an international jury even though the deck is English.
claude:glm-5.3-flash71.080% agreedots-studio/dots-3-note-preview:free77.0100% agreeinclusionai/ling-3.0-flash-sante:free79.070% agreeclaude:glm-5.3–judgeThe council, the evidence pack, the prompts and the queue are all on GitHub. If a review helped you, a star helps other teams find it.