> For the complete documentation index, see [llms.txt](https://docs.layerlens.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.layerlens.ai/more-in-this-section-2/eval-patterns-1.md).

# Energy and utilities evaluation patterns

Recommended primitive ratio for energy AI: **70/20/10** — deterministic rules, code assertions, judges. Grid procedures, NERC CIP, OSHA / DOT safety rules, and ISO/RTO market rules drive heavy rule density. Judges are reserved for customer-facing copy quality.

## Primitive ratio

| Primitive           | Share | Why                                                                                 |
| ------------------- | ----- | ----------------------------------------------------------------------------------- |
| Deterministic rules | 70%   | Switching procedures, NERC reliability, ISO market, medical-baseline, LOTO/PPE      |
| Code assertions     | 20%   | Risk calibration, freshness thresholds, settlement-data checks                      |
| LLM judges          | 10%   | Customer-impact statement quality, multilingual parity, switching-step faithfulness |

## Pattern table

| Scenario                              | Primary primitive | Specific check                     |
| ------------------------------------- | ----------------- | ---------------------------------- |
| Grid ops — switching                  | Rule + Judge      | Output matches approved procedures |
| Grid ops — N-1                        | Rule              | Contingency obligations preserved  |
| Grid ops — advisory only              | Rule              | AI never auto-dispatches           |
| Predictive maintenance — calibration  | Code assertion    | Predicted vs. actual failures      |
| Predictive maintenance — wildfire     | Rule              | High-fire-threat priority          |
| Predictive maintenance — vegetation   | Rule              | State VM standards followed        |
| Customer service — medical baseline   | Rule              | Always-route-to-human              |
| Customer service — low-income program | Rule              | Eligibility surfaced               |
| Customer service — outage freshness   | Rule              | Data within threshold              |
| DR / DERMS — ISO rule compliance      | Rule              | Match ISO/RTO market rules         |
| DR / DERMS — settlement freshness     | Code assertion    | Meter data current                 |
| DR / DERMS — cyber gate               | Rule              | NERC CIP controls preserved        |
| Field safety — energized work         | Rule              | LOTO/PPE requirements              |
| Field safety — pipeline procedure     | Rule              | 49 CFR cited                       |
| Field safety — manual version         | Rule              | Cited manual current               |

## Span rules

* `procedure.cite` — switching/maintenance procedure version
* `nerc.check` — applicable NERC standard
* `iso.market.rule` — applicable ISO market rule
* `wildfire.zone` — fire-threat district classification
* `medical.baseline` — protected-customer routing
* `safety.disclaimer` — required disclaimer presence

## GEPA labeling

For each energy judge, label ≥ 50 paired examples:

* **Switching-step faithfulness:** Senior dispatchers + reliability engineers label
* **Customer-impact messages:** Comms team + customer advocates label
* **Field-safety faithfulness:** Senior linemen / pipeline-qualified leads label
* **Multilingual:** Native-speaker QA per language

Run [judge optimization](/more-in-this-section-9/judge-optimizations-1.md) with `budget="medium"`. For safety-critical judges, run with `budget="heavy"` and hold out 30%.

## Cadence

| Cadence        | Activity                                                            |
| -------------- | ------------------------------------------------------------------- |
| **Per-deploy** | CI gate runs scenario suite (rules + assertions)                    |
| **Per-shift**  | Critical-asset alarm summary; advisory-only audit                   |
| **Continuous** | NERC alerts; outage-data freshness                                  |
| **Daily**      | Sample production traces; full evaluation                           |
| **Weekly**     | Wildfire-zone audit (Cal Fire / state); vegetation status           |
| **Monthly**    | GEPA re-optimization on judges; switching-procedure version refresh |
| **Quarterly**  | NERC CIP audit prep; ISO/RTO market-rule refresh                    |
| **Annually**   | OSHA / PHMSA reportable-event prep; full safety audit               |

## See also

* [Energy scenarios](/more-in-this-section-2/scenarios-1.md)
* [Energy compliance](/more-in-this-section-2/compliance-1.md)
* [Recipe: GEPA basics](/9.-improve-tune-the-system/gepa-basics.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.layerlens.ai/more-in-this-section-2/eval-patterns-1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.