OpenAI 2026 hackathon

Ariad: Breast

Breast cancer treatment is scary. 1000 side effects could happen from multiple different drugs. Codex and I built a reliable tool that explains side effects in language they can understand.

Solo project by Henry Conter · 0 likes · 0 comments

Archive position — measured, not model output

0 likes on Devpost

2,264 of the 7,856 archived projects have more likes, and 5,592 share exactly 0 — so this project's #2,722 place in the like-ranked listing is a tie-break inside that group, not a ranking.

Projects (log scale)

1
10
100
1k
10k
05,592
11,758
2285
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,59271.2%
11,75822.4%
22853.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,856 archived projects, captured when this archive was built.

Executive Summary

What the company appears to be

Ariad: Breast is a self-reported patient-facing educational prototype for adults receiving systemic therapy for breast cancer. It offers two starting points — “I’m starting treatment” and “I’m having a symptom” — with fixed, source-controlled information and neutral summaries of symptoms entered by users. The tool uses GPT-5.6 in tightly bounded roles to match symptoms to IDs and restate facts, but does not diagnose or recommend treatments.

What changed

The project is described as a prototype built during a hackathon (OpenAI 2026). It includes clinical content architecture, versioning, source control, and deterministic delivery logic. The tool was built with Codex as the sole engineering collaborator, and the author states that it does not collect user data or store symptom histories.

Single most important open question

Is there evidence of clinical review or approval for the content used in the prototype? The description makes clear that the current version is unreviewed and marked as draft, but no indication exists whether a process for clinical validation has begun or is planned beyond the stated “next milestone.”

Back to contents

What The Product Actually Is

The description states that Ariad: Breast is a patient-facing educational prototype for adults receiving systemic therapy for breast cancer. It offers two entry points:

  • I’m starting treatment
  • I’m having a symptom

For those starting treatment, users can search for drugs or regimens and review three practical questions: what to know before treatment, what may help at home, and when to contact the cancer team.

For those experiencing symptoms, users describe their symptom in everyday language, select from a controlled list of categories, add treatment context, and answer factual questions. The system then presents fixed, source-controlled education and warning information, along with a neutral summary of the facts entered, which can be copied or shared with the cancer team.

The tool uses GPT-5.6 in two tightly bounded roles:

  1. Matching unfamiliar wording to symptom IDs from its catalogue.
  2. Restating supplied facts into a neutral summary.

It does not diagnose symptoms, assign toxicity grades, recommend treatment changes, or write clinical guidance.

The interface is built with Next.js and React, deployed on Cloudflare Workers. It reads one compiled release at runtime, and all logic is handled by pure functions rather than generated on demand.

Not evidenced: The tool does not support accounts, data collection, or server-side symptom history.

Back to contents

Positioning & Claim Evolution

The author states that Ariad: Breast grew from two ideas:

  1. Making complex treatment information easier to navigate.
  2. Building the limits into the product from the beginning.

It is positioned as a calm path through a difficult moment, aiming to help patients move from what they are noticing to understandable, source-linked information they can discuss with their cancer team.

The tool explicitly avoids:

  • Improvising medical guidance
  • Making plausible-sounding but incorrect answers
  • Replacing the treating cancer team as the primary source of help

It is described as a clinical boundary tool, not a chatbot or triage system. The author emphasizes that it does not attempt to determine causation, assign urgency, or recommend changes.

The positioning reflects an intent to be transparent and safe, rather than comprehensive or predictive.

Back to contents

Target Customer & ICP

The target customer is defined as adults receiving systemic therapy for breast cancer.

The tool is described as a patient-facing educational prototype, not intended for clinicians or caregivers. It is built for individuals navigating treatment-related symptoms or preparing for treatment.

Not evidenced: No information on whether the tool targets specific subgroups (e.g., early-stage vs. metastatic), age ranges, or language preferences beyond English.

Back to contents

Business Model & Pricing Evidence

The description does not provide any evidence of a business model or pricing strategy.

It is described as a prototype, and no mention is made of monetization, licensing, or customer acquisition plans.

Not evidenced: No revenue streams, pricing tiers, or commercial partnerships are mentioned.

Back to contents

Technical & Delivery Signals

The product is built with:

  • Next.js and React
  • Codex as the sole engineering collaborator
  • A versioned, source-controlled clinical content architecture
  • Pure functions for logic, not dynamic generation
  • Deterministic compiler that produces immutable releases with SHA-256 hashes

GPT-5.6 is used in bounded roles only, and all outputs are validated or fall back to deterministic behavior.

The system has:

  • 175 unit and golden tests
  • End-to-end patient journeys
  • Adversarial model-output tests
  • Accessibility checks
  • Mobile testing down to 320 pixels

Deployment is on Cloudflare Workers with server-side API keys, rate limits, and closed fallbacks.

Not evidenced: No information on scalability, infrastructure costs, or long-term technical roadmap.

Back to contents

Traction & Maturity Signals

The project is described as a prototype, built during a hackathon (OpenAI 2026).

It includes:

  • 492 exact object versions
  • 139 patient-facing educational modules
  • 101 source records
  • 28 observable symptom concepts
  • Three complete treatment-and-symptom demonstration pathways

The prototype supports preparation information for 53 drugs and eight regimens.

Not evidenced: No data on user adoption, engagement, or feedback. No evidence of real-world usage or clinical integration.

Back to contents

Competitive Context

The description does not mention any direct competitors or market context beyond the general space of patient-facing health tools or symptom checkers.

It is described as a prototype, and no indication exists whether it competes with existing platforms or fills a gap in the market.

Not evidenced: No competitive analysis, market size, or positioning relative to other tools.

Back to contents

Key Risks & Red Flags

  1. Unreviewed clinical content: The prototype is explicitly marked as unreviewed and draft. No clinical approval or review process is described beyond “next milestone.”
  2. No commercialization plan: There is no evidence of a business model, pricing, or customer acquisition strategy.
  3. Limited scope: The tool only supports 53 drugs and eight regimens, with three demonstration pathways. It does not appear to be scalable beyond its current scope.
  4. No data collection or analytics: The system does not collect user data or store symptom histories, which may limit future development or clinical utility.
  5. Dependency on GPT-5.6: While the model is used in bounded roles, any failure or unavailability could impact functionality.

Back to contents

Diligence Questions To Ask The Founders

  1. What is the timeline and process for clinical review of the content?
  2. Are there plans to expand beyond the current 53 drugs and eight regimens?
  3. How will the tool be integrated into existing clinical workflows or systems?
  4. Is there any plan for user feedback collection or iterative improvement?
  5. What are the legal and regulatory considerations for deploying such a tool in a healthcare setting?
  6. Are there any partnerships or collaborations with oncology institutions already in place?

Back to contents

Investment/Partnership Verdict

Not evidenced: No information is provided about funding, valuation, or commercial traction.

The project is described as a prototype, built during a hackathon, and not yet clinically reviewed or approved. It has clear technical boundaries and safety features but lacks evidence of market readiness, clinical validation, or commercial viability.

It is positioned as a proof-of-concept with strong architectural and design principles, but it is not yet a product ready for patient use or investment consideration.

The author states that the next milestone is clinical review — which may be necessary before any further development or commercialization can proceed.

Back to contents

Source

Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.

The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.