Public launch checklist

Scientific integrity

• [ ] Public records are derived from a pinned, calibrated engine commit.
• [ ] Active, legacy, and historical scopes are visibly distinct.
• [ ] Search cohort and denominator are present for every active evidentiary record.
• [ ] Synthetic, modeled-cost, fidelity, and reproduction limitations are displayed.
• [ ] No imported public record can create a local verdict or bypass P9.

Security and privacy

• [ ] Publication uses an explicit allowlist and leak scan.
• [ ] Secrets, private sources, raw licensed data, holdout values, and local paths are excluded.
• [ ] Public storage credentials cannot write private engine state.
• [ ] Uploads, if enabled, are quarantined and rate-limited.
• [ ] A takedown and supersession procedure exists.

Product truthfulness

• [ ] No sample or placeholder record can appear as live data.
• [ ] Empty states are real zero states with an epoch stamp.
• [ ] Verdict language never implies profitability or trading advice.
• [ ] Documentation and engine versions are visible.
• [ ] Calibration health and date are public.

Operations

• [ ] Domain, TLS, backups, logs, monitoring, and budget alerts are configured.
• [ ] Static site and corpus snapshots can be rebuilt from a clean checkout.
• [ ] Publication bundle hashes are recorded.
• [ ] Rollback restores the last known-good public release.
• [ ] Submission and model spend have hard daily caps.

Recommended launch order

1. Documentation only.
2. Curated, read-only corpus snapshot.
3. Search and record detail pages.
4. Invite-only submissions.
5. Moderated public submissions after abuse and cost behavior are measured.