Aquatic Facility Permit & Certification AI Agent

What this agent does

Assembles the file, applies for nothing

A season approaches, and the register names the authority administering that site before any rule is applied.

A permit falls due, and the lead time is counted in that authority's own units, calendar days or business days.

Reason

A safety plan changes, and New York City requires that change approved by the department before it is implemented.

A log is written, and it is checked against that authority's own form and its own retention period.

A monthly submission falls due where the authority requires forwarding rather than retention, as New York City does.

Decide

A certification lapses on the rule's clock, not the card's — a New York reading we mark unsettled until re-verified.

An incident occurs, and each clock runs separately — the notification to the official, then any written report due.

Out

A file is kept with the authority behind each rule, the date it was verified and the operator it was assembled for.

Execute write actions only inside the approval boundaries agreed during implementation.

→ Product statement

The agent assembles the file; a named operator applies for the permit and a health officer approves it, and neither act is the agent's.

Example workflow

One site, register to signature

AgentHuman

1Site enters the registerA club pool, hotel spa, camp waterfront or splash pad at a named address

2Authority identifiedThe county, city or district health authority that administers the site, and the code it applies

3File assembledApplication, safety plan, operating logs, incident clocks and certification currency

4Controls appliedLead-time checks, plan-content completeness, retention tests and a clock per person per credential

No human action required

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

5DecisionBranches at the completeness gate

File complete

Goes to the named operator to sign.

Anything unverified

Adds an aquatics-lead read first.

Operator sign-off

The file is held with its authority, its clocks and what is still open.

Approve · Attach evidence · Send to aquatics lead

Signed — the operator lodges it▼

6Permit record updatedOnly where write access and filing policy allow it

7Outcome evaluatedRegister accuracy, missed clocks, inspection findings and what a later review found

Corrections

Every operator correction is counted in the evaluation.

What should not run autonomously

Human approval stays in control

Outside the boundary — human approval required8 items

Applying for or lodging a permit with any authority.

Approving a permit, a safety plan or a variance.

Certifying or clearing a guard to work a shift.

Deciding to close or reopen the water.

Automation boundaryAgent acts unaided

✓Name the authority administering each site, and the code it applies.

✓Count the lead time in that authority's own units.

✓Test the safety plan against the contents that authority names.

✓Run a clock per person per credential, and hold.

Nothing is lodged here — a named operator applies inside the boundaries set at build.

Signing the application or the safety plan.

The notification call to the permit-issuing official.

Any statement made to an inspector on site.

Changes to an authority rule, form or retention period.

Example output

One site file, annotated

When a file is wrong after the permit issues, the correction is a placard on the door, not a re-filing.

Permit file · single siteIllustrative example

Site

Rule applied

Lead time

Source of record

Confidence

Retention

Club pool, New York City

Safety-plan changes go to the department for approval before use

30 days

NYC Health Code Article 165

Rule verified

On site, and forwarded monthly

As receivedTaken from the authority's own code and form — nothing on this side is inferred by the agent.

What the register holds The administering body The code it applies The date last verified

Why this authorityThe site is in the city, so the state subpart on its own is not the answer for it.

ActionApproveAttach evidenceSend to aquatics lead

What the score decidesBelow the configured threshold the file picks up an aquatics-lead read before.

Value

Where AI adds value

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

Where the value landsValue 01 – 04

Every siteFrom the register

03Assembly

Answers an authority, not a member

Draw on the authority administering the site, the code it applies and the date that code was verified.

01Approved path

The rulebook is the county

A pool in Westchester and one in Manhattan share only the permit lead time — retention and staffing differ.

02Human review

A variance is a decision, not a fact

A district board of health, not a state legislature, revoked a Las Vegas operator's monitoring variance in 2024.

04Build an evidence trail

The clock, the authority that set it and the operator who applied stay on the permit file.

Integrations

Typical integrations

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

Facility and site recordsSite register · floor plans
Drain-cover evidence

Water quality and logsChemical controllers
Daily operation records

Staff and certificationsHR and rostering systems
Training-provider records

Agent

Aquatic permit and certification

Reads the register
Assembles the file
Holds for the operator

Authorities and filingCounty and city portals
Inspection and incident records

Observability & evaluationOpenTelemetry · 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 permit file

Six bands read from the outside in. What survives the innermost is set out in the map below.

L6 · Outermost — last line of defenceInward → L1 · closest to the model

L6Rollback / safe modePull the agent back to register assembly when evaluation or production signals degrade.Roll back

L5Version monitoringTrack model, prompt and authority-rule changes, each with the date it was last verified.Track

L4TraceabilityRecord each rule, the authority behind it, its verified date and every read of the file.Record

L3Operator gateHold the file for a named operator; it governs lodging, not whether the file is complete.Gate

L2Policy guardrailsTest each rule against the authority administering that site; a failure returns the file.Restrict

L1Completeness checksRoute a file carrying an unverified authority rule to an aquatics-lead read first.Require review

Model coreFile assembled — the authority, its rules, the clocks and what is still open

L1 – L2Test whether a file may stand

L3Puts the application in an operator's hands

L4 – L5Keep the clock and the authority behind it

L6Holds the application at unfiled when signals degrade

How Nestack evaluates it

Evaluate the whole operating file — not only the application form.

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

Surface — the file an inspector pulls

Depth of coverage ▼

E1Final-output evaluationDid each rule carry the authority and the date it was verified?

E2Step-level evaluationDid the agent apply the code administering that particular site?

E3Tool evaluationDid it read and write the correct site and the correct credential?

E4Clock calibrationDo unverified authority rules actually attract more operator corrections?

E5Slice evaluationHow does performance change across specific authority types?

E6Business outcomeHow many files needed a correction before the operator signed?

Floor — the outcome the operator answers for

Failure modes

Where each failure originates in the agent

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

Agent lifecycleDirection of processing →

01 · Retrieval1 mode

IB-03

Wrong authority named

The state code is read where a county rule governs.

Stage gathersAuthorities, codes, forms, logs and the clocks

02 · Reasoning2 modes

IB-04

Card clock trusted

A credential is tracked to the date printed on the card.

IB-06

Plan used before approval

A safety-plan change goes live before the department signs it.

Stage proposesThe authority, its rules, the clocks and gaps

03 · Tool / write2 modes

IB-02

Lead time miscounted

Calendar days are counted where the rule says business days.

IB-05

Bundled credential

A multiyear card is entered as one clock, not two.

Stage writesOnly where write access and approval policy allow it

04 · Output1 mode

IB-01

Retention period wrong

Logs are archived before that authority's period ends.

Stage returnsThe file a named operator signs and lodges

05 · Change / Version1 mode

IB-07

Silent register drift

A county amends, and the register still holds the old rule.

Stage tracksModel, prompt, authority rules and their forms

Sev-1 · the agent acts outside the boundary Sev-2 · a wrong rule reaches the permit file Sev-3 · source degrades, file holds open

See the complete Sports & Fitness failure-mode catalogue →

Affected slices

One authority absorbs the corrections

A site-level authority-register figure can read clean while one class of authority absorbs the corrections. Nestack reports the operator-correction rate by authority type, not only in total.

Slice performance — reported separately, not only in aggregateIllustrative example

Slice	Failure rate	Lift	Status
District-board-of-health sites	6.5%	3.6×	Review
City-health-code sites	4.7%	2.6×	Review
County-supplemented sites	3.2%	1.8×	Watch
Single-code state sites	2.0%	1.1×	Normal

Bar: operator-correction-rate lift vs. single-code-site baseline · scale 0–4.0× · tick marks the 2.0× review threshold 2 of 4 slices over threshold

Evidence-linked improvement

No cycle ends until the rule is retested

A cycle closes when the lapsed certification is a regression case. That suite is what the next season opened is measured against.

Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn

01Detect

Operator-correction rate rises at one authority.

02Diagnose

The guard whose card said two years and whose state said one is traced back to one cause.

03Improve

The change carries a number, and the sites behind it are filed beneath it.

04Verify

Nothing files while one touched site case is still red.

05Learn

It is kept for good, and the authority rules are amended in the same commit.

Learn → DetectThe return edge. The next season opens against a suite 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, file assembly, evaluation, integration, then production validation and handover.

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

01Permit workflow discovery and boundary definition.

02Roster and log source assessment.

03Authority-register and retention-schedule mapping.

04Log and roster ingestion and normalisation.

05Assembly logic and authority binding.

06Clock tracking and review routing.

07Operator sign-off workflow.

08Roster and log-system integration.

09Currency and lead-time cases.

10Guardrails and application controls.

11Permit-trail instrumentation.

12Deployment, documentation and Agent Care handover.

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 tier PilotOne site, one authority ProductionProduction roster and log systems AdvancedMultiple authorities / estates

Introduced at Pilot

Assembly to your authority rules✓✓✓

Operator gating✓✓✓

Authority-register baseline✓✓✓

Introduced at Production

Reporting by site—✓✓

Review workflow in your systems—✓✓

Approved write-back—✓✓

Roster-and-log integration—✓✓

Introduced at Advanced

Complex multi-venue estates——✓

Multi-stage operator approvals——✓

High site count——✓

Multi-authority permit controls——✓

Build price From $5,000 From $8,000 Custom quote

Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.

Separate from buildBuild 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.

You bringWe build with it

01Your sites and the authority for each → Register build and rule source mappingWeek 1

02Representative files behind past permits → Assembly baseline, rule extraction and authority bindingWeek 2

03Your safety plans, logs and certification roster → Authority register, rule and retention mapping, and the boundaryWeek 1

04Access to relevant APIs, feeds or exports → Roster, log and controller assessment, then integration setupWeek 2

05Logs you would not want inspected → Expiry cases and failure-mode testingWeek 4

06What no permit file may omit → Clock tracking, review routing, guardrails and gating controlsWeek 3

07Named operators to sign the application → Operator sign-off workflow, then pilot and production validationWeeks 5–6

Nothing else is required Deployment, documentation and Agent Care handover are ours.

Delivery timeline

Four phases across six weeks

Every width comes from the weeks that phase truly needs, which is why the fifth carries a pair.

Phase W1W2W3W4W5W6

Discovery W1

Build W2 – W3

Evaluate W4 – W5

Pilot & Launch W5 – W6

Week focus W1Permit discovery, authority mapping and the automation boundary W2Source integration and the assembly baseline W3Assembly workflow, clock logic and completeness controls W4Evaluation suite, retention cases and failure-mode testing W5Roster and log integration, pilot sites and targeted corrections W6One pool season run under the named operator, then Agent Care handover

Reading the bandA bar sits on the weeks its work is named in and no others. The fifth week really does carry two phases.

At the end of W6Validation closes on live sites, and Agent Care picks up monitoring.

DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.

Next step · Sports & Fitness agent

Build a permit agent around the authority that administers each site.

Show us where your water is and who signs for it. The next step is a register — one row per site, the authority that administers it, the code it applies and the date we last verified it, with the clocks that fall out of it.

Discuss this agent →

Nestack Agents · Aquatic permitsAGT-SF-20 · Agent Care available after launch