LAUNCH CONTROL · 2026-08-09
iCIDM Beta Launch Readiness
One purpose: stop feature drift, expose launch blockers, and move the colleague-facing product from ZIP to a controlled beta deployment.
87HTML pages
1027internal/external href checks scanned
35missing local link targets
0missing critical launch pages
Release gates
| Gate | Status | Exit condition |
|---|---|---|
| G1 · Colleague Demo Ready | IN PROGRESS | 5–10 colleagues complete Find → Check → Navigate → Correct without coaching. |
| G2 · CIDM Closed Beta | PENDING | Persistent review workflow, corpus QA, mobile workflow, provenance and feedback tested. |
| G3 · Institutional/Public Release | PENDING | Hosting, security/privacy, governance, ownership and release approval resolved. |
P0 launch board
| Workstream | Status | Next evidence |
|---|---|---|
| Mobile/App Home | PASS · v5.25 | Colleague usability observation |
| Critical pages present | PASS | All 8 present |
| Site link integrity | REVIEW | 35 missing local targets detected in static scan |
| Persistent Review Queue | BETA PASS | Browser-local CIDM-REV objects + JSON export/import implemented; secure backend still required for institutional persistence. |
| My CIDM end-to-end | BETA WIRED | Name/current view → contextual Review Queue → CIDM-REV → JSON export/import. Run test |
| 2,231 corpus release QA | STRUCTURAL PASS / METADATA REVIEW | 2,231 unique PMIDs; 0 invalid years; 0 PMID URL mismatches. Journal/container completeness now 2,231/2,231: 496 internally recovered + final 3 resolved from PubMed/NCBI evidence; 12 repeated-title groups remain for review. Recovery report Open QA |
| HTTPS beta hosting | PENDING | Stable staging URL |
| Privacy / security / governance | PENDING | Institutional review before broader release |
Launch rule
Freeze architecture. New research ideas go to the Future / Research Queue. P0 work may change the product only when it improves colleague use, correctness, reviewability, security or deployability.
Immediate execution order
1. Persistent Review Queue → 2. My CIDM end-to-end wiring → 3. structural corpus QA → 4. metadata repair + mobile/full-site release QA → 5. closed-beta package and hosting.