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

Smok Przewodnik

Anita Bath · Anita-Bath/smok-przewodnik

Council score

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

An impressively engineered codebase with the right per-profile concept, but largely fabricated accessibility data, missing mandatory deliverables and no business model leave the partner-critical requirements unmet.

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

The per-person constraint model (allowed, prefer_avoid, must_avoid, five presets, guest mode) genuinely changes the verdict per user, but the demo chain is broken: no PDF, no video, form unfilled, no live demo, and routes initially drawn from a simulated Bezier fallback. B's 9 is an outlier its own reasoning undercuts, and the evidence supports the more critical view of A and C.

Members disagree here: scores range by 4.0 points.
Prototype quality20%
6.0

The build is real and large, about 30k LOC across a .NET Clean Architecture backend (PostGIS, Supabase auth, Valhalla, SignalR) and an Expo app, with 79 commits by 5 authors during the event. It loses points because the required conflicting, incomplete and source-down case is nowhere demonstrated, 44 test files measure zero test cases, the only described screenshot is the stock Expo starter, and the Leaflet WebView map has no text alternative.

Data reliability15%
3.0

The model plans for provenance (confidenceState including disputed, fact statuses, one sample venue labelled unverified), but delivered data is largely invented: wheelchairAccess derived by hashing entity ids, street-surface notes hardcoded as facts, and synthetic results setting hasStepFreeAccess true while stating 'Brak zweryfikowanych danych'. The evidence supports A's and B's 3 over C's lenient 5, and no Kraków open-data ingestion is visible.

Members disagree here: scores range by 2.0 points.
Scalability20%
7.0

Clean Architecture with separated infrastructure, PostGIS and a Valhalla engine configured via tile URLs makes a multi-city setup plausible at the architecture level. The frontend is Kraków-hardcoded, no add-a-city path is documented, and no ingestion pipeline feeds the API, which caps the score near the middle.

Members disagree here: scores range by 2.0 points.
Business model20%
0.0

No business model, pricing or numbers appear anywhere in the README, docs or code, and the submission form and deck that would normally carry it are missing. All three members independently scored it 0.

Source lines30,170
Tests44 files
Claims built6.0 / 10
Task fitYes

Strengths

  • Substantial genuine build: about 30k LOC, 79 commits by 5 authors all inside the event window, spanning a .NET 10 Clean Architecture API and an Expo/TypeScript mobile app.
  • Per-person constraint levels (must_avoid, prefer_avoid) with five presets and a no-login guest mode make the route verdict depend on the user's profile rather than one green icon.
  • Serious accessibility craft in the UI: Polish accessibility roles and labels, high-contrast and dark themes, font scaling, large touch targets and voice guidance.
  • Provenance-aware data design (confidenceState with disputed, fact statuses to_check and missing) with the sample venue explicitly labelled unverified demonstration data.

Weaknesses

  • Missed requirements: no PDF deck, no video, unfilled submission form and no live demo, so the mandatory conflicting, incomplete and source-down case cannot be verified.
  • Displayed accessibility data is largely fabricated: wheelchair access assigned by hashing place ids, route and street-surface claims hardcoded in the client, and no per-datum source or date.
  • No Kraków open-data integration (MSIP, WFS, dane.gov.pl) and no ingestion pipeline feeding the API.
  • No business model anywhere in the submission.

Red flags

  • Unverified or missing data renders as accessible: synthetic results set hasStepFreeAccess true while stating 'no verified data', and hash-derived wheelchairAccess is shown as place data, the cardinal sin for this task.
  • Routes come from a simulated Bezier fallback that asserts 'zero stairs' with 98 percent confidence regardless of reality.
  • 44 test files measure zero test cases and the only described screenshot is the unmodified Expo starter screen, weakening evidence of what actually runs.
Built during the event: yes: 79 commits by 5 authors, 2026-10-03 09:35 to 2026-10-04 08:18 UTC
Live demo: none found in the form or README
Council v9
Aclaude:glm-5.3-flash43.0100% agree
Bdots-studio/dots-3-note-preview:free55.060% agree
Cinclusionai/ling-3.0-flash-sante:free44.570% 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