{"resourceId":"clarity-aema-curtailment-before-connect-20260916","versions":[{"version":"external-065051557cb29b36d65bba0d4456f1ee4fc2aecd8caa7f1eb3df9235436033be","resource":{"id":"clarity-aema-curtailment-before-connect-20260916","title":"Clarity: AEMA wants curtailment terms fixed before interconnect—evidence still thin","organization":"The Clarity","sector":"Energy / AI infrastructure analysis","geography":"United States (grid interconnection policy)","publishedAt":"on/around September 16, 2026 (story cluster)","publicationDate":"2026-09-16","eventDate":"2026-09-16","sourceName":"The Clarity","sourceLabel":"Independent analysis with claim ledger","sourceUrl":"https://theclarity.today/story/emerald-ai-google-and-nvidia-launch-alliance-to-advance-flexible-ai-data-centers-20a454c5","evidenceClass":"independent-research","outcomeClass":"cautionary","topics":["infrastructure","governance-procurement","operating-model"],"finding":"Clarity AEMA cluster synthesizes NVIDIA/Emerald/Google launch coverage and theneuron.ai scrutiny: principles call for ride-through, curtailment, and contingency-response obligations before a facility connects, plus standardized metrics (response speed, duration, predictability, emergency behavior). Measured evidence cited remains a 256-GPU, 25% power cut for three hours with SLOs held, and Google 1 GW demand-response as contracted capacity—not a single emergency reduction. No utility/grid operator is named as having adopted AEMA principles; AEMA is described as a reboot of a 2014 demand-response group. Household bill relief is treated as a separate arrangement from faster interconnection for operators.","sledRelevance":"Directly relevant to SLED facilities seeking faster interconnect via flexible AI load narratives: forces explicit curtailment depth/time commitments and warns against treating vendor demos or contracted GW as proven emergency performance. Limited relevance to software procurement alone.","evidence":"Claim ledger items on principles, 25%/3h/256-GPU test, Google 1 GW contracted DR, no named utility adopter, first-of-its-kind vs 2014 reboot, technology-neutral mechanisms (shift/storage/generation/contingency).","architectureImplications":"Schedulers must classify interactive vs deferrable jobs; Flex/DSX paths need verifiable telemetry for depth/duration/speed.","governanceImplications":"Interconnection filings should attach measurable flexibility commitments; do not assume ratepayer benefit follows operator queue wins.","securityPrivacyImplications":"Grid-signal automation expands OT trust boundaries; not deeply analyzed here.","caveats":"Secondary synthesis of Axios/Heatmap/theneuron/NVIDIA; derived 4 GW sizing check labeled insufficient; adoption score low by Clarity own rubric.","streamIds":["nvidia"],"roles":{"sales":"When buyers cite AEMA for faster interconnect, lead with Clarity gate: name curtailment depth, response time, and duration as verifiable commitments before connection—not after. Separate operator queue benefits from household rate impacts. Do not sell the 256-GPU 25% demo as campus-scale proof or imply utilities have already adopted AEMA tariffs. Keep claims bounded to the inspected evidence and require site-matched proof before any capacity or interconnect commitment.","engineering":"Fit for sites pursuing Flex/demand-response interconnect pathways. Architecture needs workload classification, storage/generation options, and telemetry that utilities can audit. Proof of value: a utility-witnessed curtailment drill with MW, minutes, and SLO hold—not a coalition membership slide. Document configuration pins and failure modes so the next upgrade cannot silently invalidate the measured result. Document configuration pins and failure modes so the next upgrade cannot silently invalidate the measured result.","delivery":"Work is policy plus ops: draft interconnection flexibility exhibit, run drills, publish metrics. Ownership: facilities/utility liaison with platform. Risks: interactive inference cannot curtail; contracted GW mistaken for demonstrated cut; no tariff yet encodes AEMA metrics. Record acceptance evidence in the program archive so later editions can cite what was actually proven. Record acceptance evidence in the program archive so later editions can cite what was actually proven."},"roleDetails":{"sales":{"customerProblem":"Interconnection queues block AI capacity; flexibility is pitched as a shortcut without enforceable terms.","stakeholders":["utility liaison","facilities","CFO","public affairs"],"discoveryQuestions":["What curtailment depth/time will you put in the interconnect agreement?","Which jobs are non-curtailable?","Has any utility adopted AEMA metrics?"],"valueHypothesis":"Credible, measurable flexibility can unlock risk-adjusted interconnect—if utilities adopt the metrics.","potentialEngagement":"Flexibility exhibit workshop plus witnessed curtailment drill design.","unsupportedClaims":["AEMA already adopted by utilities","25% campus-wide proven","Household bills automatically fall"]},"engineering":{"fit":"Sites with deferrable training/batch mix; weak for always-on interactive-only halls.","architectureIntegration":"DSX Flex/Emerald-class controls with audited telemetry and job priority classes.","prerequisites":["job taxonomy","metering","runbook for contingency","SLO definitions"],"constraints":["Demo scale 256 GPUs","location-limited flexibility","no named utility tariff yet"],"security":"Authenticate grid signals; protect OT control path.","proofOfValue":["Witnessed MW reduction","Duration/response logs","SLO hold during event"]},"delivery":{"work":"Negotiate terms, instrument meters, rehearse curtailment, file evidence pack.","dependencies":["utility","platform scheduler","legal"],"ownership":"Facilities interconnection lead.","skillsAdoption":"Operators need demand-response runbooks alongside GPU ops.","governanceCheckpoints":["Terms before energization","No GW claims without emergency proof","Public rate narrative separate"],"acceptanceCriteria":["Signed flexibility metrics","Drill report filed","Non-curtailable list approved"],"risks":["Tariff never materializes","Interactive load cannot flex","Coalition optics over substance"]}},"retrievedAt":"2026-09-20T03:06:00Z","enrichedAt":"2026-09-20T03:13:48Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"None stated.","procurementImplications":"Condition any flexible-load vendor claims on utility-accepted metrics and drill evidence.","operatingModelImplications":"Flexibility becomes a contractual operating regime, not a software feature checkbox.","sourceVerification":{"openedUrl":"https://theclarity.today/story/emerald-ai-google-and-nvidia-launch-alliance-to-advance-flexible-ai-data-centers-20a454c5","referenceExcerpt":"The alliance's principles call for defining ride-through, curtailment and contingency-response obligations before a facility connects.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}