# Identify Issues In State Environmental Compliance Order

> Guides preparation of a defense memorandum for a state environmental compliance order by assessing each alleged violation against facility permit records, audit findings, inspection documentation, and monitoring data.

- Skill: `finchipaiorg/identify-issues-in-state-environmental-compliance-order` (Agent Skill)
- Install (CLI): `npx skillmds@latest add finchipaiorg/identify-issues-in-state-environmental-compliance-order`
- Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/identify-issues-in-state-environmental-compliance-order/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: FinchipAIOrg (https://skillmd.com/u/finchipaiorg)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/finchipaiorg/identify-issues-in-state-environmental-compliance-order

---


# Skill: Identify Issues in State Environmental Compliance Order — Issue Memorandum

## 1. Subject-matter triage
- Confirm the enforcement posture: NOV, compliance order, consent proposal, or hybrid state/federal action.
- Identify each regulated medium implicated by the source set, then separate the analysis by program before any merits assessment.
- Determine whether the facility is facing one state action or multiple coordinated actions; analyze each jurisdiction on its own authority, deadlines, and penalty posture.
- If the source set includes a voluntary audit, privilege claim, or self-disclosure, flag it immediately for mitigation analysis and privilege-sensitive handling.

## 2. Failure modes the skill is correcting
- Reviews the allegations in the order without tying each count to the governing permit condition, rule, or monitoring obligation.
- Collapses air, water, waste, stormwater, and other program violations into one generalized response instead of analyzing each media-specific record set.
- Ignores pre-existing audit findings or corrective actions that may support good faith, reduced culpability, or mitigation.
- Relies on the order’s narrative without testing it against permits, DMRs, manifests, inspection notes, logbooks, calibration records, and chain-of-custody materials.
- Treats multiple states, agencies, or programs as a single enforcement track even where each has separate authority and settlement consequences.
- States defenses abstractly without identifying the controlling regulation, permit section, or enforcement standard supporting the position.
- Describes problems without closing each issue with scale, document cross-reference, and downstream consequence.
- Fails to end with concrete response steps tied to responsible roles and timing.

## 3. Legal frameworks / domain conventions that apply
- State air enforcement typically turns on permit conditions, emissions limits, monitoring, opacity observations, deviation reporting, and inspection authority.
- State water enforcement typically turns on effluent limits, sampling methods, DMR accuracy and timeliness, stormwater terms, and certification requirements.
- State waste enforcement typically turns on generator status, container management, accumulation time, manifesting, shipping records, and land-disposal related requirements.
- Temperature-controlled waste or process-stream rules, where present, depend on logs, calibration, and recording integrity.
- Voluntary environmental audit statutes or policies, where available, may provide privilege, immunity, or penalty mitigation if the facility meets statutory prerequisites.
- State penalty assessment frameworks commonly consider gravity, economic benefit, compliance history, cooperation, and promptness of correction.
- Where the order cites a regulation, permit term, or guidance document, use that citation as the primary authority and align the defense to the exact section or condition.
- Where a generally recognized enforcement or privilege rule is needed, name the rule or statute expressly rather than implying it.

## 4. Analytical scaffolds
- Start by enumerating every alleged count, citation, program, and cited period in the source set before analyzing the merits.
- For each count, extract four core items: the allegation, the controlling authority, the agency’s evidence, and the facility record that bears on it.
- Then assess whether the record supports a complete defense, a partial defense, or a concession with mitigation.
- For each issue, close the analysis with three moves:
  - scale the issue using a figure or threshold from the source documents;
  - cross-reference the interacting permit term, record, or related document;
  - state the practical consequence for the client if the issue stands.
- Use the facility’s own records as the primary factual check: permits, renewal applications, audit reports, inspection notes, DMRs, manifests, shipping papers, calibration logs, and corrective-action tracking.
- For air issues, compare the cited observation or exceedance against permit language, contemporaneous readings, and any pre-inspection audit finding.
- For water issues, compare the reported discharge against sample dates, analysis methods, outfalls, certification, and submission timing.
- For waste issues, test accumulation dates, container status, and manifest chronology against the cited rule and the actual operating records.
- For audit-related mitigation, identify whether the facility discovered the issue first, corrected it before the order, or disclosed it through a protected channel.
- Separate legal insufficiency from factual rebuttal; do not merge a missing citation with a disputed measurement.
- When the record is incomplete, identify the missing proof and explain whether the gap helps or hurts the defense.

## 5. Vertical / structural / temporal relationships
- Treat the timeline as part of the defense: pre-inspection conditions, inspection date, order date, and post-order corrective actions each matter.
- If the internal audit predates the inspection, analyze whether it shows prior detection and remediation, even if the final defense still concedes a technical violation.
- If the agency relied on post-inspection sampling or later-developed data, test whether it fairly reflects the cited period.
- If more than one enforcement body is involved, separate any resolution leverage, penalty effect, or compliance schedule issue by jurisdiction.
- If corrective action began before the order, document it as mitigation and as a reason to narrow the requested relief.
- If the order demands a compliance schedule, compare it to operational lead times, procurement needs, shutdown constraints, and other practical milestones in the record.

## 6. Output structure conventions
- Write as a defense memorandum, not a narrative memo of facts.
- Use an opening summary, then a count-by-count analysis grouped by medium, then a penalty and mitigation section, then a recommended response section.
- Include an explicit severity label for each issue using a consistent ordinal scale defined once at the top of the memorandum.
- For each issue, state:
  - severity;
  - allegation;
  - controlling authority;
  - evidence for the agency;
  - record-based defense or concession point;
  - classification as defensible, partially defensible, or conceded with mitigation;
  - recommended response.
- Keep the authority citations specific to the cited permit, rule, regulation, or statute; do not rely on generalized statements of law.
- If multiple counts or periods are present, give each its own entry rather than collapsing them into a single mixed analysis.
- End with a Recommended Actions section that uses imperative verbs, assigns the responsible role where the source set identifies one, and ties each step to a deadline, inspection milestone, response deadline, or other regulatory timing anchor.
- Preserve the task output filename exactly as instructed: `conov-issue-memorandum.docx`.