Cracow without barriersSelf-submittedNot a finalist (self-declared)

ClearWay

Senti · domikolo/hackyeah2026

Council score

Median of 3 models, weighted by the task's official criteria
71.8 / 100

A deep, unusually data-honest accessibility prototype with real open-data pipelines, per-datum provenance and clean scalability, kept below the top band by the missing mandatory video, the unperformed WCAG self-check, unpriced revenue and no independently verifiable demo.

Criteria · line = median, dots = each member
Relation & usability25%
7.5

Four mobility profiles with per-attribute thresholds (kerbs, incline, surfaces, door widths) recolor the map and change routing per person, provenance renders in every popup, and missing data shows as grey 'Brak danych', never as accessible. The task-required WCAG 2.2 self-check of the main scenario was never executed, so accessibility rests on code-level evidence only, which caps the score.

Prototype quality20%
7.0

The measured facts (11,386 LOC, 45 test cases, 17 screenshots, 110 commits during the event) support the members who found a real working system over the doubt that the frontend never rendered data: FastAPI with A* routing over about 5,600 footway segments, navigation with rerouting, and photo obstacle reports. But the mandatory video of at most 3 minutes is missing, and with no hosted demo and an empty demo_checks array no end-to-end run was verified.

Data reliability15%
8.0

Every attribute carries source, URL, date and a four-level confidence, unverified data is visibly flagged, sample data is marked is_sample, and conflicts such as the Wawel declaration-versus-OSM case surface explicitly. The open-data integration is real in code (OSM via Overpass, GUGiK lidar slopes, ZDMK parking, 25 parsed declarations), though declaration coverage is only 25 institutions and 320 places carry inferred attributes.

Scalability20%
8.0

Ingestion (fetch scripts, normalized GeoJSON with provenance, merge, REST API) is cleanly separated from a React frontend that holds no data or labels of its own, so a new city is a REGION polygon plus rerunning the documented scripts, estimated at 1-2 days, and a new source is one fetch script. Single-region SQLite and in-process Python A* are honest prototype limits with a stated PostGIS/Valhalla migration path.

Business model20%
5.5

Four structured revenue streams (widget/API subscription, owner-verified profiles, data licensing, city gap dashboard) come with a priced cost base of roughly 50-100 PLN per month. The team explicitly declines to quote any revenue prices, deferring them to pilots, so the commercial side remains qualitative despite the credible structure.

Source lines11,386
Tests45 cases
Claims built7.0 / 10
Task fitYes

Strengths

  • Provenance on every datum (source, URL, date, confidence) enforced through the API, popups and place cards, with unknown never rendered as accessible.
  • Genuinely real open-data pipelines: OSM via Overpass, GUGiK lidar-derived sidewalk slopes, ZDMK accessible parking, and a crawler parsing 25 official accessibility declarations, with conflicts surfaced rather than hidden.
  • Exemplary separation of ingestion from presentation: the frontend renders entirely from API dictionaries, making a new city a documented 1-2 day configuration task.
  • A complete navigation loop (profiles, alerts, rerouting, obstacle TTL with confirmation voting, photo reports) backed by 45 measured test cases and 17 screenshots.

Weaknesses

  • The mandatory video deliverable (at most 3 minutes) is missing; the submission form field is still a placeholder.
  • The task-required WCAG 2.2 AA self-check of the main scenario (keyboard, screen reader, contrast) was planned but never performed; only code-level aria and text-timeline evidence exists.
  • The business model has cost numbers but no priced revenue streams; the team defers all pricing to future pilots.
  • No hosted demo and no recorded demo run (demo_checks empty), and several UI pieces such as the source-down banner and the data-info panel were still to-do.

Red flags

  • Repository was private at the submission deadline, with jury access promised as a to-do and not verified.
  • The form claims 51 automated tests while the measurement found 45 test cases.
  • Repository created and 3 commits pushed before the official event start; minor scaffolding, with 110 commits during the event and none after the deadline.
Built during the event: partly: 3 commits before the event; 113 commits by 2 authors, 2026-10-02 22:08 to 2026-10-04 08:46 UTC
Live demo: none found in the form or README
Council v9
Aclaude:glm-5.3-flash78.870% agree
Bdots-studio/dots-3-note-preview:free71.890% agree
Cinclusionai/ling-3.0-flash-sante:free67.590% agree
Jclaude:glm-5.3–judge
Self-submitted and unverified: the result shown is the team's own claim. The council read an evidence pack built from the repo, its decks and docs; it didn't run the code or see the pitch.
The site is open source

The 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.

Star on GitHub