SHA-256 chain
Hedera anchor · daily
0.0.4812741@1744934401.000
Merkle root: 9f3a…7c44
Verify this anchor →
One entry. Two jobs.

Proof for regulators.
AI for operators.

Every log entry is sealed to a public blockchain — so regulators can verify integrity themselves. The same entry grounds an AI that reads your plant's history, lab results, and permit.

#4,217 2026-04-17 · 06:14 M. Webb · Shift start
DO in aeration basin 2 reading 4.8 mg/L at start of shift. Blower 3 at 62% after overnight adjustment. TSS effluent 14 mg/L — within permit limit of 30.
hash: 7b2d…f891 anchored
AI shift briefing · 06:00
Quiet night. One thing to know.

Blower 3 ran at 62% overnight — DO held above 4.5 in basin 2 throughout. TSS effluent 12–14 mg/L, well inside the 30 mg/L permit limit. No amendments. Check solids inventory before the 10:00 sample round.

Ask your plant
When did TSS last run above 20 mg/L?
Entry #4,203 on 2026-04-11 at 08:22 — TSS 22 mg/L, noted as "post-storm, settled by 14:00." Three entries cite that storm event.
The problem

Compliance software that's defensible
is rarely useful.
Tools that help operators
rarely hold up under audit.

Current tools
Paper logbook Defensible Not queryable
Excel / shared drive No integrity proof No AI
eLogger / Klir Trust-based trail No plant-context AI
Pick one: records a regulator trusts, or tools an operator uses.
CertaQ
Sealed to a public blockchain — independently verifiable
Plant-context AI grounded in this plant's entries, lab results, and permit
Same entries power both — no trade-off, no duplication
Same entry. Cryptographic receipt for regulators. AI context for operators.
01 — Log

Log the way you already do.

Type an observation. Snap a photo — the AI extracts the reading and fills in the entry. Record a lab result. Every input lands in the same logbook with the same integrity guarantee.

2026-04-17 · 06:14
DO in aeration basin 2 reading 4.8 mg/L at start of shift. Blower 3 at 62% after overnight adjustment.
02 — Chain

Every entry becomes a receipt.

SHA-256 hashes the entry against the previous hash, the sequence number, operator ID, and timestamp. A daily Merkle root anchors to Hedera. No UPDATE or DELETE — corrections are amendments that appear in the chain alongside the original.

prev_hasha3f8…c12e
plant_idIL-POTW-0412
seq4217
operator_idop-mwebb
timestamp2026-04-17T06:14:22Z
SHA-256 ↓
entry_hash7b2d…f891
Hedera: 0.0.4812741@1744934401anchored 00:00 UTC
03 — Two answers. One entry.

The regulator checks the math.
The operator asks a question.

A regulator rebuilds your chain from the Hedera transaction — without calling you or us. An operator asks the AI and gets an answer grounded in this plant's actual history and permit limits, with entry citations.

Regulator
Verify chain →
✓ 4,217 entries. Chain intact. Last anchor 2026-04-17T00:00Z. Hedera txn 0.0.4812741.
same entry
Operator
When did TSS last exceed 20?
Entry #4,203 on April 11 — TSS 22 mg/L, attributed to storm runoff. Three entries cite that event.
The AI layer

The log is the AI's memory.
Your plant's history. Not generic best practices.

Every question is answered against this plant's actual entry history, lab results, permit limits, and compliance schedule. The more your team logs, the more specific the answers get.

Shift briefing

Incoming operator gets a plain-English summary of the previous shift: what happened, what to watch, any amendments — in the tone of a handoff note.

"Quiet night. Blower 3 at 62%, DO held. Check solids before 10:00 round."

Photo to log entry

Photograph a gauge, lab card, or bioreactor surface. The AI extracts the observation and proposes a structured entry. Operator confirms it.

Photo → "DO 4.8 mg/L, basin 2, visual: normal foam line" → entry proposed

Permit parser

Upload the NPDES permit PDF. Parameters, limits, sampling frequencies, and compliance deadlines extracted in minutes.

TSS limit: 30 mg/L (daily max) · BOD: 25 mg/L · sampling: 3×/week

Tribal knowledge retained

New operators ask the log what a veteran would know. The answer is in the chain, with the entry number it came from.

"Entry #3,847 — last time BOD spiked pre-holiday, operator reduced loading 15% at 06:00."
Verifiable proof

Don't take our word for it.
Check the math yourself.

A live sample chain anchored to Hedera. The verify button fetches the anchor transaction from the Hedera mirror node directly — we're not in the loop.

IL-POTW-0412 · Springfield Water Reclamation 4,217 entries
#4,217 2026-04-17 06:14 7b2d…f891 verified
#4,216 2026-04-17 05:58 a3f8…c12e verified
#4,215 2026-04-17 05:31 c91e…8d44 verified
#4,214a 2026-04-17 05:30 f02b…1c77 amendment
Hedera anchor — 2026-04-17 00:00 UTC
0.0.4812741@1744934401.000
Merkle root: 9f3ac7e2…7c44b81a

This calls the Hedera mirror API directly. We are not in the loop.

One logbook.
Records your regulator can verify.
Answers your operators can use.

Upload your NPDES permit PDF. We extract parameters, limits, and your compliance schedule. Your team starts logging the same day.

No contract. Class I–IV plants.