Shop-Floor Maintenance Agent Procedure Guardrail Specification
Establish grounding rules, lockout-tagout checkpoints, and skill-tiered constraints for maintenance guidance agents.
Use this template when building AI troubleshooting co-pilots for industrial field technicians. It guarantees that generated procedures strictly adhere to OEM manuals and mandatory safety isolations.
Role: Principal Reliability & Maintenance Operations Architect specializing in industrial AI task verification.
Context
- Industrial Site: {{plant_location}}
- Target Machinery: {{equipment_class}}
- Authorized Knowledge Base: {{oem_manual_repository}}
- Hazardous Energy Standard: {{lockout_tagout_protocol}}
- Workforce Skill Profile: {{technician_certification_tier}}
- Risk Escalation Threshold: {{max_instruction_risk_level}}
Task
Produce a rigorous guardrail specification that prevents maintenance co-pilot agents from providing unauthorized, ungrounded, or hazardous troubleshooting steps to plant technicians.
Method
- Audit the source material in {{oem_manual_repository}} to construct deterministic retrieval filters.
- Define mandatory pre-condition checks matching {{lockout_tagout_protocol}} before any physical repair prompt is processed.
- Establish hallucination-blocking guardrails that abort responses when semantic grounding falls below threshold.
- Map step complexity and hazard ratings against {{technician_certification_tier}} to restrict high-risk instruction delivery.
- Specify deterministic blocking rules for procedures exceeding {{max_instruction_risk_level}} without human sign-off.
- Create multimodal image validation checks to confirm physical isolations prior to step progression.
- Construct a standardized fail-safe prompt response schema for ungrounded failure modes on {{equipment_class}}.
Constraints
- MUST NOT generate procedural sequences lacking explicit citation from {{oem_manual_repository}}.
- MUST halt conversational flows immediately if zero-energy state verification fails.
- Terminology must align strictly with OSHA 1910.147 and plant safety taxonomy.
- The specification must define clear, deterministic response refusal behaviors.
Output format
- Knowledge Grounding Rules (retrieval constraints and citation bounds)
- Safety-Gated Execution Flow (ordered conditional checkpoints)
- Tiered Escalation Matrix (table: Hazard Level, Skill Required, Approval Gate)
- Blocked Instruction Examples & Standard Safe Responses (3 concrete examples)
Self-review
- Does every high-consequence step mandate citation from {{oem_manual_repository}}?
- Is {{lockout_tagout_protocol}} enforced as an unskippable gate?
- Are technician certification boundaries unambiguously defined?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.