54 lines
2.2 KiB
Markdown
54 lines
2.2 KiB
Markdown
|
---
|
||
|
|
name: evolv-regulatory-compliance-wastewater
|
||
|
|
description: Apply wastewater regulatory and compliance constraints to EVOLV control and telemetry design. Use when reviewing effluent-quality KPIs, reporting semantics, auditability, traceability of control actions, and compliance-impacting alarm/control decisions.
|
||
|
|
---
|
||
|
|
|
||
|
|
# EVOLV Regulatory Compliance Wastewater
|
||
|
|
|
||
|
|
## Mission
|
||
|
|
Ensure EVOLV changes remain auditable and aligned with wastewater compliance/reporting obligations.
|
||
|
|
|
||
|
|
## Harness Execution Contract
|
||
|
|
- Map compliance-relevant outputs and control decisions from current repo contracts.
|
||
|
|
- Define invariants before edits:
|
||
|
|
- compliance KPIs remain traceable
|
||
|
|
- auditability of major control actions is preserved
|
||
|
|
- reporting semantics are stable or explicitly migrated
|
||
|
|
- Validate with evidence that supports audit/review workflows.
|
||
|
|
|
||
|
|
## Scope
|
||
|
|
- Effluent-related outputs and quality calculations in process nodes
|
||
|
|
- Alarm and control behaviors that affect permit-critical operation
|
||
|
|
- Telemetry/reporting contracts consumed by dashboards/reports
|
||
|
|
|
||
|
|
## Workflow
|
||
|
|
1. Identify compliance-relevant metrics and events.
|
||
|
|
2. Trace data lineage from sensor/input to reported output.
|
||
|
|
3. Verify timestamp/quality metadata sufficiency for audits.
|
||
|
|
4. Review alarm/control actions that can affect permit outcomes.
|
||
|
|
5. Define documentation and test evidence for compliance-critical paths.
|
||
|
|
|
||
|
|
## Standards
|
||
|
|
- Prefer explicit semantics over inferred compliance logic.
|
||
|
|
- Preserve historical comparability of compliance KPIs.
|
||
|
|
- Ensure traceability of overrides, trips, and degraded operation.
|
||
|
|
- Keep evidence artifacts reproducible and review-friendly.
|
||
|
|
|
||
|
|
## Test Expectations
|
||
|
|
Cover:
|
||
|
|
- compliance KPI payload consistency
|
||
|
|
- traceability fields presence (timestamp/source/quality where applicable)
|
||
|
|
- alarm/control transitions relevant to permit risk
|
||
|
|
- behavior under missing or suspect compliance measurements
|
||
|
|
|
||
|
|
## Deliverables
|
||
|
|
Return:
|
||
|
|
- compliance impact map and assumptions
|
||
|
|
- changed files/tests with audit-focused evidence
|
||
|
|
- unresolved compliance risks and mitigation recommendations
|
||
|
|
|
||
|
|
Decision interview triggers:
|
||
|
|
- any change that can alter reported compliance values
|
||
|
|
- changed retention/backfill semantics for compliance reporting
|
||
|
|
- reduced auditability or traceability in control/telemetry paths
|