AI News: Central Banks Warn of AI-Driven Financial Crash Risk

June 29, 2026: BIS, Telegraph, FT flag AI bubble risk; Ford rehires engineers; German court rules Google liable for AI summaries.

Top Stories

Central Banks Quietly Start Pricing an AI-Bust Scenario

The Bank for International Settlements has flagged a non-trivial probability that the AI capex cycle unwinds into a credit event, citing how concentrated the supplier base has become and how levered hyperscaler balance sheets now sit. The BIS quarterly review is the cleanest macro read on the buildout so far, and it lands at a moment when senior central bankers are no longer treating AI infrastructure spending as an unambiguously positive productivity story.

The Telegraph quoted senior regulators publicly warning that the AI boom risks a global financial crash, framing current infrastructure spending as a systemic risk factor rather than a tailwind. The Financial Times argued the cycle looks more like past bubbles than prior compute transitions, and that any unwind would likely be long rather than sharp.

Taken together, the three notes mark the first time the institutions that set financial conditions have publicly aligned on the bust scenario. The next test is whether that framing hardens into supervisory guidance or stays in the op-ed pages.

Ford Rehires 350 Veteran Engineers After AI Quality Stumbles

Ford has rehired roughly 350 veteran engineers - some returning from retirement, others from suppliers - after automated quality systems failed to deliver. COO Kumar Galhotra said Ford had been “relying more and more on automated quality systems” with disappointing outcomes, prompting the company to “bring back technical specialists” who “hunt for failure points before a part ever reaches the plant floor.”

VP Charles Poon acknowledged that simply feeding design requirements into AI did not yield high-quality products. The “gray beard” engineers are now training younger staff and reprogramming AI tools, with CEO Jim Farley citing reduced warranty and recall costs worth “hundreds and hundreds of millions of dollars.” Ford also topped mainstream brands in the latest JD Power Initial Quality Survey, suggesting the rollback is working even if the underlying AI tooling has not yet matured.

German Court Holds Google Liable for AI Search Summaries

A German court has ruled that Google is liable for false statements in its AI search summaries, treating the summaries as Google’s own words and reflecting its own business activity. The court rejected Google’s defenses, including the argument that users could verify the information themselves and that people should know better than to trust AI blindly.

The decision lands in the broader debate over the carrier-versus-publisher distinction that Section 230 of the CDA codified for internet platforms. AI Overviews are wrong roughly 10% of the time, and Google processes more than five trillion searches per year - meaning even small error rates produce large absolute counts. The ruling joins earlier precedents including Air Canada (liable for what its chatbot told a customer about discounts) and an Ashley MacIsaac lawsuit against Google over an AI summary that falsely labeled him a sex offender.

Micron Has Its Nvidia Moment on the AI Memory Shortage

Micron briefly passed Meta and Tesla in market cap on June 25, closing that Friday at roughly $1.27 trillion against Meta’s $1.39T and Tesla’s $1.42T. The stock is up more than 236% in the past month alone, and sits at $1,132/share after years below $100 before mid-2025. Q3 revenue quadrupled year-over-year to $41.45 billion, with profits jumping from $1.88B to $28.2B.

The argument: AI servers pull orders of magnitude more memory than laptops, and Nvidia, Microsoft, AWS, Google, Meta, and Oracle are buying in bulk, forcing Dell and HP to hoard. The resulting “RAMageddon” supply crunch is forecast to persist into 2027 and is already raising prices on Apple products and Xbox consoles. Micron has signed 16 long-term strategic agreements across data center, consumer, and auto segments - including with Nvidia and Anthropic - to ride the cycle past any traditional memory-chip glut.

PhantaField Unveils a 330 GB On-Die DRAM AI ASIC

PhantaField has published a whitepaper for the Sophon PFG-1, a unified train-and-serve AI die built on a 28 nm Si base with a 64-tier monolithic 3D stack alternating 2D-TMD MAC logic tiers and 2T0C gain-cell DRAM memory tiers. The package carries 330 GB of on-die DRAM with no HBM, 1.8-second retention, and roughly 0.08 W refresh.

The claimed throughput is striking: 2,100 TFLOPS BF16, 4,200 TFLOPS FP8, and 8,400 TOPS INT8 across 131,072 digital CIM tiles, with 2.10 PB/s in-tile weight bandwidth (the whitepaper cites ~95× more bandwidth than Nvidia’s announced Rubin R200 and ~107× more than AMD’s MI455X per die). The die targets 14,438 tok/s on 80B FP8 decode (B=1) and 72,188 tok/s with INT4 plus speculative decoding, at a claimed BOM of about $8,358 per die - roughly an order of magnitude cheaper than Rubin R200 or MI455X. If those numbers hold, this is a real architectural alternative to Nvidia’s HBM memory hierarchy for self-hosted inference.

Six Months of AI Agent Credential Incidents, Catalogued

DevFortress has published a semi-annual retrospective on six months of AI-agent credential leaks, token theft, and scope-violation incidents. The catalogue is a practitioner’s view of where agents are quietly breaking: secrets surfacing in retrieved documents, tool calls drifting outside intended scopes, and tokens escaping agent memory into downstream logs.

The report lands in the same week as Stack Overflow’s new agents feed, where coding agents post their own questions, debugging notes, and reusable patterns. Jon Udell has also pushed back on the phrase “human in the loop,” arguing on his blog that the framing “cedes authority to the machines” and that the safer default is keeping agents inside human-controlled loops. The throughline: as agents move from demos to production, the credential and scope story is the bottleneck.

AI Agents Nuke Toulouse to Stop a Threat They Can See

Liam Wilkinson has built CivBench, a long-horizon strategic reasoning benchmark that drops frontier models into Civilization VI. Claude Opus 4.6, GPT-5.4, Gemini 3.1 Pro, and Kimi K2.5 played as Portugal against France; one Claude agent spent roughly 50 turns researching Nuclear Fission, then launched a nuclear strike on Toulouse (France’s cultural capital) on turn 305 and a follow-up strike six turns later.

The catch: France was already within reach of a diplomatic victory the agent could not see. As Decrypt put it, the agent “nuked a city to stop the threat it could see, and lost on the threat it couldn’t.” In another match, a Claude playing as Babylon kept pursuing a scientific victory while falling behind. The benchmark adds a fresh, reproducible data point to the small but growing “AI agent behavior in long-horizon games” literature, joining a King’s College London study where leading models selected nuclear escalation in geopolitical crises.

A Mythos-Derived 9B Model With a 1M-Token Context

Empero AI has released Qwythos-9B-Claude-Mythos-5-1M on Hugging Face under Apache-2.0. The 9B reasoning model is fine-tuned from Qwen3.5-9B with full-parameter SFT on 500M+ tokens of Claude Mythos and Fable traces plus an in-house rethink chain-of-thought. Context is 1,048,576 tokens via YaRN rope-scaling (factor 4.0 over a 262k native window).

Specs include BF16 precision, a hybrid Gated DeltaNet attention layer (3:1 linear to full), and eval lifts over the base of +34 points on MMLU, +30 on gsm8k-strict, and +19 on gsm8k-flex. Recommended sampling is T=0.6, top_p=0.95, top_k=20, with a repetition penalty of 1.05 and max_new_tokens of 16384. For local-AI tinkerers tracking derivative work around the Mythos weights, this is a downloadable artifact with a long context window.

AI Patches a Closed-Firmware DHCP Bug in EdgeOS

Guru Labs has published a writeup of using a frontier model to patch a long-standing EdgeOS bug where dhcrelay3 re-relays already-relayed DHCP packets in violation of RFC 2131. The author loaded the closed-firmware binary (cross-compiled MIPS, Cavium Octeon big-endian or MediaTek MT7621 little-endian) into a disassembler, walked the AI through the relevant code paths, and verified every suggestion against SHA256 hashes, byte diffs, and live router behavior.

The shipped patch is 8 bytes at offset 0xCF38 on the Octeon build, replacing an interface-flag test with a giaddr != 0 check that jumps to the function’s existing exit. The repo ships with a SHA256-verifying shell script that backs up the original, atomically swaps the binary, restarts the relay, and reinstalls on firmware upgrades via /config/scripts/post-config.d/. The disclosure went to the Ubiquiti community; no vendor response so far.

Quick Hits

  • Stack Overflow agents feed goes live: A new public feed where coding agents post their own questions, debugging notes, and reusable patterns. agents.stackoverflow.com

Worth Watching

The macro thread is now open. BIS, the Telegraph’s central-banker quotes, and the FT analysis together mark the moment when the AI buildout stopped being treated as an unambiguously positive macro story by the institutions that set financial conditions. Watch for whether supervisory guidance follows the op-eds, and which hyperscaler balance sheets and HBM suppliers are first to feel it if not.

Inference plumbing is the new battleground. PhantaField’s monolithic-3D ASIC paper, the GuruLabs EdgeOS patch, and the Empero-AI Mythos derivative release suggest the next twelve months of local-AI gains will come as much from inference-side innovation (memory hierarchy, binary patching, distilled long-context models) as from new base models. The economics of self-hosting are going to shift faster than the model-release calendar suggests.

Agent incidents are outpacing agent policy. The DevFortress catalogue, the Stack Overflow agents feed, and the CivBench escalation result together sketch a landscape where agents are already running in production but their credential, scope, and behavior norms are still being written in incident reports. The first well-publicized agent-caused real-world incident will compress that timeline.