Sport & HealthcareSelf-submittedNot a finalist (self-declared)

Offload

Offload Team · denyss4/offload

Council score

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

A consent-first, wellbeing-aware planner with a genuinely tested decision matrix and standout accessible design, whose pitched AI loop is mostly stubbed, whose integrations are unverified, and whose own pack cannot decide which app it is showing.

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

The consent-first bridge from how you feel to an approved calendar change is a genuine wedge. But the delivered core is a simple four-branch energy and stress matrix and the pitched conversational loop is only partly built, so the innovation is real but moderate, which the evidence supports over both the loftier and the harsher readings.

Relation to Category20%
7.0

Sport and mental wellbeing genuinely drive the tested matrix, so the council sides with the higher scores over the view that the fit is shallow. The fit is still capped because health input is entirely self-reported, the HRV, sleep and resting heart rate fields are never populated, and access to care is only support contacts and a 112 card.

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

Account-free setup, one-tap check-ins, bilingual UI, consent screens and disclaimers show real usability care. But nothing is verified on a device, calendar writes need a development build, the LLM path needs external credentials, and no live demo was checked, so everyday use is limited to the local rules path.

Design (visual/UI)20%
8.0

The token-based dark Lichen theme has documented WCAG contrast, colour-vision-deficiency simulations, and glyph plus label so meaning never rests on colour alone. All three members agree here and differ by only half a point.

Completeness & Implementation Value10%
6.5

Roughly 16k lines of source and 72 tests cover the decision matrix, scheduler and calendar adapters, backed by unusually honest limits documentation. But the LLM is stubbed, OAuth and encrypted storage are unverified on any device, and the repo bundles a second app and a starter scaffold, blurring what this entry actually is.

Source lines15,987
Tests72 cases
Claims built7.0 / 10
Task fitYes

Strengths

  • A tested decision engine: a safety-ordered matrix in the backend produces a concrete plan and per-change calendar proposals with reasons, approval, audit and undo.
  • A consent-first architecture: correctable stress labels, explicit external-AI disclosure, the LLM kept off the write path, account-free setup and encrypted local state.
  • Exceptional design rigor: generated WCAG contrast tables, colour-vision-deficiency simulations, and plans marked by glyph and label so colour is never the only carrier of meaning.
  • Honest documentation: gaps and critique logs, a demo script that forbids overclaiming, and unverified integrations flagged rather than hidden.

Weaknesses

  • The pitched AI interaction is not delivered: the Lumen chat runs on local rules or is stubbed without credentials, and voice venting is blocked in the app configuration, so the headline feature promised in the form and deck is missing.
  • Key integrations are mocked or unverified: there is no live demo evidence at all, calendar writes and Google OAuth need an untested native build, encrypted storage is unverified, and no health data is ever collected.
  • The submission is inconsistent about what it is: the repo bundles the Form readiness planner, an unrelated Expo starter and the Offload MVP, and the committed demo runbook rehearses the older Form app rather than the pitched product.
  • The healthcare side is shallow: energy and stress chips feed the matrix while biometric fields stay null, and access to care is limited to support contacts and an emergency number.

Red flags

  • The submission overclaims: the form and deck promise voice venting and a full Lumen chat, but voice input is blocked in the app configuration and the LLM gateway lacks the credentials and signing key it needs, so the headline interaction cannot run as claimed.
  • The committed demo runbook rehearses the older Form app, whose own notes say the demo build has no chat and that presenters should say it is coming, contradicting the pitched product.
Built during the event: partly: 32 commits before the event; 54 commits by 1 author, 2026-09-30 14:50 to 2026-10-04 07:11 UTC
Live demo: none found in the form or README
Council v9
Aclaude:glm-5.3-flash73.580% agree
Bdots-studio/dots-3-note-preview:free61.060% agree
Cinclusionai/ling-3.0-flash-sante:free66.090% 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