# Production Readiness Foundation

This checklist defines the minimum runtime boundary before a real casino integration or public production deployment.

For the selected first deployment lane, use `docs/deployment-vercel-supabase-cloudflare.md`.

## V1 Product Contract

- Provider-facing currency is configured per operator profile.
- Supported v1 currencies are `USD`, `EUR`, `GBP`, `USDT`, `USDC`, `BTC`, `uBTC`, `ETH`, `LTC`, `DOGE`, `BNB`, `SOL`, `XRP`, `ADA`, `TRX`, `XLM`, and `ZEC`.
- The casino may support multiple player wallet currencies, but each launched Rouge Reels game session uses the configured operator currency only.
- Every provider bet, payout, rollback, limit, feed row, report, and reconciliation entry must match the session currency.
- Rouge Reels does not perform FX conversion, wallet custody, or on-chain settlement.
- Manual and Auto bet modes are active for v1. Strategies remains visible but disabled.
- Dice, Limbo, and Plinko are the enabled v1 games.

## Required Production Environment

- `NODE_ENV=production` or `APP_ENV=production`
- `STORAGE_DRIVER=postgres`
- `DATABASE_URL=<Supabase/Postgres runtime connection string>`
- `OPERATOR_SECRET_<OPERATOR_ID>=<real shared secret>`
- `DEMO_OPERATOR_API_SECRET` must not be the demo value in production.
- Operator callback URLs must be HTTPS. `sandbox://demo-casino` is local-only.
- Vercel deployment must route through `api/index.js` and pass `GET /health`.

The app intentionally rejects production startup with memory storage. Production operator configs must come from Postgres/Supabase and real deployment secrets, not fallback demo config.

## Smoke Test

1. Open `GET /health` and confirm `status: "ok"`, `currency: "multi"`, `supportedCurrencies`, and `storageDriver: "postgres"`.
2. Create a sandbox/staging launch for each enabled game.
3. Create a session and confirm the returned session and balance use the operator's configured currency.
4. Place one winning and one losing round.
5. Replay the same idempotency key and confirm no duplicate wallet transaction occurs.
6. Force a failed settlement path and confirm rollback/reconciliation evidence.
7. Open the operator dashboard and confirm the round audit trail is complete.

## Go-Live Gate

Do not treat the platform as real-money production-ready until legal, security, jurisdiction, certification, seed encryption, observability, and operator callback review are complete.