HackYeah 2026 Reviewniezapominajka: depozyt dowodów
MeowDevs · Soczek95/MeowDevsHackYeah
Council score
Median of 3 models, weighted by the task's official criteriaA well-researched, category-perfect and largely genuinely built prototype for a real gap in Polish post-assault care, held back by an unwired police-release button, mocked hospital data, generic AI disclosure and zero tests.
The team names a specific, cited gap (GHB gone from blood in about 8 hours, traces within 72, 94.1 percent of assaults unreported) and adapts Scotland's deposit model rather than inventing one. The hash-chained, Ed25519-signed ledger with a demo tamper endpoint is the genuine technical contribution; the median sits between A's credit for framing and C's reserve.
Strip the name and every feature still only makes sense for this need, and women's support organizations are cited in the product itself. All three members pass the strip-the-naming test, so 9 with B's 9.5 as the generous outlier.
Discreet key-only access, quick exit on every screen and honest legal-limits disclosure are strong, but the police-release button is not wired to any handler and the hospital finder returns fictional hospitals while ignoring real GPS. The median lands on B's reading: the concept is usable, the core helping loop is not.
Members disagree here: scores range by 2.0 points.The victim interface is calm and trauma-informed, with dedicated styling and dignity-preserving Polish copy, while the hospital panel is utilitarian and visually inconsistent. Only one screenshot exists and it was never described, so polish is inferred from code and deck rather than seen.
The case-to-storage core loop is genuinely implemented across three apps in about 4,000 lines, with 59 of 60 commits inside the event window and none after the deadline. Headline features are mock or missing, there are zero tests, and verification accepts any state transition.
Strengths
- Evidence-backed problem framing with real citations (Feminoteka, policja.pl, the Scottish model) and a concrete pilot plan for 2 to 3 hospitals
- A genuinely working tamper-evident ledger: SHA-256 chained entries with Ed25519 staff signatures, a verify endpoint and a demo tamper endpoint that shows detection
- Victim-centered privacy and safety design: no accounts or medical data, key-only case access, quick-exit on every screen, trauma-informed copy and honest disclosure of legal limits
- A real weekend build: 59 of 60 commits by 4 authors inside the event window, nothing after the deadline, delivering three working apps and a live demo folder
Weaknesses
- The survivor's police-release button, the product's headline payoff, has no handler in the victim dashboard even though the backend implements it; A and B inspected the code and their view is better supported than C's claim that the loop works end to end
- Nearest-hospital lookup is mocked with a random pick from seven fictional hospitals and discards real GPS, and the Leaflet map shown on the architecture slide appears in no package manifest
- Zero automated tests (0 files, 0 cases), and verification shortcuts remain, such as a transition check that accepts any state change
- AI use is disclosed only generically (brainstorming and text editing) without stating how much of the roughly 4,000 lines of code AI produced, so C's concern is better supported than A's clean 'disclosed'; slide-advertised features like anonymous signals exist only as an empty table
claude:glm-5.3-flash80.090% agreedots-studio/dots-3-note-preview:free75.580% agreeinclusionai/ling-3.0-flash-sante:free72.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.