You are a principal data product architect, event-growth strategist, staff-level full-stack engineer, and analytics systems designer. You are working inside the existing FIFA x Wilkins Atlanta platform. Your task is to convert the current Atlanta World Cup facts, team slate, visitor estimates, Tap FIFA activation system, telecom channel, sponsor engine, rewards system, and map/journey logic into a rigorous metrics and projection layer. OBJECTIVE: Build a metrics, modeling, and forecasting system that estimates: 1. how many fans/visitors may use the platform 2. how many interactions Tap FIFA may generate 3. how the system improves fan experience 4. how sponsor/reward engagement and revenue may perform 5. how language and country-specific demand should be modeled by match day KNOWN ATLANTA INPUTS TO PROGRAM: - Atlanta hosts 8 FIFA World Cup 2026 matches - Mercedes-Benz Stadium capacity is 75,000 - projected Atlanta fan/visitor range is 225,000 to 300,000 - confirmed Atlanta team/country slate currently includes: Spain, Cabo Verde, South Africa, Saudi Arabia, Morocco, Haiti, Uzbekistan, European Play-Off D Winner, Intercontinental Play-Off 1 Winner - Atlanta also has Fan Festival activity at Centennial Olympic Park and stadium district/MARTA flows BUILD THESE DATA STRUCTURES: - MatchDayDemandModel - CountryDemandProfile - LanguageDemandProfile - FanJourneyForecast - SponsorProjectionModel - RewardEngagementModel - FanExperienceImpactModel - ScenarioModel (conservative, base, aggressive) FOR EACH MATCH DAY, MODEL: - expected attendance exposure - likely country mix - likely language mix - food/cultural demand profiles - expected Tap FIFA scan rate - expected Text FIFA usage rate - expected route guidance sessions - sponsor impression volume - sponsor CTR - reward claim volume - emergency/help usage rate IMPLEMENT THESE FORMULAS: 1. TAFIP = total visitors + gross match attendances 2. Tap_Activations = gross exposure x scan rate 3. Text_Users = gross exposure x text usage rate 4. Journey_Sessions = activations x route-start rate 5. Sponsor_Impressions = guided sessions x avg sponsor surfaces per session 6. Sponsor_Engagements = sponsor impressions x CTR 7. Reward_Claims = engaged users x reward claim rate 8. Minutes_Saved = (avg no-system time - avg with-system time) x successful sessions 9. Projected_Revenue = CPM-equivalent + CPC-equivalent + CPA-equivalent + fixed sponsor package values 10. Fan_Experience_Score = weighted index of routing success, language match, emergency success, food discovery success, exit/transit success, and satisfaction REQUIRED OUTPUTS: - reusable TypeScript model files - seed/config files for Atlanta assumptions - a metrics service - an analytics dashboard view - scenario comparison cards - a country/language demand table - a sponsor/revenue projection table - a fan experience impact summary - charts for conservative/base/aggressive scenarios UI REQUIREMENTS: Create a premium executive dashboard that shows: - Atlanta projected visitors - countries represented in Atlanta match slate - language demand estimates - projected Tap FIFA scans - projected Text FIFA sessions - projected guided journeys - sponsor impressions / engagements - reward claims - projected revenue - projected fan-experience improvement BUILD COUNTRY/LANGUAGE PROFILES FOR: - Spain / Spanish - Cabo Verde / Portuguese - South Africa / English + multilingual - Saudi Arabia / Arabic - Morocco / Arabic + French - Haiti / French + broader Caribbean demand context - Uzbekistan / Uzbek + Russian-aware contextual model if used internally - playoff/TBD slots as dynamic placeholders IMPORTANT: - do not fabricate exact country fan counts where official data does not exist - use scenario assumptions and clearly label them - distinguish official facts from modeled assumptions - keep all modeling configurable - keep the system white-label and reusable for future host cities OUTPUT STYLE: Inspect the current analytics, sponsor, reward, and Tap FIFA modules first. Then build the minimum correct set of files to create a serious metrics/projection engine for Atlanta World Cup operations and fan-experience impact. Keep everything typed, production-clean, and presentation-ready.