The Dashboard Was Reading the Wrong Artifact
Our audit read the source files. The source files were correct. The shipped pages were not — and the gap was 3,226 links wide. What it costs to measure the artifact your users actually receive.
BLOG POSTS
Your Model Vendor Gave You Three Days
A provider announced model decommissioning with three days' notice. Two of our systems depended on those models. Here is what that exposes about the rent-versus-own decision, and the four controls that make a deprecation notice boring.
A Gate That Cannot Go Red Is Decoration
Everyone tests the code. Almost nobody tests the checks that guard it. Here is a pipeline where every one of nine gates is fed a deliberately broken artifact on demand, and any gate that passes is treated as the defect.
Verification That Cannot Fail Is Not Verification
Five failures from one week of AI-assisted engineering, each caught late because a check reported success while measuring the wrong thing.
Adversarial Verification & Fail-Closed Gates: The Mechanics Behind 509 Scheduled, 135 Held, 0 Bad Publishes
The post-mortem on a real production run: 644 items processed, 509 scheduled, 135 quarantined, 13,044 lines of validated data. Plus the 287-line gate-integrity meta-gate that makes those checks un-bypassable.
Green CI, 381 Passing Tests, and a Product That Never Published a Post
A 50-agent adversarial audit confirmed 23 of 25 findings on a codebase whose CI was green and whose tracker said shipped. The two that mattered: content created through the API was never handed to the publisher, and no production code path ever marked a post published. What green signals actually guarantee.