byASB Ankiit Singh Book a scoping week
Writing · field teardowns

What broke,
and why.

Teardowns of real systems that failed in the field — the symptom, the actual cause, and the fix. Written from engagements, with the numbers intact.

Most debugging writing stops at the symptom. These go to the decision that produced it — usually something that looked reasonable when it was written.

Teardowns

3 posts
AI agents I let an agent do the last mile of an App Store release A build appearing in App Store Connect wakes seven agents on Google ADK that take it to Waiting for Review unattended. What the first real run caught — including a rejection no API field exposes. 2026 Regulated software Certification is not a phase at the end A UAE telehealth platform built from zero, taken through full health-authority approval, launched and handed over — and why approval is a constraint on your data model, not a block on your plan. 2026 Computer vision The model scored a hand 0.303 and a bolt 0.921 An EV charging pad's foreign-object detector was failing in both directions at once. Why lowering the threshold would have made it worse, and the two-tier detector that replaced it. 2026

More teardowns are being written up from the work in the project archive — regulated healthcare approval, state-scale video architecture, and hardware faults caught on paper before the bench.