Signal

The template detail: Hy4's published chat_template.jinja permits exactly two reasoning_effort values — high (the default) and no_think — a coarse binary switch rather than the graded low/medium/high/xhigh scale this month's other releases expose. It's also a big jump in scale from Hy3 (295B total, 21B active, 256K context, 598GB on Hugging Face, released just last month) to Hy4's 770B total, 49B active, 1M context, 1.56TB.

The demo: run at default high effort via OpenRouter, Willison's go-to test prompt produced a reasoning trace second-guessing itself over a pelican illustration: “Maybe add a small cycling cap or helmet? The user didn't ask; can add red helmet? Might be cute. But pelican with big beak; a helmet might obscure. Better maybe no.” His read: the hidden chain-of-thought skips correct grammar because perfect English isn't token-efficient for reasoning nobody's meant to read directly.

One blog post, one prompt, no benchmark suite — this is a mechanics-and-vibes look at Hy4's reasoning template, not an assessment of its actual capability; that still rests on Tencent's own blind internal eval from this morning's edition.

What actually changed: comparing an old snapshot against the current Q4_K_M, the poster found the raw tensor bytes differ throughout (a different importance matrix/calibration), machine-path metadata changed, the old version/finetune fields were dropped, and size_label was corrected from “256x2.6B” to “35B” with license/tags/basename added. Everything structural is unchanged — same qwen35moe architecture, 248k tokenizer, file type, expert count, context length — so it's the same model family, re-quantized against a different calibration checkpoint and relabeled, with a file-size shift of only a couple hundred bytes, which is why nobody noticed for days.

Why it lands on this edition's ledger: a second, independent, concrete case for the “GGUF filenames don't reliably describe what's actually shipped” thread already flagged after the 64-of-443 mislabelling audit — except here the label arguably got more honest even as the underlying weights silently changed beneath it. The open question the poster raises and can't answer alone: is the new calibration actually better, or just tidier?

Single user's byte-level diff against their own backup, verified only against the official repo, not third-party mirrors; no quality re-benchmark yet comparing old vs. new calibration.

The Finland-based Centre for Research on Energy and Clean Air (CREA) puts the added cost of the war to global energy importers at up to $330 billion over six months, measured against what analysts had forecast before the conflict — despite both oil and gas prices rising by less than initially feared. CREA's own framing: the bill isn't finished, since the war hasn't ended and further disruption could add to the total. Only the lede of this report made it into today's capture; the full country/fuel breakdown and CREA's methodology weren't retrieved.

Why it's here: the clearest case this edition has today of war and energy touching directly rather than needing an AI hook to justify inclusion — a reminder that the same geopolitics reshaping chip export controls is also quietly repricing the fuel bill for every economy this edition's data-centre and grid stories assume will keep the lights on.

Single outlet relaying a single think tank's modelled estimate against a forecast baseline, not measured against realised prices; no other outlet's corroboration captured, and the underlying CREA report wasn't retrieved in full.

The actual text: Debian's resolution states the project “neither endorses nor prohibits the use of generative AI tools in the development, maintenance, or documentation of software, packaging, documentation, and other media published within the Debian Project,” recognising such tools “can substantially improve the productivity of contributors when used responsibly.” The operative clause is the second half: “the use of a generative AI tool does not diminish the contributor's responsibility for the work they submit” — contributors are expected to “understand, review, test, and, where appropriate, modify AI-assisted output before incorporating it into Debian.”

Why it's worth a line, not a headline: it's a governance vote, not a technical development — but it lands the same week this edition is also tracking maintainers drowning in AI-generated slop PRs filed purely to farm contributor badges (still on yesterday's ledger). Debian's approach is the opposite of a ban: rather than policing the tool, it makes the human accountable for the output, which is a cleaner answer to the slop problem than most projects have managed so far.

A project policy vote, not an enforcement mechanism — nothing here says how “responsibility” gets checked in practice.

A poster weighing a 2×96GB M5 Ultra cluster against a single 256GB M5 Ultra says most people, including advisors in a parallel r/LocalLLM thread, recommended the single machine — the usual reasoning being that Thunderbolt 5's interconnect bandwidth caps out clustering's benefit. Exo's own claims complicate that advice: linear bandwidth scaling across clustered units via their RDMA solution, which would undercut the standard single-box recommendation if it holds. But in the same breath, an Exo employee posting on r/LocalLLM reportedly argued that for their clustering approach specifically, latency — not bandwidth — is the real bottleneck, which the poster says most people (himself included) weren't factoring in when giving that single-box advice.

Why it's a weak signal, not a story yet: a vendor claim, an internal-seeming contradiction about which metric even matters, and a buyer who says he's sticking with the conventional single-box order anyway despite hearing the pitch. Nobody's independently benchmarked either the linear-scaling claim or the latency-over-bandwidth argument.

Single Reddit thread relaying a vendor's own claims about its own product, including a seller employee's competing framing of what matters — no independent benchmark exists yet.

What leaked: per TestingCatalog, Astra outputs generated zero-shot at “Max” reasoning effort reportedly produced a GTA 2-style game in one attempt, plus detailed websites, 3D objects and voxel environments — the difference from prior releases described as attention to implementation detail and how much complete functionality comes out of a single prompt. GPT-6 remains a plausible eventual public name; OpenAI hasn't confirmed either that or the “mozaik-alpha-fdm” codename.

The part that matters more than the demo: OpenAI has already acknowledged Astra by name and said its internal evaluations showed major advances in agentic coding and cybersecurity capability — potentially crossing its own “Critical” cyber-capability threshold. Some Astra workloads were reportedly paused to add stricter safeguards, and OpenAI says government agencies and selected AI-safety organisations are now part of the actual testing process, not just post-hoc reviewers. That makes government evaluation a formal deployment gate rather than a talking point — read next to this edition's ongoing coverage of Anthropic's court fight with the Pentagon (still on the ledger below), it's a second, very different data point on how government and frontier labs are entangling themselves with each other right now.

Single-outlet leak sourced to a Discord server, not OpenAI directly; no release date, and OpenAI has confirmed neither the “mozaik-alpha-fdm” codename nor a GPT-6 name.

The official launch: Tencent calls Hy4 preview its most capable model yet and its largest generation-over-generation gain measured, aimed at long-horizon software engineering, office work, game prototyping and research. A blind internal comparison — 163 Tencent experts rating outputs across 203 engineering tasks — scored it 2.99 average against GLM-5.3's 2.92 and Kimi K3's 2.94, with 46.8% outright wins over GLM-5.3 and 51.2% over Kimi K3. In one internal test it ran several Codex sessions in parallel, changing research direction as results came in, and reportedly beat Codex working alone on all eight benchmarks in a small-model post-training task. Pricing: $0.042/$0.834/$2.501 per million tokens for cached input, input and output respectively. Tencent's own caveat: it can over-reason and over-verify on complex tasks.

The compression, days later: a since-unelaborated r/LocalLLaMA post claims the 1.5TB model has been compressed to roughly 200GB in GGUF form while retaining about 98% of performance — no methodology given in what's been captured here, but if it holds, it's a dramatic footprint reduction for a 770B model.

Then an official 1-bit quant: a separate thread reports Tencent itself shipped a low-bit quant (actually 2.38 bits per weight once corrected from an initial “Q1” label) with barely-moved benchmark scores versus BF16: MCP Atlas 83.7→83.2, SWE-Bench multi 82.9→81.3, MRCR 81.3→81.1, IFBench 73.5→72.5. That's a strikingly small accuracy hit for a sub-2.5-bit quant, if the numbers are Tencent's own and not community-remeasured.

Why it's a feature, not a footnote: this is the same “fast follow” economics that's run through this edition's open-weight coverage all month — a frontier-scale release, then an aggressive compression pass, then an official ultra-low-bit variant, compressed into about a week rather than the usual quarters-long cadence.

The official launch numbers are Tencent's own blind internal eval; the 200GB compression claim and the 1-bit quant's benchmark deltas are both community-relayed and not independently re-measured here.

A poster flags Terminal-Bench 4.0's own framing as the most interesting part of the announcement: its maintainers are explicit about iterating the benchmark quickly to stay ahead of the pace of new model releases, rather than letting a fixed test set get gamed and saturated the way older coding benchmarks have. Against that new version, the poster reads GLM-5.3 as landing at the same level as Fable 5 “accounting for margin of error” — a striking claim, if it holds, for an open-weight model against Anthropic's top tier. The same thread separately asks the field's now-standard follow-up question: what cheaper, smaller benchmarks exist for evaluating one's own coding harness, since benchmarks at this scale can cost 5–10 billion tokens to run — not something most individual developers or small teams can absorb.

A single community poster's read of a fresh leaderboard, not an official head-to-head comparison published by Terminal-Bench's maintainers; treat the GLM-5.3/Fable-5 parity claim as unverified until a primary-source table is captured.

What's alleged: the publishers accuse Anthropic of a “brazen campaign of illegally torrenting, scraping, and downloading copyrighted works” to train Claude, seeking up to $150,000 per work plus up to $25,000 for each instance where identifiable copyright data was stripped — across “tens of thousands” of works, which The Verge notes could total several billion dollars if a court awards the maximum. The complaint names co-founders Dario Amodei and Benjamin Mann as individual defendants, alleging Mann personally used BitTorrent to download over five million pirated books and that employees downloaded at least two million more from Pirate Library Mirror; it also alleges Anthropic scraped lyrics from licensed sites MusixMatch and LyricFind. Named songs include Marvin Gaye and Tammi Terrell's “Ain't No Mountain High Enough,” Bon Jovi's “Livin' On a Prayer” and Leonard Cohen's “Hallelujah.”

Why this one's different from the pile already on the ledger: Anthropic already faces suits from Universal Music Group, Concord, ABKCO, BMG and Round Hill Music, and was ordered to pay $1.5 billion in the landmark Bartz v. Anthropic case after a judge found training on copyrighted books legal in principle but acquiring them via piracy was not. This filing explicitly builds on that precedent and widens it — adding the “flagrant piracy” framing to music lyrics and sheet music specifically, and putting two named individuals, not just the company, on the hook.

Read against this edition's Pattern: courts, not legislators, are still doing the actual work of defining what training-data acquisition is permissible — and the price of getting it wrong keeps climbing with each new plaintiff who can point to Bartz as the template.

These are allegations in a filed complaint, not proven facts; Anthropic had not responded to either outlet's request for comment before publication.

The tyres: Tesla's updated tyre spec on the Model 3 adds roughly 38km of range and improves efficiency without any change to battery capacity — pushing total range past 570km. It's a reminder of how much of an EV's real-world range is determined by rolling resistance and drivetrain tuning rather than battery chemistry alone, and a cheap lever automakers can keep pulling between actual battery generations.

The FSD rollout: Tesla has provided an update on bringing “FSD Lite” to older-hardware Model 3 and Model Y vehicles in Australia and New Zealand — markets that have typically waited well behind the US for full self-driving features, and that have historically had older in-fleet hardware generations than the US mix.

Why both belong in this lane: incremental efficiency gains and broader FSD availability are both small, steady additions to the same electricity load and driving-behaviour base that AU's data-centre and grid stories track from the other side — sustained EV demand growth is one more call on the grid this edition follows daily, alongside the Rinehart mine story and the biggest-dealer “EV buyers don't go back to ICE” claim carried on yesterday's ledger.

Single outlet for both items; no independent range test of the tyre claim, and no rollout timeline given for FSD Lite beyond “update provided.”

What just happened elsewhere: the UK began selling plug-in solar (“balcony solar”) on Thursday, with single panels from £599 (or ~£24/month via buy-now-pay-later) through retailer Argos, following Germany and Spain. New Zealand's government has separately signalled it could legalise plug-in solar within nine to twelve months, potentially beating Australia to it.

The actual technical ask: Smart Energy Lab's Glenn Morris says the fix doesn't need new technology, just a product standard: an inverter that shuts down instantly when unplugged, an ~800W cap so it can't overload a standard circuit, and simple network registration. Germany has run over a million such systems for years without inventing anything new. Solar Citizens estimates an 800W system in most of Australia would generate ~1,000kWh/year, worth $300–400/year off a power bill, paying for a ~$1,000 kit within three years and continuing to work for twenty.

Why it's a weak signal rather than a story: this is advocacy pressure, not a policy announcement — Solar Citizens has written to Australian governments but no regulator has responded on the record yet. It's a small, steady thread in the same rooftop-electrification story as home batteries and EVs, sitting one level down from the federal data-centre energy fights this edition tracks daily.

Sourced entirely to advocacy groups (Solar Citizens, Smart Energy Lab) with a direct stake in the outcome; no government or regulator response captured yet.