Engineering notes
A dated record of engineering decisions behind the systems this practice runs: what changed in the field, what was tested and under what conditions, what was adopted, what was rejected, and the limits of each result. Three notes so far, two about things that were wrong before they were right and one evaluating a published finding on agent permissions, and a methods table that says plainly which capabilities are in use, which are tested on synthetic data only, and which are still a question.
Read the engineering notes →
My own infrastructure
The seven scheduled jobs that run this business unattended, what verified means here and why a job's own report never counts, the record as of September 7, 2026, the two production drift episodes and the failed-check hours written up with their causes, what the record does not prove, and the seven rules that decide what goes on the public card.
Read the operating record →
Cost guide
Other firms' and guides' published prices for assessments, strategy, builds, retainers and hourly work, each checked at its source, in one table next to my own prices. Then the six questions to ask any consultant before paying.
Read the cost guide →
For quality and compliance managers at suppliers
What Section 3 holds and the six ways it varies, where scanned sheets misread, the five checks that catch a wrong value before it enters a disclosure, what a measured run on 22 synthetic sheets found, and a vendor-neutral acceptance checklist for any SDS reader.
Read the safety data sheet guide →
For fabricators and service centers
The eight blocks on a cert, a five-minute receiving check, ten tells a steel person catches on sight, the heat-analysis limits for A36, A572 Grade 50 and A992 as a recorded gate enforces them, where OCR and AI misread faxed and photocopied certs, and a printable checklist.
Read the mill cert guide →
For oilfield service companies
What has to be true before a ticket bills, the seven places money leaks between the field and the portal, why operators' portals reject, what a recorded agent fleet caught and refused, the three checks that need no AI, and the honest labor arithmetic.
Read the field ticket guide →
Reference data, CC BY 4.0
Twenty-six documented incidents, each verified against a primary source and published with its own page: who was involved, when, what class of failure, who discovered it, whether the company running the AI caught it, and the control that was missing. Also as JSON and CSV, versioned and mirrored.
Read the receipts →
Reference data
The stories that arrived for checking and were not there: what was searched, what was found, and the real incident each one usually stands in for, with corrections dated on the record.
Read the refuted claims →
Method
The same discipline pointed at AI research itself: the claims research tools produced about the industries I work in, and how each one died at the primary source.
Read the verification log →
The standing rule for everything on this page: no number without a denominator, no source below a regulator's release, a court record, a company's own statement or a named newsroom, and every correction dated where the reader can see it.