> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aquaops.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Compliance Guide

> Current compliance behavior in AquaOps and the near-term direction of the platform.

This page explains the current compliance behavior and the near-term direction of the platform.

## Current compliance features

Implemented today:

* audit logging foundation
* chemistry status evaluation
* Illinois-based chemical defaults in the seed configuration
* closure-threshold support for configured chemical fields
* closure warning messaging on affected chemical record detail pages
* comment and history support on chemical records
* manual closure incidents with reopen/resolve flow
* evidence attachments and corrective actions
* scheduled closures kept separate from compliance incidents
* facility-status, exception-ledger, and timeline views

## Illinois water quality defaults

The seeded demo chemical profile uses Illinois-oriented defaults based on `77 Ill. Admin. Code 820`.

Examples:

* free chlorine ideal 1.0 to 4.0 ppm
* free chlorine closure below 0.5 ppm
* total chlorine closure above 5.0 ppm
* pH closure below 6.8 or above 8.0
* cyanuric acid alert above 100 ppm

These are defaults, not forced values. Each pool profile can be adjusted.

## Current limitation

The system now has the core compliance workflow, but the deeper reporting layer is still incomplete:

* inspection packets
* manager digest emails
* jurisdiction-specific checklist/template support
* advanced inspector-facing reporting

## Current recommended operating procedure

<Steps>
  <Step title="Log the reading">
    Log the chemical record accurately.
  </Step>

  <Step title="Review status">
    Review the status on the detail page.
  </Step>

  <Step title="Open a closure incident if needed">
    If the record shows `closure_required`, open or review the linked closure incident.
  </Step>

  <Step title="Document follow-up">
    Add notes, evidence, and corrective actions inside the incident record.
  </Step>

  <Step title="Use scheduled closures for planned downtime">
    Use scheduled closures only for planned downtime such as holidays or maintenance windows.
  </Step>

  <Step title="Preserve records">
    Preserve records rather than deleting them unless necessary.
  </Step>
</Steps>

## Current compliance workflow highlights

* closure incidents are manual and can optionally reference a chemical record
* resolution requires attestation, not a structured retest workflow
* comments act as the incident notes thread, including any follow-up readings
* evidence uploads cover photos, PDFs, SOPs, and handwritten sheets
* corrective actions are structured follow-up tasks inside the incident

## Scheduled closures vs. compliance closures

The roadmap distinguishes:

* scheduled closures
  Examples: weekends, holidays, facility days off
* compliance closures
  Examples: closure-threshold chemistry or visibility failures

That separation is important so planned downtime is not mixed with health or regulatory incidents.