Security and compliance

Software that can move a setpoint in a water plant needs more than a good model.

Hydrira is designed around three facts: treatment plants are critical infrastructure, their output is public health, and the plant's existing automation must keep running if Hydrira stops. This page is the design posture; certifications are on the roadmap and not claimed.

Permit limits read, never writtenTenant isolation by designSOC 2 on the roadmap

run_scn_0418 · agent graph · scenario 10 nodes · 1 approval gate
01 · intake_screen Read influent and forecast ✓ SUCCEEDED 02 · orchestrator Rehearse the next 24 hours ✓ SUCCEEDED 03 · quality_anomaly Fuse cameras and analyzers ✓ SUCCEEDED 04 · dose_coagulate Compute the dose curve ✓ SUCCEEDED 05 · dose_coagulate Trim the coagulant setpoint ✓ SUCCEEDED 06 · aerate_bio Minimum-energy DO schedule ✓ SUCCEEDED 07 · orchestrator Blower move approved ◆ APPROVAL 08 · membrane_disinfect Flux hold and backwash timing ✓ SUCCEEDED 09 · compliance_energy Permit conformance check ✓ SUCCEEDED 10 · conformance Write the shift record ✓ SUCCEEDED

Illustrative scenario: one municipal activated-sludge wastewater plant with a membrane train, planning the next 24 hours after a rain forecast. Not a measured run.

Defense in depth

Six layers between a model and a setpoint

01

Allow-list

An agent can only write to tags declared for it.

02

Limits

Per-tag rate and magnitude limits, declared and versioned, inside documented process, permit, equipment and rollback bounds.

03

Stage

Shadow, assist or bounded, set per loop; nothing writes in shadow.

04

Policy engine

Interlock state, permit margin, excursion forecast, shift and operator presence evaluated before every write; a move that would thin a permit margin, a disinfection residual minimum or an integrity limit is blocked.

05

Human gate

Anything above the threshold, every permit-adjacent move and every discharge release waits for a named person.

06

Fallback

If Hydrira stops, the plant runs on its existing SCADA, PLC and DCS control and interlocks.

Tool calls

Every call, on the record

Every tool invocation, argument and result is written to an immutable, human-readable log, and every reasoning step is expandable. Nothing about a run is hidden from the plant. The log below is the scenario run, not a measured one.

tool-call stream · run_scn_0418
  1. 05:40:02scada.read_influent({ plant: "WWTP-A", tags: ["FLOW", "NTU", "NH4", "ALK"] })
  2. 05:40:03ok flow 412 L/s · turbidity 118 NTU · ammonia 31 mg/L · alkalinity 184 mg/L
  3. 05:40:03weather.read_forecast({ horizon_h: 24 })
  4. 05:40:04ok rain from 14:00 · expected influent +38% by 17:00
  5. 05:40:04twin.simulate({ horizon_h: 24, candidates: 240, objective: ["permit_margin", "kwh", "chemical"] })
  6. 05:44:14ok 240 plans evaluated · 31 hold permit margin through the surge · best plan selected
  7. 05:44:15vision.fuse_state({ cameras: ["CLAR-1", "CLAR-2", "AER-3"], analyzers: "all" })
  8. 05:44:15ok blanket 1.1 m · foam none · effluent turbidity 1.8 NTU · residual 0.9 mg/L
  9. 05:44:16cuopt.solve_dose({ window_h: 12, constraints: ["NTU", "P", "sludge", "cost"] })
  10. 05:44:18ok coagulant ramp 38 → 46 mg/L from 13:30 · polymer unchanged · cite sop:DOSE-07 §3
  11. 05:44:19policy.evaluate({ loop: "dose", stage: "bounded", tag: "DOS1.SP" })
  12. 05:44:19ok permitted · max_step 4 mg/L per 15 min · rollback 38 mg/L
  13. 05:44:19plc.write_setpoint({ tag: "DOS1.SP", value: 42, unit: "mg/L" })
  14. 05:44:20ok written · ack from PLC · audit id 0418-05
  15. 05:44:20cuopt.solve_blowers({ basins: 4, constraints: ["NH4", "NO3", "P", "DO_min"] })
  16. 05:44:23ok DO 2.0 → 1.6 mg/L basins 1–3 from 06:00 · predicted −9% kWh · nutrient margin held
  17. 05:44:24policy.evaluate({ loop: "aeration", stage: "assist", tag: "BLW.DO_SP" })
  18. 05:44:24above threshold for this loop · routed to approve.human · engineer on shift notified
  19. 05:50:26approved by the process engineer on shift · reason: nutrient margin 0.6 mg/L above limit
  20. 05:50:27membrane.schedule_backwash({ train: "MBR-2", surge_at: "14:00" })
  21. 05:50:29ok flux held 24 LMH · backwash moved 16:00 → 13:15 · residual minimum untouched
  22. 05:50:29permit.evaluate({ permit: "NPDES-WWTP-A", horizon_h: 24 })
  23. 05:50:30ok all parameters inside limit · excursion risk 24 h: low · cite permit §II.A
  24. 05:50:30audit.commit({ run: "run_scn_0418", steps: 10, approvals: 1 })
  25. 05:50:30ok shift record written · immutable · exportable

Reasoning trace

Goal, plan, thought, action, observation, exactly as the orchestrator would record it.

GoalHold effluent turbidity, nutrients and disinfection residual i…

Hold effluent turbidity, nutrients and disinfection residual inside the discharge permit for the next 24 hours while taking aeration energy and coagulant use to the minimum the permit margin allows.

PlanRead influent and the forecast; rehearse the horizon on Simflo…

Read influent and the forecast; rehearse the horizon on Simflo; fuse the plant state; compute dose and DO schedules; write the dose inside bounds; route the DO move for approval; hold flux and move the backwash; check the permit; commit the record.

ThoughtRain arrives mid-afternoon and the influent will rise by about…

Rain arrives mid-afternoon and the influent will rise by about a third. Dosing has to ramp before the surge, not after, and the DO schedule has to keep nutrient margin through it.

Actioncuopt.solve_dose over a 12-hour window under turbidity, phosph…

cuopt.solve_dose over a 12-hour window under turbidity, phosphorus, sludge and cost constraints; plc.write_setpoint on the coagulant pump inside the declared rate and magnitude limits.

ObservationThe dose ramp holds predicted effluent turbidity under 2 NTU t…

The dose ramp holds predicted effluent turbidity under 2 NTU through the surge. The DO schedule saves energy but is above the threshold set for the aeration loop.

ThoughtEnergy never outranks permit margin. The DO change goes to the…

Energy never outranks permit margin. The DO change goes to the engineer with the predicted nutrient margin attached, and nothing is written until it is approved.

Actionapprove.request to the process engineer on shift; membrane.sch…

approve.request to the process engineer on shift; membrane.schedule_backwash to hold flux and move the next backwash ahead of the surge; permit.evaluate across the horizon.

OutcomeTen steps, one human approval, all parameters inside limit on …

Ten steps, one human approval, all parameters inside limit on the forecast, and the shift record written. Illustrative scenario; nothing here is a measured plant result.

Guardrails

An agent that can move a setpoint needs a leash

Hydrira writes to control equipment in a plant that keeps a community's water safe. Every capability is scoped, every write is policy-checked, every output is cited, and every action is written to an append-only audit log the plant owns.

  • Bounded action space. Each agent can only write to an explicit tag allow-list, inside per-tag rate and magnitude limits, at the autonomy stage the plant has set.
  • Permit limits are read, never written. Permit-limit setpoints, disinfection residual minimums, integrity limits and discharge release decisions stay with the permit and the operator of record.
  • Policy engine before every write. Autonomy stage, interlock state, permit margin, excursion forecast and operator presence are evaluated before a setpoint moves.
  • Grounded and cited. Every recommendation carries a citation to the permit, SOP or regulation it relied on. Retrieval is tenant-isolated and permission-aware.
  • Immutable audit log. Append-only, exportable and retained on the plant's own storage, aligned to Safe Drinking Water Act, discharge-permit and EU Water Framework record-keeping.
  • Hard fallback. If the edge node, the network or a model stops, the plant keeps running on its existing SCADA, PLC and DCS control and interlocks.
  • Tenant isolation and critical-infrastructure posture. Telemetry, permits, SOPs and models never cross a customer boundary. On-prem and edge-only deployment available for utilities.

Assurance posture

Assurance and certification status
ItemScopeStatus
SOC 2 Type I + critical-infrastructure cyber reviewCloud control plane, edge QUEUED Roadmap, first 6 months
SOC 2 Type IICloud control plane QUEUED Roadmap, 6 to 12 months
SDWA · discharge permits · EU WFD · nutrient and PFAS rulesGrounding and record-keeping RUNNING Design basis for retrieval and the audit log
Per-tenant isolationData, memory, models RUNNING Design rule
On-prem or edge-only deploymentUtilities, critical infrastructure RUNNING Design option

Hydrira supports your compliance records. It is not a certification, it does not replace your permit and it never removes the operator of record from a compliance decision.

Read the security overview

Autonomy

Four stages, set per loop

A plant does not go from manual to bounded control in one step. Hydrira makes the stage explicit per loop, auditable and reversible at any time, and some decisions never leave the person.

Autonomy stages and the human role at each
StageWhat the agent doesWhat the person doesWhen
ShadowPredicts water quality, fouling, excursion risk and energy; writes nothingRuns the plant as today; compares predictions to lab, analyzer and SCADA outcomesFirst phase with every design partner
AssistRecommends dose, DO, flux and cleaning moves with predicted quality, energy and permit impactApproves, corrects or rejects each move; corrections train the modelsAfter accuracy is proven against the plant's own baseline
BoundedWrites to an allow-list of low-risk loops inside declared rate and magnitude limitsSets the limits, watches the record, pulls the loop back at any timePer loop, after the assist-mode gate and compliance sign-off
ExceptionsEscalates anything above the threshold, every permit-adjacent move and every releaseDecides; the operator of record is never removed from compliance decisionsAlways
Assurance

Certification status

Stated plainly. Items on the roadmap are roadmap items.

Assurance items and status
ItemScopeStatus
SOC 2 Type ICloud control plane QUEUED Roadmap, first 6 months
Critical-infrastructure cybersecurity reviewEdge and connectors QUEUED Roadmap, first 6 months
SOC 2 Type IICloud control plane QUEUED Roadmap, 6 to 12 months
Compliance and cyber assurance packagesDesign partners QUEUED Roadmap, 6 to 12 months
Safe Drinking Water Act, discharge permits, EU Water Framework, nutrient and PFAS rulesGrounding and records RUNNING Design basis; not a certification of Hydrira
IP-safe and edge-only deploymentPlant data, permits, SOPs RUNNING Design rule; on-prem option
OT safety

Failing safe is a design requirement

  • Supervisory, not primary. Hydrira sits above existing SCADA, PLC and DCS control; it never replaces an interlock or a safety system.
  • Permit limits are read-only. Permit-limit setpoints, disinfection residual minimums and integrity limits are checked and logged, never written.
  • Release is human. The conformance agent assembles the shift record and checks it against the permit; the operator of record releases.
  • Loss of Hydrira is loss of advice. The plant degrades to the way it runs today, not to a stop.

What leaves the plant, and when

Data flows
DataWhere it stays
SCADA tags, analyzer streams, imagesTenant-scoped; on-prem or edge-only option
Permits, SOPs, process modelsTenant-scoped
Audit log and shift recordThe plant's own storage, exportable
Surge, fouling and upset patternsFederated, IP-isolated transfer across similar plant archetypes (planned, opt-in)
Multi-agent handoff

Agents negotiate, they do not collide

Two agents will want the same actuator. The orchestrator arbitrates on the run goal, with permit margin above everything, and the handoff is logged like any other step.

Dose-and-Coagulate and Aerate-and-Bio both want phosphorus

  1. 01Conflict detected SUCCEEDED0.2 s

    Chemical phosphorus removal (more coagulant) and biological phosphorus removal (more aeration) both reach the target; each agent proposes its own route.

  2. 02Orchestrator arbitrates SUCCEEDED1.4 s

    Simflo scores both routes on permit margin, kilowatt-hours and chemical cost over the horizon; the permit margin is identical, so cost decides.

  3. 03Plan handed back SUCCEEDED0.3 s

    The biological route wins for this shift; the dosing agent holds coagulant at the clarity dose and the aeration agent takes the phosphorus target.

  4. 04Both requests logged SUCCEEDED0.1 s

    Both proposals, the arbitration and the chosen route are written to the shift record so a process engineer can see why.

Arbitration rules

  • Permit margin outranks everything. No arbitration may thin a permit margin, a disinfection residual minimum or an integrity limit, whatever it saves.
  • Health and safety outrank cost. Where a route touches disinfection or pathogen removal, the conservative route wins by rule.
  • The orchestrator decides, the agents do not negotiate directly. An agent never writes to another agent's actuator.
  • Arbitration is a step. It is typed, timed and logged like any other, and it is reversible.

See the agent roster

Enterprise

Standardize autonomy across the fleet

One policy model, one audit trail and one set of energy, chemical, compliance and water-quality benchmarks across every plant in the fleet, with each site's permits, SOPs and process models kept private to that site.

Talk to us Enterprise details

  • Multi-site plant-edge fleet with shared model governance
  • Custom process, compliance and energy models per site
  • SSO and role-based access, named approvers (roadmap, 6 to 12 months)
  • Model versioning, validation reports and rollback
  • On-prem or private-cloud deployment
  • SLAs and outcome-based components on the highest-value workflows
FAQ

Straight answers

The questions operations managers, process engineers and compliance leads ask in the first meeting.

Only at the autonomy stage your plant has set, and only to an explicit allow-list of low-risk loops inside documented limits. Every design partner starts in shadow mode, where Hydrira predicts and writes nothing. Assist mode follows, where a process engineer approves each move. Bounded write-back comes last, per loop, after the accuracy gate and compliance sign-off, and can be pulled back at any time.

Get started

Get the security pack

The design posture, the data flows and the roadmap dates, written for a compliance lead and an IT/OT security lead.