6a6c04d34b
- Update all submodule URLs from gitea.centraal.wbd-rd.nl to gitea.wbd-rd.nl - Add settler as proper submodule in .gitmodules - Add agent skills, function anchors, decisions, and improvements - Add Docker configuration and scripts - Add manuals and third_party docs - Update .gitignore with secrets and build artifacts - Remove stale .tgz build artifact Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2.2 KiB
2.2 KiB
name, description
| name | description |
|---|---|
| evolv-regulatory-compliance-wastewater | 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
- Identify compliance-relevant metrics and events.
- Trace data lineage from sensor/input to reported output.
- Verify timestamp/quality metadata sufficiency for audits.
- Review alarm/control actions that can affect permit outcomes.
- 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