HackYeah 2026 ReviewMaydayMama
Council score
Median of 3 models, weighted by the task's official criteriaA genuinely built and deployed postpartum depression early-warning network with cited evidence, privacy-first execution and rare engineering discipline, held back by the absence of a measurable-impact plan, not-yet-reviewed health content and stale submission hygiene rather than by any real gap in the working product.
The insight that close ones see changes but have no safe way to act together without judging her or going behind her back is specific and backed by cited Polish and international statistics. Circle-based PPD support is not wholly new, so it lands strong rather than exceptional.
Strip the name and the product still only works for postpartum depression: one-minute mood, sleep and anxiety check-ins, observation questions for loved ones, explainable trend rules, per-voivodeship care paths and a PPD conversation guide. A gender-neutral product could not reuse this.
A live mobile-first demo at maydaymama.pl with demo accounts, a free core tier and crisis lines that work signed out with dialable numbers makes it genuinely reachable. It loses points for having no measurable-impact plan and health content still awaiting expert review.
Members disagree here: scores range by 3.0 points.Code and specs show disciplined, dignity-centered design: a token system, dark mode, reduced-motion support, focus management, and e2e tests asserting contrast and no horizontal scroll at 375px. But only one screenshot exists in the repo and none are described, so visual quality rests mostly on code evidence.
Members disagree here: scores range by 2.5 points.Measured 21,684 SLOC, 42 API operations with a frozen OpenAPI baseline, 985 test cases in 75 files, live-mode browser journeys and a deployed demo make the whole helping loop real. On the disputed README line about sample data, the evidence supports Members A and B, who both describe a deliberate mock fallback plus live-mode e2e tests against the deployed backend, over Member C's reading that the app is an empty shell; the line is a stale status note and a documentation defect, not proof of a missing frontend.
Members disagree here: scores range by 4.0 points.Strengths
- Need evidenced with cited Polish and international statistics (GUS, the NFZ referral gap, JAMA, MBRRACE-UK) and a concrete insight about families noticing changes with no safe way to act.
- Privacy and safety handled in code: anonymous observations feed only an aggregate, RBAC is enforced server-side, crisis text is never stored, phrase rules run before any AI call, and dialable helplines work even signed out.
- Explainable rules-based trend engine combining check-ins and observations into a signal, not a black box, plus a real crisis path with calm wording.
- Engineering discipline rare for a hackathon: 92 commits all within the event window, frozen contract baseline, spec-driven workflow, and 985 tests including browser e2e against the live deployment.
Weaknesses
- No measurable-impact plan: no baseline metric, target improvement or measurement method, and no evidence of testing with the target group, only a sketched midwife pilot.
- Health and education content is self-written and flagged by the team itself as awaiting psychologist or midwife review.
- Stale README status line claiming the frontend still runs on sample data, contradicting the live-mode screens and e2e tests; documentation is out of step with the code.
- Visual evidence for the jury is thin: one screenshot in the repo and none described, so design must be judged mainly from code and deck text.
Red flags
- Minor claim discrepancies in the submission: the deck claims 1500+ fast tests versus 985 measured cases, and lists four team members while commits show three authors, with the form team name left as just 'c'. Sloppy hygiene rather than deception.
claude:glm-5.3-flash80.0100% agreedots-studio/dots-3-note-preview:free86.580% agreeinclusionai/ling-3.0-flash-sante:free64.050% 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.