| Q-02 |
Issue scoped, account-owned Cloudflare API tokens to replace the Global API key |
| Q-03 |
Provide the production Cognito user pool and app client, and production hosts for eCards, logbook, profiles and professional APIs |
| Q-04 |
Confirm that PADI's TrustArc notice covers Datadog RUM and device fingerprinting before a consent choice |
| Q-05 |
Decide the 53 legacy redirect rows, language-less redirects and where redirects load; share the owner of the store /courses/{course} list; decide the root files (ads.txt, app links, favicons, verification files) |
| Q-06 |
Choose option A or B for signing in on PADI Travel (MyPADI) |
| Q-07 |
Agree website performance and availability targets and the expected launch-season peak |
| Q-08 |
Agree recovery time and recovery point objectives per system |
| Q-09 |
Confirm ownership and billing of AWS accounts 871993978063 and 984950935535, and of the Datadog organisation |
| Q-10 |
Publish rate limits, SLAs and an owner for each PADI platform API |
| Q-11 |
Close the data-exposure findings API-R1 to API-R3 in the MyPADI API readiness report |
| Q-12 |
Confirm production authentication settings: tokens out of the callback URL, SRP-only on the production client |
| Q-13 |
Decide the source of truth for single sign-out (session service or Cognito global sign-out) |
| Q-14 |
Plan the missing APIs: pinned certifications, course-to-form link, card designs, renewal dates, dive recency, bookings, badges |
| Q-15 |
Decide ownership of the rebuilt account app (Next.js), whether it replaces the current account app, and how its 26 locales map to the 21 served on padi.com |
| Q-16 |
Decide a single source of truth for member preferences (language, units, communication opt-ins) |
| Q-17 |
System of record for image text (Acquia DAM or Crowdin); video translation tool |
| Q-18 |
Handling of old Russian URLs; Russia and Belarus on blog paths after the blog move |
| Q-19 |
Reconcile the two blocked-market lists (edge Worker and CMS notices) |
| Q-20 |
Provide a scheduled row in a replicated PADI Travel table as the finder feed's liveness signal; add alarm recipients for the Travel-side replication alarms |
| Q-21 |
Provide the Google Places key for staging and confirm the production key's allowed addresses |
| Q-22 |
A data-classification policy and retention targets; confirm whether sending telemetry to Datadog US1 needs a data processing update |
| Q-23 |
Name approvers for this document and owners for the operating model |
