Energy Regulatory Filing Review with Claude Code: API Runtime Pattern
A production playbook for energy regulatory filing review in energy operations using Claude Code: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Energy compliance teams
The problem
Energy compliance teams need energy regulatory filing review to run repeatedly against filings, permits, inspection reports, meter data, and regulator correspondence. In energy operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the energy regulatory filing review instructions as a skill, send filings, permits, inspection reports, meter data, and regulator correspondence as run-scoped inputs, execute with Claude Code, poll terminal status, and consume argo.result.v1 instead of parsing a transcript.
Tradeoffs and failure modes
The API boundary forces the workflow to define inputs, terminal states, and result shape before customers depend on it. For energy regulatory filing review, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Run request
POST /api/skills/<skill_id>/run
provider=claude-code
workflow=energy-regulatory-filing-review
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo