EquipCert AI
Web and mobile inspection evidence with offline capture and explicit certification boundaries.

Deployed inspection app · operational probes verified
Independent build
My web/mobile equipment-inspection product. Operational probes and tests have dated evidence; regulatory certification is not claimed.
THE ENGINEERING
An equipment-inspection application with Next.js, Flutter, Supabase records, offline evidence capture, signatures, optional AI assistance and PDF reporting. October 14 verification recorded 104 web unit tests, seven production probes, three dependency checks and zero configuration-boundary violations across 157 files. The database keepalive now requires an actual database query. The 429 native-client tests and mobile build results remain dated October 1 evidence. Authenticated inspection walkthroughs, persisted signature-consent evidence, commercial payments, an off-machine signing-key backup and a completed restore drill remain open; inspection evidence is not regulatory certification.
BEFORE → AFTER
Real problems from this build, what I changed and the verified result.
- CASE 01Before
The audit table existed but nothing wrote to it, application users could insert rows, and its append-only guard would have crashed GDPR erasure the moment it filled up.
AfterDatabase suite went from 8 failing to 28 of 28 passing, erasure included.
How I fixed itMoved audit writing into database triggers on the core tables, blocked application writes, and defined the one permitted erasure mutation.
- CASE 02Before
The live database went offline: the free hosting tier paused it after a week without activity, even though a keep-alive job reported success twice a week.
AfterOctober 14 verification passed seven production probes, three dependency checks and 104 web unit tests. Authenticated inspection and a complete restore drill remain separate gates.
How I fixed itFound that the keep-alive called a health endpoint that never touched the database. It now runs a real query every day and reports success only when a row comes back.
- CASE 03Before
On the serverless host, the subscription webhook would have rejected every genuine payment event: the platform parsed the body first, but the provider signs the exact original bytes.
AfterWith provider-signed test payloads, the old handler fails the platform-replay and raw-stream cases and the new one passes all of them; serverless behavior was checked against the platform runtime's source.
How I fixed itMade the handler read the exact bytes on both deployment targets, and stopped logging event contents that can include customer details.
Evidence reviewed: Source review October 14, 2026; verification dates and open gates stated above