Checklist

Use this before enabling live operator traffic. Record acceptance evidence and named owners; this is a checklist to complete, not a claim that any drill has passed.

Integration contract

• operator launch endpoint working
• wallet adapter endpoints working
• wallet mutations deduplicate by idempotency key
• ambiguous primary mutation runbook tested
• webhook receiver signature verification working
• dedupe by event_id working
• Polyflight launch rejects disabled operators and preserves Opinion as the default
• Polyflight native reasons/metadata and exact IDR amounts accepted
• Polyflight read scopes assigned explicitly rather than added to old grants
• human staff access kept separate from API keys; Support and Market Requests cannot be automated with machine keys

Credentials and secrets

• API keys split by workload
• webhook secret stored in secret manager
• wallet adapter auth secret stored in secret manager
• optional wallet signature secret stored separately
• no secrets in repo, docs, tickets, or screenshots

Behavior validation

• happy-path buy validated
• happy-path sell or redemption validated
• duplicate idempotency safely replayed
• webhook retry drill passed
• dead-letter replay drill passed
• unknown wallet result drill passed
• dashboard-hosted simulator launch exercised through the real Mini App session
• simulator evidence kept separate from real REST v1 adapter certification
• Polyflight winning, losing, cancelled/refunded, compensated, and manual-review cases reconciled
• current/scheduled/history terms and statement/export parity reviewed
• positive, negative, and zero signed-position examples reviewed
• valid Polyflight loss acknowledgement accepts exactly zero without changing wallet balance; generic mutations still require positive amounts
• callback historical backfill and bulk resend understood as notification recovery, never financial replay

Operations

• staff can inspect Webhook Deliveries, Balance Ops, and Cash Flow Triage using least-privilege grants
• team distinguishes Market PnL, resolution exposure, monthly settlement, and confirmed bank payment
• Operator Support escalation evidence prepared; no secrets or unrelated personal data included
• UTC timestamps used in logs and runbooks
• team knows unresolved Polyflight liabilities block statement finalization when cash state is unknown
• team knows disabling entry must not disable owed payouts/refunds/compensation
• failed-but-unpaid Opinion payouts remain tracked after a failed cash-outcome decision; support closure or a sent callback does not erase debt
• monthly Opinion reporting uses settlements:read; Polyflight terms/statements use their separate read grants
• where private-market requests are available, authorized staff understand permanent operator ownership and principal/payout underwriting before accepting risk

Release approval

• operator-side owner approved go-live
• Polynion-side owner approved go-live
• rollback owner identified
• contact path for launch-day incident agreed
• explicit authorization obtained for production deployment, migration, operator enablement, and wallet activity
• no staging result treated as implicit production approval