A field guide to running AI in production: the supply chain as a dependency, quiet failure as the default mode, the verification gate as the method, and cost per correctly solved task as the metric.
Two movements meet: AI is getting production responsibilities, and production data is flowing through AI. Anthropic’s September report, malicious routers, training data provenance and model drift show what to verify before an AI reaches production.
A study of 100 students linked both CS knowledge and writing to vibe coding performance. I unpack the statistics, DHH’s claim and a practical way to test agent workflows.
GPT-6-Astra XHIGH sits alone on the DeepSWE cost-performance frontier, and an older model beats a flagship tier. Follow-up: DeepSeek V4.1 Flash hits 98% of Astra’s score at 1.4% of the cost.
AI products moved from the answer arrives to the answer flows. What streaming inference changes in capacity planning: TTFT, token throughput, concurrent streams.
DHH’s account of AI coding raises a workflow question, not a universal ranking of developers. I separate requirements from implementation preferences and set out a practical review process.
Ox Alpha is a free anonymous-provider preview on OpenRouter. I explain how I would test task quality, agent reliability, cost, privacy, and fallback readiness before production use.
The Bitcoin Red Team campaign after Coldcard exposed a dependency beyond model capability: usable access. Separate self-reported findings from confirmed vulnerabilities, then test safeguards, data controls and fallback workflows.
Knowledge distillation trains a student using a teacher’s examples, output scores or internal features. Compare the access each method needs, then evaluate quality, unwanted behavior, serving performance and full lifecycle cost.
Qwen3 reports a roughly tenfold GPU-hour difference in one post-training comparison. The result explains the value of teacher feedback, not a universal rule for total frontier-model development cost.