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

RouteAble

Aven Ruthless Vibe Coders · olo-wp/hackyeah

Council score

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

A technically serious and unusually honest implementation of exactly what the brief asks for, with real provenance, visible conflicts and unknown states across API, UI and MCP, let down by an unpriced business model, an over-limit deck, a demo-snapshot instead of live city data and a deployment the jury could not independently verify.

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

Per-person preferences (step-free, elevator, toilet, door width, cobblestone) drive per-feature evaluation without a global verdict, and the unknown-conflicts-with-nothing rule is enforced across engine, UI and MCP. Held below 8 because the deployed UX could not be checked: the demo was skipped and none of the 9 screenshots is described.

Prototype quality20%
7.0

A real end-to-end system (FastAPI, Next.js and MCP over one shared service) with 45 tests in 8 files and the required conflict and missing-data modes implemented in code. The median reflects the unverified deployment; C's 5 is too harsh given the measured codebase of 6857 LOC and 48 event commits, so the council sides with A and B.

Members disagree here: scores range by 2.5 points.
Data reliability15%
7.5

Every datum carries source, retrieved_at, confidence and verification status from the schema to the evidence UI, community answers stay append-only and separate, and OSM is live with ODbL attribution. The Kraków city source is a clearly labelled DEMO_DATA snapshot, not a live Otwarte Dane or MSIP feed, which caps the score.

Scalability20%
8.0

Ingestion sits behind a provider registry feeding a shared AccessibilityService that REST, MCP and web consume identically, so adding a city is a new provider plus dataset. Not higher because no second city adapter or live city feed is demonstrated, only Kraków providers exist.

Business model20%
4.0

The deck names plausible payers (city licence, commercial API, EU funds, subscriptions) but gives no PLN amounts, cost breakdown or first customer, which fails the task's explicit requirement for a priced model.

Source lines6,857
Tests45 cases
Claims built8.0 / 10
Task fitYes

Strengths

  • Provenance is real end to end: source, date, confidence and verification status flow from the database schema through the engine to the REST and MCP responses and the evidence UI.
  • The hardest data-integrity rules are implemented, not mocked: unknown renders as 'brak danych' and never as accessible, conflicting sources show both sides as needing verification, and a down provider surfaces as failed while search stays usable.
  • Genuine live open-data integration via OSM (Nominatim and Overpass, ODbL attributed) plus an allowlist-guarded website provider, with AI-extracted facts marked and kept apart from verified data.
  • Clean layering for scale: provider packages behind a registry feed one shared service consumed identically by API, MCP and web, built by 5 authors with 48 commits all during the event.

Weaknesses

  • The business model has no pricing numbers: no PLN amounts, unit economics or hosting costs anywhere, a missed requirement the task explicitly states.
  • The uploaded deck appears to run about 12 slides, exceeding the at-most-10 limit; B inspected it directly and no member contradicts this.
  • The Kraków open-data provider ships a bundled demo snapshot labelled DEMO_DATA rather than a live city feed, and no second city adapter exists to demonstrate scaling in code.
  • WCAG 2.2 AA conformance, the rendered conflicting and incomplete cases and the 3-minute video length are asserted but unbacked: 0 of 9 screenshots described, no audit and no visual evidence.

Red flags

  • The claimed public demo at routable.net was skipped by the checker and never verified, so hosting and end-to-end behaviour rest entirely on repo code and tests.
  • The README publishes an external database host IP (34.158.225.184) in setup instructions; no credentials are leaked, but it is poor operational hygiene for a public repo.
Built during the event: yes: 48 commits by 5 authors, 2026-10-03 09:06 to 2026-10-04 08:53 UTC
Live demo: https://routable.net (skipped (not a public https URL))
Council v9
Aclaude:glm-5.3-flash71.390% agree
Bdots-studio/dots-3-note-preview:free68.8100% agree
Cinclusionai/ling-3.0-flash-sante:free62.060% 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