Main site

Mining AI agent · Discharge certification

Water Discharge & Exceedance Certification AI Agent

Build the discharge monitoring pack behind an outfall value, run the exceedance clock from a time a person entered, and hold the pack for the officer whose signature carries it.

Typical delivery
4–6 weeks
Deployment
Your stack
Officer signs
Pre-signature
After launch
Agent Care

What this agent does

Assembles the pack, not the certification

In

  1. 01

    A sample is taken at an outfall, and the custody form, the sampler named on it and the laboratory job come with it.

  2. 02

    A result returns, and its QC status, its holding time and the analytical method are carried with the value.

Reason

  1. 03

    A value is compared against the permit limit held for that outfall, on the averaging basis that permit sets.

  2. 04

    A limit is exceeded, and the pack fixes the outfall, the value and the time the result was first read.

  3. 05

    A clock runs from that entered time, with the oral and written windows of 40 CFR 122.41(l)(6) beside it.

Decide

  1. 06

    A reportability question stays open on the pack, marked open, until a named person answers it.

  2. 07

    A non-compliance narrative and a corrective-action record are drafted from the logs the site kept at the time.

Out

  1. 08

    A record is retained under 40 CFR 122.41(j) for the period it sets, naming who sampled and who analysed.

  2. 09

    A write runs only inside the approval boundaries agreed at implementation, and never ahead of the signature.

Product statement

The agent assembles and compares; the named officer certifies under 40 CFR 122.22(d) and personally carries what a knowing false statement attracts.

Example workflow

One outfall, sample to certification

  1. 1Sample receivedField sampling round, contractor custody form or laboratory portal
  2. 2Pack assembledCustody records, laboratory data and QC, permit limits and site logs, each with its source
  3. 3Comparison runOutfall values, limit basis, flagged exceedances and confidence
  4. 4Controls appliedCustody and QC checks, limit-basis checks, signatory-authorisation checks and confidence threshold

No human action required

Stages 1 to 4 run unaided, and nothing is certified at any of them — the agent is assembling, and the officer's lane opens at the confidence gate.

5DecisionBranches at the confidence threshold
High confidence

Goes to the named officer to certify.

Low confidence

Adds an environmental-lead read first.

Officer certification

The pack is held with its evidence, its open questions and the confidence.

Approve · Amend · Send to second read

Certified — report released

  1. 6Reporting system updatedOnly where write access and approval policy allow it
  2. 7Outcome evaluatedPack completeness, amendment rate, notification timeliness and inspection findings

Amendments

A corrected report goes out, and the late notification is itself the violation.

What should not run autonomously

Human approval stays in control

Outside the boundary — human approval required

8 items

  • Signing the certification statement on the report.
    • Deciding whether an event is reportable.
    • Making the oral or written notification to the regulator.
    • Judging whether an upset or bypass defence holds.

  • Automation boundary

    Agent acts unaided

    • ✓Assemble the pack from custody, laboratory and permit records.
    • ✓Compare each outfall value against the limit on file.
    • ✓Run the notification clock forward from the entered time.
    • ✓Name what is unresolved and hold the pack for the certifying officer to read.

    Writes stay inside the boundaries agreed at implementation, and never ahead of the certification.

    • Authorising a signatory, or filing that authorisation.
    • Accepting a laboratory result that failed its QC.
    • Approving a corrective action or calling it complete.
  • Changes to limit rules, clocks or approval thresholds.

Example output

One outfall value, annotated

Everything the agent assembles is attached to the record it was drawn from.

Certification pack output · single outfall

Illustrative example
Outfall
Treatment-circuit outfall
Drafted line
The monthly value sits above the limit written for this outfall
Clock cited
40 CFR 122.41(l)(6)
Source of time
Officer-entered
Confidence
88%
Clock
Runs from the entered time

As received

Taken from the custody, laboratory and permit records — nothing on this side is written by the agent.

Evidence used

  • Chain-of-custody form
  • Laboratory QC batch
  • Permit limit page

Why this basis

It is the averaging basis the permit sets, and a person still decides what follows.

What the score decides

Below the configured threshold the pack picks up an environmental-lead read.

Action

ApproveAmendSend to second read

Value

Where AI adds value

The same four claims, placed at the point in the workflow where each one applies.

Where the value lands

Value 01 – 04

Every outfall

From the sample record

03Assembly

Take the part tenement tracking

The tenement agent tracks what a tenement obliges you to do; this one assembles the report an officer certifies.

01Approved path

A named officer certifies

Routine monthly values arrive already compared, with their evidence attached.

02Human review

Send review to the exceedances

A flagged value, an unresolved QC batch or a signatory that no longer matches is marked before the officer reads.

04

Build an evidence trail

The sample, the limit it was measured against and the officer who certified stay on the report.

Integrations

Typical integrations

Five system groups connect to the same agent. Which of them are in scope is decided in discovery.

  • Laboratory data

    • LIMS
    • EDD deliverables
    • Contract laboratory portals

  • Field and sampling

    • Custody forms
    • field meters
    • Site rain and flow gauges

  • Permit and limits

    • Permit register
    • limit tables
    • Outfall and monitoring plan

Agent

Discharge certification

  • Reads the sample
  • Compares to the limit
  • Holds for certification

  • Reporting and records

    • NetDMR
    • state e-reporting
    • Records archive
    • retention

  • Observability & evaluation

    • OpenTelemetry
    • Langfuse
    • Supported monitoring/evaluation sources

Integration availability depends on the client's existing systems and API access.

Agent controls

Six layers between the model and the report

The six nest tightly, outer to inner. What escapes all six is listed in the map below.

L6 · Outermost — last line of defence

Inward → L1 · closest to the model

L6Rollback / safe modeHold assembly at draft-only when evaluation or production signals degrade.Roll back
L5Version monitoringTrack model, prompt, limit-rule and permit-configuration changes.Track
L4Pack traceabilityRecord the sources, the comparison, the amendments and what stayed unresolved.Record
L3Officer certificationHold packs for the named officer; the gate governs release, not whether the certified value is right.Gate
L2Policy guardrailsTest packs against custody, QC, limit-basis and signatory rules; a failure returns the pack.Restrict
L1Confidence thresholdsRoute low-confidence packs to an environmental-lead read before the officer sees them.Require review
Model corePack assembled — outfall values, limit basis, flagged exceedances and confidence
L1 – L2
Test whether a value may stand
L3
Puts the certification in the officer's hands
L4 – L5
Keep the sample and the limit behind it
L6
Holds the report at uncertified when signals degrade

How Nestack evaluates it

Evaluate the assembly workflow — not only the finished report.

Coverage runs the whole depth of the workflow, and every layer is cut by slice.

Surface — the report the regulator reads

  1. E1Final-output evaluationDid each value in the pack match the record it came from?
  2. E2Step-level evaluationDid the agent use the right outfall, the right limit and the right basis?
  3. E3Tool evaluationDid it read and write the correct outfall and the correct field?
  4. E4Confidence calibrationDo low-confidence packs actually attract more officer amendments?
  5. E5Slice evaluationHow does performance change across specific outfall types?
  6. E6Business outcomeHow many packs reached the officer unresolved, and how many reports were corrected after?

Floor — the outcome the permittee answers for

Failure modes

Where each failure originates in the agent

Seven failure modes, each placed at the stage where it originates.

Agent lifecycle

Direction of processing →

  1. 01 · Retrieval

    1 mode

    • DM-03

      Superseded limit value

      The limit came from a record the modification replaced.

    Stage gathers

    Custody records, laboratory data and permit limits

  2. 02 · Reasoning

    2 modes

    • DM-04

      Awareness timed to the inbox

      The clock is dated from when the report was opened.

    • DM-06

      Averaging basis misapplied

      A monthly average is run against a daily limit.

    Stage proposes

    Outfall values, the limit basis and confidence

  3. 03 · Tool / write

    2 modes

    • DM-02

      Reportability closed by silence

      An open question leaves the pack as though settled.

    • DM-05

      Sample type not checked

      A grab stands where the permit sets a composite.

    Stage writes

    Only where write access and approval policy allow it

  4. 04 · Output

    1 mode

    • DM-01

      Signatory not on file

      The named signer does not match the authorisation filed.

    Stage returns

    The pack the officer certifies and the regulator reads

  5. 05 · Change / Version

    1 mode

    • DM-07

      Silent limit-rule regression

      A model or rule change loosens what is flagged.

    Stage tracks

    Model, prompt, limit rules and permit config

  • Sev-1 · certified outside the boundary
  • Sev-2 · a wrong value reaches the report
  • Sev-3 · lab data degrades, pack holds
See the complete Mining failure-mode catalogue

Affected slices

One outfall can carry most of the exceptions

An outfall-level certification-readiness figure can look settled while a few outfalls absorb most of the unresolved items. Nestack reports the unresolved-item rate by outfall, not only in total.

Slice performance — reported separately, not only in aggregate

Illustrative example
SliceFailure rateLiftLift vs. thresholdStatus
Storm-driven outfalls9.1%3.6×Review
Pit-dewatering discharges6.9%2.8×Review
Treatment-circuit outfalls4.7%1.9×Watch
Steady-state outfalls2.3%0.9×Normal

Bar: unresolved-item lift vs. the steady-state-outfall baseline · scale 0–4.0× · tick marks the 2.0× review threshold

2 of 4 slices over threshold

Evidence-linked improvement

Nothing closes until a test exists

A cycle closes when the late notification is a regression case. That suite is what the next report certified is measured against.

Improvement cycle · five stages

Switchback — the path turns at Improve and returns at Learn

  1. 01

    Detect

    Late notifications rise on one outfall.

  2. 02

    Diagnose

    The exceedance known on site before the watched clock started is read back until one cause remains.

  3. 03

    Improve

    The fix carries a number, and the outfalls that forced it travel with it.

  4. 04

    Verify

    Nothing goes out until every touched outfall case has passed again.

  5. 05

    Learn

    It is kept permanently, and the limit rules are amended alongside it.

  6. Learn → Detect

    The return edge. Each new cycle opens on a suite that is one case longer.

Typical build scope

Twelve workstreams across six weeks

The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, assembly workflow, evaluation, integration, then production validation and handover.

Workstream

Week 1Week 2Week 3Week 4Week 5Week 6

  1. 01Discharge workflow discovery and boundary definition.Week 1
  2. 02Laboratory and custody source assessment.Week 1, Week 2
  3. 03Permit limit, averaging-basis and clock rule mapping.Week 1, Week 2
  4. 04Sample and result ingestion, normalised.Week 2
  5. 05Outfall comparison and source binding.Week 2, Week 3
  6. 06Confidence scoring and exception routing.Week 3
  7. 07Officer certification workflow.Week 3, Week 4
  8. 08Laboratory and reporting integration.Week 5
  9. 09Limit and exceedance cases.Week 4, Week 5
  10. 10Guardrails and certification controls.Week 4
  11. 11Sample-trail instrumentation.Week 5, Week 6
  12. 12Deployment, documentation and Agent Care handover.Week 6

12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel

Final scope and sequence confirmed in discovery

Engagement tiers

What each tier includes

Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.

Capability✓ in scope · — not at this tierPilotOne outfall, one permitProductionProduction laboratory systemsAdvancedMultiple permits / sites
Introduced at Pilot
Assembly to your permit record✓✓✓
Officer review gate✓✓✓
Chain-of-custody baseline✓✓✓
Introduced at Production
Reporting by outfall—✓✓
Review workflow in your systems—✓✓
Approved write-back—✓✓
Laboratory-system integration—✓✓
Introduced at Advanced
Multi-permit limit rules——✓
Multi-stage officer approvals——✓
High outfall volume——✓
Multi-permit certification controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build price
Confirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
Separate from build
Build pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.

What we need from you

What you bring, and what we build with it

Each input maps to a piece of build scope and a week in the delivery timeline.

  1. 01Your outfall list and monitoring plan structure

    Sample and result ingestion and evidence mapping

    Week 1

  2. 02Representative laboratory deliverables

    Assembly baseline, limit extraction and source binding

    Week 2

  3. 03Your permit limits, clocks and signatory register

    Limit, clock and signatory-rule mapping, and the boundary

    Week 1

  4. 04Access to relevant APIs, feeds or exports

    Laboratory and custody assessment, then integration setup

    Week 2

  5. 05Reports you would not want re-sampled

    Clock cases and the evaluation suite

    Week 4

  6. 06What no certification may cover over

    Confidence scoring, exception routing, guardrails and approval controls

    Week 3

  7. 07Named officers to certify the packs

    Officer certification workflow, then pilot and production validation

    Weeks 5–6

Nothing else is required

Deployment, documentation and Agent Care handover are ours.

Delivery timeline

Four phases across six weeks

Weeks, not slides, set the width of every band on this chart, which is why the fifth carries a pair.

Phase

W1

W2

W3

W4

W5

W6

  1. DiscoveryW1
  2. BuildW2 – W3
  3. EvaluateW4 – W5
  4. Pilot & LaunchW5 – W6

Week focus

W1Discharge workflow discovery, limit mapping and the automation boundary

W2Laboratory integration and the assembly baseline

W3Assembly workflow, confidence logic and certification controls

W4Evaluation suite, guardrails and failure-mode testing

W5Reporting integration, pilot outfalls and targeted corrections

W6One reporting period run under the responsible officer, then Agent Care handover

Reading the band
A bar covers only the weeks its work is named in. The week 5 overlap is two phases at once, not padding.
At the end of W6
The final checks clear on live outfalls and monitoring moves to Agent Care.
Duration
Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.

Next step · Mining AI agent

Build a discharge-certification agent around your permit and your signatory.

Show us your outfalls, your laboratory feed and your permit limits. Who carries the report when it is wrong — the officer whose name is on the certification, which is why the pack is built for that signature.

Typical delivery
4–6 weeks
Deployment
Your outfalls and lab
Officer signs
Pre-signature
After launch
Agent Care available

Nestack Agents · Discharge certification

AGT-MN-12 · Agent Care available after launch

Build a discharge-certification agent

Four questions so the call starts from your actual setup — then pick a time that suits you.

About you
Your outfalls

No obligation. We’ll map the workflow, name the automation boundary and tell you if an agent is the wrong answer.