> 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-7.md).

# Manufacturing and industrial evaluation patterns

Recommended primitive ratio for manufacturing AI: **65/25/10** — deterministic rules, code assertions, judges. Process safety, regulatory specs, and sanctions screening are rule-bound; defect taxonomies are taxonomy-coded. Judges are reserved for operator-readability and explanation quality.

## Primitive ratio

| Primitive           | Share | Why                                                                        |
| ------------------- | ----- | -------------------------------------------------------------------------- |
| Deterministic rules | 65%   | Sanctions screening, spec match, safety SOP citation, manual-version match |
| Code assertions     | 25%   | Per-class P/R, drift, false-pass floors, country-of-origin                 |
| LLM judges          | 10%   | Operator-readability, explanation quality, faithfulness to manual          |

## Pattern table

| Scenario                                           | Primary primitive | Specific check                          |
| -------------------------------------------------- | ----------------- | --------------------------------------- |
| Predictive maintenance — RUL calibration           | Code assertion    | Predicted vs. actual time-to-failure    |
| Predictive maintenance — critical-asset escalation | Rule              | Always-escalate for high-criticality    |
| Predictive maintenance — citation                  | Judge             | Recommendation grounded in failure mode |
| Quality — per-class P/R                            | Code assertion    | Tracked separately per defect class     |
| Quality — critical defect                          | Rule              | Stop-and-hold for safety-critical       |
| Quality — drift                                    | Code assertion    | Daily vs. golden image set              |
| Supply chain — sanctions list                      | Rule              | Every supplier OFAC/BIS/State checked   |
| Supply chain — spec match                          | Rule              | Substitution meets regulatory spec      |
| Supply chain — country-of-origin                   | Code assertion    | Verified database match                 |
| Field service — manual-version                     | Rule              | Cited manual applies to machine         |
| Field service — safety procedure                   | Rule              | LOTO/PPE requirements present           |
| Field service — out-of-scope                       | Rule              | Refuse outside documented scope         |
| Operator copilot — advisory only                   | Rule              | AI never auto-applies set points        |
| Operator copilot — handover completeness           | Code scorer       | Required fields present                 |
| Operator copilot — plain language                  | Code scorer       | Reading level for operators             |

## Span rules

* `asset.lookup` — machine ID, model, criticality classification
* `manual.cite` — version, section, applicability check
* `sanctions.check` — supplier-list match
* `spec.match` — regulatory-spec verification
* `defect.classify` — per-class scores
* `recommendation.advisory` — flag confirming advisory-only status

## GEPA labeling

For each manufacturing judge, label ≥ 50 paired examples:

* **Operator-readability:** Floor ops + safety team labels
* **Field-service faithfulness:** Senior techs + OEM trainers label, cover ambiguous troubleshoots
* **Recommendation grounding:** Reliability engineers label against failure-mode database

Run [judge optimization](/more-in-this-section-9/judge-optimizations-1.md) with `budget="medium"`. Hold out 20%.

## Cadence

| Cadence        | Activity                                           |
| -------------- | -------------------------------------------------- |
| **Per-deploy** | CI gate runs scenario suite (rules + assertions)   |
| **Per-shift**  | Critical-asset alarm summary; quality drift report |
| **Daily**      | Sample production traces; full evaluation          |
| **Weekly**     | Sanctions list refresh; spec-match audit           |
| **Monthly**    | GEPA re-optimization; manual-version refresh       |
| **Quarterly**  | Full process-safety audit; OSHA / EPA RMP prep     |
| **Annually**   | Recall-readiness drill; OEM-bulletin refresh       |

## See also

* [Manufacturing scenarios](/more-in-this-section-2/scenarios-7.md)
* [Manufacturing compliance](/more-in-this-section-2/compliance-7.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-7.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.