Launch readiness

What is ready, blocked, or still risky.

MatchMedi touches medical information, community, Korean support, and mobile apps. This page keeps the launch decision honest.

ready: 0partly ready: 10blocked: 1deferred: 0

Launch judgment

This is closer to private alpha review than public launch. Legal review, source verification, moderation staffing, and Korean clinical source mapping remain important blockers.

Automated verification

Commands to run before review

pnpm verify:launch
pnpm verify:research
pnpm verify:claims
pnpm verify:content
pnpm build
pnpm mobile:build

These checks cover launch safety, research data, claim auditing, content, static build output, and Capacitor sync.

Hard blockers

Do not launch publicly until these are resolved

No public launch while donation/nonprofit language is legally unclear.
No public forum launch without moderation staffing and production auth.
No Korean clinical treatment launch until Korean source mapping or reviewer review is complete.
No iOS/Android store submission until physical-device builds pass.
No claim that a trial search result means eligibility.

Manual review path

What still needs human eyes

Open /en, /en/navigator, /en/forum, /en/forum/new, /en/treatments/tunlametinib-hl-085, and /en/readiness.
Check 360px, 390px, 768px, and desktop layouts for readable spacing and no header clutter.
Submit a local forum draft with a report selected and confirm the file is not stored.
Open the install page on iPhone Safari after HTTPS deployment and confirm Add to Home Screen behavior.
Confirm every clinical page shows sources, evidence tier, jurisdiction status, and disclaimer.

Partly ready

Medical safety model

Core guardrails are implemented, but final clinical pages still need ongoing source review and legal/disclaimer review before public promotion.

Evidence

Structured research database with evidence tiers.
Claim audit verifier exists.
Treatment recommendation language is avoided by product rules.

Next step

Run a page-by-page clinical copy audit before launch.

Partly ready

Melanoma / NRAS research depth

The melanoma and NRAS information map is materially stronger than a thin article site, but unresolved leads remain.

Evidence

Tunlametinib / HL-085 record exists with China-specific framing.
Research gaps are tracked explicitly.
Jurisdiction matrix flags unknowns instead of assuming availability.

Next step

Resolve the remembered U.S. trial link for tunlametinib plus PD-1/PD-L1 or keep it clearly unresolved.

Partly ready

Other cancer expansion

Other cancer entry points now exist as source-backed overviews, but they are not deep treatment modules.

Evidence

Lung, breast, colorectal, leukemia/lymphoma, and pediatric solid tumor overview pages exist.
Navigator and trial finder route non-melanoma queries to overview pages and trial-search terms.
PWA cache includes the overview pages in English and Korean.

Next step

Choose one next cancer for deeper build only after source mapping, claim audit, and reviewer/legal posture are ready.

Partly ready

Korean experience

Korean support pages, navigator, forum, and source-status flows exist. Korean clinical treatment pages remain review-gated.

Evidence

Korean UI and footer are localized.
Korean install, source map, and question-guide flows exist.
Korean clinical pages do not ship machine-translated treatment claims.

Next step

Map 국가암정보센터/Korean regulator sources into the research database before publishing Korean clinical treatment pages.

Partly ready

Forum user experience

The forum feels active in prototype mode and supports local pending drafts, but true public posting requires server deployment and moderation staffing.

Evidence

Cohort threads exist by drug/mutation context.
Thread/comment drafts save as pending review.
Doctor-report file selection does not store the report.

Next step

Deploy the Worker + D1 backend and connect moderator actions to server records.

Partly ready

Forum safety backend

The Worker has moderation, reporting, logs, and rate limits, but production auth and deployment are not complete.

Evidence

D1 schema includes threads, comments, reports, moderation log, and rate limits.
All submissions default to pending review.
Rate limits and unsafe-language blocks are implemented.

Next step

Replace placeholder moderator token with real auth and deploy behind HTTPS.

Partly ready

PWA / iPhone install

The app can be installed from Safari after HTTPS deployment. The install flow is documented in-product.

Evidence

Manifest exists and starts at the language chooser.
Service worker caches install, forum, Korean home, English home, and key melanoma pages.
Install pages exist in English and Korean.

Next step

Deploy over HTTPS and test Add to Home Screen on a physical iPhone.

Partly ready

Native iOS / Android

Capacitor shells exist and sync, but physical builds require Java/Android Studio and full Xcode setup.

Evidence

iOS and Android projects exist.
Capacitor sync passes.
Native storage abstraction uses Capacitor Preferences.

Next step

Install Java + full Xcode, then run Android debug build and iOS simulator/device build.

Blocked

Nonprofit / legal

Public launch should not imply nonprofit status, donation tax deductibility, or legal clearance until the governance track is real.

Evidence

Funding and policy pages exist.
No ads or affiliate links are in the MVP plan.
Donation flow is not yet active.

Next step

Choose fiscal sponsor or file path, then review disclaimers and donation language with counsel.

Partly ready

Source verification

Internal data verifiers pass, but live external source verification may fail from network/source availability and still needs launch-day review.

Evidence

Research, claim, and content verifiers pass.
Citation/source registry exists.
Source licensing posture is documented.

Next step

Run source URL verification from a stable network and manually review any failures.

Partly ready

Design and readability

The interface is calmer and more useful, but final design QA across phone sizes is still needed.

Evidence

Mobile-first layout exists.
Menu and language toggle reduce header clutter.
Evidence badges, source cards, and forum cards are consistent.

Next step

Do a 360px, 390px, 768px, and desktop visual QA pass.