# Controlled v1 launch checklist

## Committee acceptance
- Verify current 2027 regulations and event supplementary regulations. Record their exact version, source and effective date in Race Control. Do not approve the demo baseline as real rules.
- Run a complete historical weekend, including qualifying and both races, through staging and independently reconcile every class, bonus, distance exception, carryover and standings total with the official signed results. Only the supplied Race 2 PDF was available here.
- Confirm policies that are not unambiguously specified: guest eligibility/close-up scoring, fastest-lap distance eligibility, tie decisions, single-race bonus treatment, counting-round components and driver/car changes.
- Keep a separate reconciled ledger for Time Attack/non-event awards until integrated. Final official championship sign-off is not automated by this release.
- Confirm branding against the club's original CI assets. The header and entry point are now visibly driver-first; exact supplied-font/logo approval is still yours.

## Hosting and data protection
- Deploy a private staging instance first. Remove all demo data before member launch.
- Configure the real HTTPS hostname, trusted reverse proxy, body/rate limits, persistent encrypted disk, external encryption key, MFA administrator accounts, malware screening, backup and monitoring.
- Test that private pages refuse framing and public results can embed on the existing site. Verify successful login, upload and logout on an actual iPhone and Android device.
- Test file-access denial between two real staging accounts and immediate access revocation. Confirm that public results contain no medical, identity, bank-proof or private incident data.
- Approve the club privacy notice, purpose/access/retention policy, incident response procedure and authorised personnel list. This software is not a legal privacy-compliance certification.
- Restore a protected backup into an isolated instance; verify all encrypted records and attachments with the separately retained key.
- Run dependency/security scans and an external application review against the deployed environment. This build is not a penetration-test certificate.

## Release control
- Capture the final source hash, rule version and responsible committee approver.
- Use a fresh production database or a verified migration, never a blind overwrite of an older portal's database.
- Publish only after blockers are resolved and official decisions are recorded. Check the public/driver view after every correction.
- Keep the authoritative timing PDFs and official decisions independently. The app does not replace MSA/CoC procedures or formal submission deadlines.
