sarvesh kapre

sure - i'm using the ChatGPT desktop app, /goals, GPT-5.6 Sol at extra-high effort, in Standard mode. Prompt --------- Build and continuously improve Power Atlas: a production-quality, map-first web app showing the physical infrastructure that powers, computes, and connects the world. Use Next.js, TypeScript, Tailwind CSS, shadcn/ui, and a reliable interactive mapping library. Keep the app deployable as a ChatGPT Site, maintainable, tested, and excellent on desktop and at a 390px mobile viewport. Cover: - Power generation and energy storage - Transmission lines, substations, interconnectors, and grid upgrades - Interconnection queues - Data centers, AI campuses, and compute infrastructure - Submarine cables, landing stations, and connectivity infrastructure Prioritize coverage in this order: 1. United States 2. China 3. Europe 4. India 5. Canada Work autonomously for as long as meaningful improvements remain. Continuously audit coverage, identify high-impact gaps, research authoritative and recent sources, normalize data, reconcile duplicates and conflicts, validate results, commit durable checkpoints, publish verified releases, and continue. Prefer official sources such as regulators, government agencies, utilities, operators, permit filings, and company disclosures. Track distinct lifecycle states, including operating, construction, approved, permitted, proposed, queued, suspended, cancelled, retired, and unknown. Never assume a project is complete simply because its target date has passed. For every record, preserve source links, source dates, verification dates, ownership, capacity, lifecycle, location evidence, uncertainty, geometry type, precision, and confidence. Calculate all displayed totals from the database and never present partial coverage as complete. Map accuracy is critical. Never invent coordinates or place infrastructure at city centers, company offices, administrative centroids, or unrelated facilities. Keep records with unreliable locations searchable, but clearly label them as unplotted. Use: - Points for verified sites - Polygons for large campuses and project areas - Realistic lines for transmission infrastructure - Clearly labeled schematic routes for submarine cables - Separate records for facilities, substations, interconnection points, and landing stations Make the map the dominant full-screen canvas with compact floating search, filters, statistics, source information, and project details. Keep it pannable and zoomable while records are inspected. Use drawers and bottom sheets instead of navigating away from the map. Support Generation, Grid, Compute, Buildout, and Connectivity views. Geography selection must update the map, statistics, search, filters, coverage reporting, and URL. For every release, run the production build, lint, data-integrity tests, search and inspector checks, desktop and 390px mobile verification, overflow checks, browser-console checks, and live production verification. Prioritize correctness, provenance, transparency, maintainability, and useful coverage over impressive-looking record counts. When evidence is incomplete, preserve the uncertainty instead of guessing.