Scenario 02

---
name: review-agency-inspection-scenario-02
task_id: environmental-esg/review-agency-inspection/scenario-02
description: Guides preparation of a defense-oriented issues memorandum for a contested agency multi-media inspection by organizing findings medium-by-medium and assessing each allegation against facility records, monitoring data, and procedural documentation.
activates_for: [planner, solver, checker]
---

# Skill: Issue Identification Memorandum for Contested EPA Multi-Media Inspection of Chemical Manufacturing Facility

## 2. Failure modes the skill is correcting

- Baseline describes inspection findings without matching each allegation to the corresponding facility record set, monitoring period, and procedural document
- Baseline collapses separate media into a single compliance narrative, obscuring distinct air, water, and spill-prevention defenses
- Baseline omits procedural and evidentiary defects in the inspection process, including access documentation, sample handling, and the integrity of the inspection record
- Baseline ignores prior response correspondence as contemporaneous evidence of the client’s position and as a source of admissions, clarifications, or inconsistencies
- Baseline states conclusions without tying them to the governing regulatory authority or the specific record support

## 3. Legal frameworks / domain conventions that apply

- Agency inspection authority: identify the governing statute, regulation, or permit authority for entry, inspection, sampling, and record review; evaluate whether the inspection steps complied with the cited authority
- Air compliance framework: emission limits, monitoring obligations, recordkeeping, reporting, and deviation procedures under the applicable permit and air program rules
- Water compliance framework: discharge limits, discharge-monitoring obligations, sampling integrity, and reporting conditions under the applicable permit and water program rules
- Spill-prevention framework: plan requirements, inspection obligations, containment requirements, amendment timing, and implementation duties under the applicable spill-prevention rules
- Evidentiary integrity: sample collection, chain of custody, access logs, timestamps, and document provenance may affect the reliability or admissibility of specific findings
- Inspection record accuracy: the report should fairly reflect observed conditions, the facility’s contemporaneous explanations, and any correcting documentation
- Penalty posture: gravity, economic benefit, compliance history, good-faith cooperation, prompt correction, and current compliance status may affect enforcement and settlement posture
- Governing authorities should be cited by name and section, part, or comparable identifier when stating the legal rule supporting a defense or mitigation point

## 4. Analytical scaffolds

- First enumerate the inspection findings by medium and subtopic before analyzing them; if the source set shows only one finding in a category, state that expressly
- For each finding, identify: the inspection allegation, the governing authority invoked, the facility record set that bears on it, and the factual dispute or defense theory
- For air findings, compare the report to emissions workbooks, operating logs, deviation records, and reporting history for the relevant period
- For water findings, compare the report to discharge-monitoring records, sampling logs, analytical results, and any contemporaneous explanations for anomalies
- For spill-prevention findings, compare the report to the written plan, inspection checklists, amendment history, training materials, and implementation records
- For procedural defects, evaluate access documentation, inspector credentials or notice materials, chain-of-custody forms, sample preservation, and any gaps or inconsistencies in the inspection chronology
- For prior correspondence, map each prior statement to the current issue set and flag where the correspondence supports, qualifies, or conflicts with the present defense
- For each issue, close the analysis with three moves: the scale of the issue as shown in the records, the related document or rule that interacts with it, and the practical consequence for defense, enforcement exposure, or mitigation
- Classify each issue as defensible, partially defensible, or conceded with mitigation, and give a brief reason for the classification
- Where the record supports it, separate a substantive compliance defense from a procedural or evidentiary defense rather than merging them

## 5. Vertical / structural / temporal relationships

- Treat prior response correspondence as a contemporaneous record that can strengthen or weaken the current position; reconcile any inconsistencies proactively
- Assess whether cited conditions were isolated, repeated, corrected before or after inspection, or reflected in later monitoring; timing affects both liability theory and penalty posture
- Trace cross-media relationships only where supported by the source set, such as operational conditions affecting multiple programs or a spill event affecting both containment and discharge issues
- Distinguish historical conditions from present conditions so the memo can address both alleged noncompliance and current remediation status

## 6. Output structure conventions

- Draft as a defense-oriented issues memorandum in conventional legal memo form, with a concise executive summary followed by issue-by-issue analysis organized by regulatory medium
- Include a short severity label for each issue using a consistent ordinal scale defined once at the start of the analysis section
- For each issue, state the allegation, controlling authority, record support, defense theory, classification, and recommended response
- Keep factual assertions tied to the source set; do not generalize beyond the inspection record and supporting documents
- Include a distinct section for procedural and evidentiary issues, a distinct section for penalty mitigation, and a distinct recommended actions section
- In the recommended actions section, use imperative verbs, identify the responsible role or function, and anchor timing to a deadline, inspection milestone, response due date, or similar regulatory milestone
- Do not present a legal conclusion without naming the authority that supports it
- Deliverable filename must match the task instructions exactly