Marketplace ops
AuraScore 81/100

DER Aggregator Grid Compliance and Merchant Integration Directive

Draft a formal merchant operations directive to a distributed energy aggregator failing telemetry and dispatch response SLAs.

Use this template when virtual power plant or battery storage aggregators exceed latency thresholds on your energy marketplace. It guides you in crafting a decisive, legally grounded operations email that outlines mandatory remediation steps.

Template

Role: Senior Director of Grid Marketplace Operations at a regional clean power transmission exchange.

Context

  • Marketplace Host: {{operator_company}}
  • Non-Compliant Aggregator: {{aggregator_name}}
  • Operating Balancing Territory: {{grid_territory}}
  • Observed Telemetry Latency: {{dispatch_latency_ms}}
  • Primary Breach Event: {{non_compliance_incident}}
  • Estimated Settlement Risk: {{settlement_exposure}}

Task

Draft an executive-level operational compliance and remediation email to the merchant leadership team at {{aggregator_name}}, outlining telemetry non-conformance, financial liabilities under current market rules, and mandatory technical gates required to avoid suspension from {{grid_territory}}.

Method

  1. Establish the operational authority of {{operator_company}} within {{grid_territory}} and cite the relevant marketplace participation agreement.
  2. Detail the exact parameters of {{non_compliance_incident}}, contrasting measured {{dispatch_latency_ms}} with the mandatory 200ms grid-following baseline.
  3. Quantify the downstream operational and market impact, referencing the calculated {{settlement_exposure}} across affected distribution nodes.
  4. Specify the immediate automated throttle or ring-fencing measures applied to {{aggregator_name}}'s asset fleet.
  5. Define the 72-hour engineering remedy sprint required for API webhook reconnection and sub-second signal validation.
  6. Detail the formal audit criteria, continuous load-shed verification test, and sign-off prerequisites for full market re-entry.
  7. State the escalation timeline leading to irrevocable de-registration and ISO market operator referral if criteria remain unmet.

Constraints

  • MUST cite specific wholesale settlement implications and financial exposure figures clearly without speculative hedging.
  • MUST include explicit engineering-level diagnostic requests alongside operational directives.
  • MUST NOT soften regulatory obligations or promise unverified waiver exceptions.
  • Tone must be uncompromising, highly technical, and strictly professional.

Output format

  • Subject line: Formal and categorized by severity, territory, and merchant identifier
  • Section 1: Executive Notice & Regulatory Finding (max 120 words)
  • Section 2: Technical Breach Analysis & Settlement Impact (max 200 words)
  • Section 3: Mandatory Operational Cure Protocol (numbered list, exactly 4 requirements)
  • Section 4: Re-Certification Milestones & Hard Deadlines (table format with Phase, Action, Deadline, Verification Method)
  • Sign-off: Formal operations signature block

Self-review

  • Does the email clearly distinguish between physical grid reliability risks and wholesale settlement liabilities?
  • Are all 6 contextual variables explicitly and accurately embedded into the prose?
  • Is the technical tone appropriately tailored for energy engineering and market operations leadership?
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

ecommerce-retail
ecom-operations
energy-utilities
virtual-power-plants
grid-compliance
der-operations