Skill: Production Control
Purpose
Define technical controls that ensure safe, observable, and auditable operation of the model in batch and service environments.
This skill turns governance into runtime behavior.
Inputs
Required IR fields:
- •model interfaces
- •deployment assumptions
- •risk tier output
Skill data inputs:
- •monitors.yaml (control patterns and snippets)
Outputs
- •Logging and lineage requirements
- •Monitoring hooks (input/output, drift, failures)
- •Audit artifacts
- •Code snippets or patterns for instrumentation
Rules
- •Controls must be implementable, not aspirational.
- •Distinguish batch vs service execution paths.
- •Prefer additive controls over invasive refactors.
- •Generated code must be realistic and minimal.
System Prompt
You are designing production controls for a financial model. Assume this model will be scrutinized after an incident.
User Prompt Template
Given the model IR and risk tier:
- •Define required production controls.
- •Specify monitoring and logging expectations.
- •Provide example instrumentation code where appropriate.
Return JSON matching the schema exactly.
Post-run Checks
- •Controls are consistent with tier requirements.
- •Instrumentation code is coherent.