From the NVIDIA edition of September 19, 2026
Clarity: AEMA wants curtailment terms fixed before interconnect—evidence still thin
The Clarity · Energy / AI infrastructure analysis · United States (grid interconnection policy)
- Publisher
- The Clarity
- Original publication
- on/around September 16, 2026 (story cluster)
- Source retrieved
- 2026-09-20
- Event date
- 2026-09-16
What happened
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.
Why it matters
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 and measured results
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).
Limitations and uncertainty
Secondary synthesis of Axios/Heatmap/theneuron/NVIDIA; derived 4 GW sizing check labeled insufficient; adoption score low by Clarity own rubric.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-20; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Interconnection queues block AI capacity; flexibility is pitched as a shortcut without enforceable terms.
- Stakeholders
- utility liaison
- facilities
- CFO
- public affairs
- Discovery questions
- What curtailment depth/time will you put in the interconnect agreement?
- Which jobs are non-curtailable?
- Has any utility adopted AEMA metrics?
- Value hypothesis
- Credible, measurable flexibility can unlock risk-adjusted interconnect—if utilities adopt the metrics.
- Potential engagement
- Flexibility exhibit workshop plus witnessed curtailment drill design.
- Unsupported claims
- AEMA already adopted by utilities
- 25% campus-wide proven
- Household bills automatically fall
Pre-sales engineering
Role takeaway
- Fit
- Sites with deferrable training/batch mix; weak for always-on interactive-only halls.
- Architecture and integration
- 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.
- Proof of value
- Witnessed MW reduction
- Duration/response logs
- SLO hold during event
Delivery
Role takeaway
- Work
- Negotiate terms, instrument meters, rehearse curtailment, file evidence pack.
- Dependencies
- utility
- platform scheduler
- legal
- Ownership
- Facilities interconnection lead.
- Skills and adoption
- Operators need demand-response runbooks alongside GPU ops.
- Governance checkpoints
- Terms before energization
- No GW claims without emergency proof
- Public rate narrative separate
- Acceptance criteria
- Signed flexibility metrics
- Drill report filed
- Non-curtailable list approved
- Risks
- Tariff never materializes
- Interactive load cannot flex
- Coalition optics over substance
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Schedulers must classify interactive vs deferrable jobs; Flex/DSX paths need verifiable telemetry for depth/duration/speed.
Governance
Who approves, reviews and stays accountable for outcomes?
Interconnection filings should attach measurable flexibility commitments; do not assume ratepayer benefit follows operator queue wins.
Security and privacy
What data, permissions and controls need testing?
Grid-signal automation expands OT trust boundaries; not deeply analyzed here.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
None stated.
Procurement
What should contracts, pricing and exit terms secure?
Condition any flexible-load vendor claims on utility-accepted metrics and drill evidence.
Operating model
Which teams own the service once it runs?
Flexibility becomes a contractual operating regime, not a software feature checkbox.
Publication history
- 2026-09-19NVIDIA · Issue 148 resources
Stable resource ID: clarity-aema-curtailment-before-connect-20260916