Integration checklist

The ordered list both sides work through, split into ours and theirs. Also in the repo as docs/integration/CHECKLIST.md — this page is the rendered copy.

Ours (fidra)

• Kickoff call held — outputs recorded: theme choice, game list, locale, flags, wallet mode, go-live target
• Tenant created (scripts/new-tenant.mjs) — operator id, theme validated against contrast rules, ≥ 2 playable games
• Dashboard key + (if network features) pool key generated and handed over via password manager — never chat or email
• Staging embed URL for the tenant delivered
• Docs link (this site) delivered to the operator's developer
• Holdout configured; assignment events verified flowing
• Go-live: production embed URL issued after every "theirs" item below is green

Theirs (operator)

• Iframe embedded on a staging page of the operator's app (Quickstart §1)
• Listener receiving events — ready, session_start, bet_placed observed (Events)
• launch_request handler answering with tokenized URLs for the real catalog
• Sandbox wallet cycle green — happy path and the failure modes: insufficient, reject, timeout-retry with the same roundId, 500 (Sandbox wallet)
• Real test wallet green — same cycle against the operator's staging wallet service, idempotency verified against a durable store
• Holdout verified — a control-group test user genuinely sees no feed anywhere in the app
• Daily outcome rows flowing to /api/outcomes, including zero-NGR rows for assigned non-players (Measurement)
• RG hooks verified: player_check answered; a forced fidra:v1:pause shows a breather; risk states tested if used (Responsible gaming)
• Operator dashboard reachable with the handed-over key
• Go-live date agreed; rollback contact known on both sides
• On-call named on both sides (name + channel + hours)