A cleaned text extract from the T1985 archive, shown for source transparency. This is one of the documents T1985 Intelligence draws on. Restricted, financial, and personal material is excluded from public view.
Create the syria2033.com connected shell implementation plan and React/router structure. Do not rebuild the existing Syria / KETURAH land-cover, DB Analytics, Plan Map, chatbot, notification, or theme systems. The objective is to mount the existing app inside a clean syria2033.com domain shell, preserving all completed work and connecting it under one public-facing operating layer. Required output: 1. Existing System Map • Identify the current app shell • Identify existing routes • Identify the Home page • Identify city pages • Identify DB Analytics • Identify Plan Map DB layer • Identify chatbot component • Identify theme provider / theme toggle logic • Identify notification helper • Identify database/project-site routes 2. syria2033.com Shell Purpose Define syria2033.com as the domain-level entry shell for: • Syria 2033 master-plan intelligence • KETURAH-style development-area control logic • Land-cover and infrastructure mapping • DB-backed project-site analytics • AI chatbot / assistant layer • Dark/light theme consistency • Public-ready navigation layer 3. Connected Route Plan Create a route plan that wraps the existing app instead of duplicating it. Required routes: • / • /map • /analytics • /projects • /projects/[id] • /cities • /cities/[citySlug] • /chat • /admin • /api/project-sites • /api/analytics • /api/notifications 4. Component Layout Show a React / Next.js style component structure. Required shell components: • Syria2033Shell • GlobalHeader • GlobalNavigation • ThemeToggle • ChatbotDock • StatusBar • MainContentFrame • ExistingAppMount • MapMount • AnalyticsMount • ProjectInspector • NotificationBridge 5. Theme Rule Reuse the existing theme provider. Do not create a second disconnected dark/light system. Home page, city pages, map pages, analytics pages, and chatbot must all read from the same theme state. 6. Chatbot Rule Mount the existing chatbot as a persistent dock or panel inside the syria2033.com shell. The chatbot must not replace the app. The chatbot must help interpret map layers, DB Analytics, project status, and Syria 2033 master-plan logic. 7. Database Rule Use the existing seeded project-site database. Do not hardcode fake chart values. The shell must read the same DB-backed data used by: • DB Analytics • Plan Map DB layer • Inspector panel • Project detail pages 8. Notification Rule Use the existing notifyOwner helper. Add the notification bridge only if required. Do not create duplicate notification logic. Project status changes must trigger email/push notifications only once. 9. No-Rebuild Rule The shell must wrap and organize existing features. It must not rewrite land-cover logic, map layers, tRPC routes, DB schema, notification helpers, or theme providers unless a connection bug is found. 10. Required TypeScript / React-Style Structure Provide pseudo-code or implementation-style structure for: app/layout.tsx app/page.tsx app/map/page.tsx app/analytics/page.tsx app/projects/page.tsx app/projects/[id]/page.tsx app/cities/page.tsx app/cities/[citySlug]/page.tsx components/shell/Syria2033Shell.tsx components/shell/GlobalHeader.tsx components/shell/GlobalNavigation.tsx components/shell/ChatbotDock.tsx components/shell/StatusBar.tsx components/theme/ThemeToggle.tsx components/map/MapMount.tsx components/analytics/AnalyticsMount.tsx components/projects/ProjectInspector.tsx components/notifications/NotificationBridge.tsx 11. Acceptance Criteria The final implementation must satisfy: • syria2033.com loads a connected Home shell • Existing app features remain functional • Existing map layers remain connected • DB Analytics displays seeded database records • Plan Map DB layer displays seeded database records • Chatbot is mounted globally or as a dock • Theme toggle works across Home, map, analytics, city, and chat views • Notifications still use notifyOwner • No duplicate data source is introduced • No duplicate theme provider is introduced • No duplicate notification system is introduced • No unverified Syria sample data is presented as verified • Existing completed work remains connected • Tests pass 12. Final Output Format Return: A. Step-by-step implementation checklist B. File-by-file implementation map C. React/router structure D. Data-flow diagram in text E. Theme-flow diagram in text F. Notification-flow diagram in text G. Testing checklist H. Final no-drift QA checklist Operate as a connected continuation of the existing Syria / KETURAH app, not as a new build.