Smart CitySelf-submittedNot a finalist (self-declared)

UczciwaCena

Last Minute · LastMinuteGameStudio/smieciarka.pl

Council score

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

A genuinely engineered and honestly documented zero-waste resident tool with real semantic matching and privacy care, whose smart-city claim rests on quality-of-life framing alone, with no urban data integration, poll-only alerts, a mocked OTP and a missing deck and submission form.

Criteria · line = median, dots = each member
Idea & Innovation30%
6.0

A real urban habit (posts about trash-shed finds scrolling away) is served by a working pipeline where vision captioning feeds embeddings and a calibrated reranker with measured thresholds. The free-exchange concept itself is not new, so the novelty is in the matching, not the idea.

Relation to Category20%
5.0

Waste reduction is a genuine resident pain, but the evidence confirms there is no municipal data feed, no city-staff role and no mobility, energy or crisis dimension anywhere in the code. The smart-city link rests on quality-of-life framing alone, which supports the middle reading over both the strict no-fit and the strong-fit view.

Members disagree here: scores range by 4.0 points.
Practical Applicability / Usability20%
6.0

The end-to-end flow works (post, semantic search, photo upload, notifications), browsing needs no login, and the README ships an APK, seed data and a one-command start. Alerts require login, the free tier allows one watch filter, OTP is a fixed mock, and notifications only arrive by polling.

Design (visual/UI)20%
5.0

The Flutter theme code is coherent (Material 3 palette, Rubik typography, styled navigation), but no deck was provided and 0 of 42 screenshots were described, so visual quality cannot be verified from the evidence.

Completeness & Implementation Value10%
6.0

About 6,100 lines across a real FastAPI backend with pgvector, migrations, S3 storage, EXIF stripping, JWT auth and reranker matching, plus a Flutter client, in 40 event commits. This is offset by only 5 test cases, no vector or geospatial indexes, and synchronous AI calls in request handlers.

Members disagree here: scores range by 2.0 points.
Source lines6,089
Tests5 cases
Claims built7.0 / 10
Task fitYes

Strengths

  • Real, measured AI pipeline: Jina embeddings and reranker, Gemini vision captioning and query expansion wired into the listing and filter paths, with documented thresholds.
  • Privacy engineering beyond the demo norm: EXIF stripped by re-encoding and public coordinates rounded to about 100 m.
  • Honest internal docs (stan-obecny.md) that separate the target spec from what actually works.
  • Practical demo path: release APK, seeded Warsaw listings and a one-command start script.

Weaknesses

  • No municipal or urban data source and no city-staff role anywhere in the code, so the smart-city case rests on framing and the platform depends entirely on its own user-generated listings, a two-sided cold start.
  • The core alert promise is weak at scale: notifications are poll-only with no push, and OTP is a hardcoded 123456 mock with no real SMS gateway.
  • Missed deliverables: no presentation deck and a submission form left essentially unfilled, so with 0 of 42 screenshots described the UI cannot be judged and the README is the only pitch.
  • Sparse tests (5 cases), no PostGIS, Redis or Celery, and no integration with the real Facebook group posts the project itself names as the problem.

Red flags

  • One commit landed after the deadline (1 of 40; the other 39 were during the event, so this is minor).
  • No demo check in the evidence pack verified the README's hosted-backend and APK claims.
Built during the event: yes: 40 commits by 2 authors, 2026-10-03 15:57 to 2026-10-05 12:54 UTC
Live demo: none found in the form or README
Council v9
Aclaude:glm-5.3-flash56.0100% agree
Bdots-studio/dots-3-note-preview:free50.070% agree
Cinclusionai/ling-3.0-flash-sante:free55.080% 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