What You Need to Know: Anthropic opened a research preview of its Model Hardware Standard (MHS) today, inviting partners in science, robotics, and manufacturing to help extend Claude Code's hardware reach. Google released Gemini 3.5 Transcribe with separate streaming and batch endpoints reporting 4.0% and 2.6% word error rates. A community developer reverse-engineered an Axera NPU engine format to run GGUF models directly at 1.5× the vendor runtime speed on Raspberry Pi hardware.

Top Story

Anthropic launched a research preview of the Model Hardware Standard (MHS), a collaboration that began with the Howard Hughes Medical Institute and now invites stakeholders across science, robotics, electronics, and manufacturing. The standard currently covers lab and manufacturing equipment best; the preview aims to extend it to boards, cameras, and other devices already driven by Claude Code so everything works through one interface. Anthropic notes that LLMs still lack physical intuition because they learned the physical world only from text and images, so the preview will also produce more safety evaluations before any open-source release. Builders working on physical-world agents should watch the preview for early access and feedback channels. The effort directly addresses the gap between text-only agents and real hardware control. Source: anthropic.com

Model Updates

Gemini 3.5 Transcribe: Google AI Google released Gemini 3.5 Transcribe as two endpoints rather than one. The streaming endpoint delivers sub-second transcription but drops speaker diarization and word timestamps. The batch endpoint retains both features at half the cost. Google reports 4.0% word error rate on streaming and 2.6% on non-streaming, with 70% faster finalization than Chirp 3. Builders building voice agents should test both endpoints this week to decide whether the diarization trade-off is worth the latency savings. Source: marktechpost.com

Ornith 1.5: r/LocalLLaMA community Community users report Ornith 1.5 delivers strong tool-calling performance at roughly 130 tokens per second with MTP on consumer hardware. Testers describe it as filling the gap between Qwen 3.8 27B and a hypothetical faster 35B variant, calling it a practical daily driver for rapid tool-testing loops. The model runs well where larger Qwen variants felt too slow. Try it first on tool-heavy workflows before committing to larger closed models. Source: reddit.com

TelecomGPT-R1-9B: arXiv Researchers released TelecomGPT-R1-9B, a unified open-source reasoner fine-tuned from Qwen3.5-9B on a 67,427-example corpus covering protocol, knowledge, modeling, and fault axes. The model ranks first among open-source telecom LLMs on seven public benchmarks after multi-teacher LoRA SFT followed by GRPO with axis-aligned verifiers. It reaches performance comparable to closed frontier reasoners on telco-specific tasks. Developers in network operations should evaluate it for grounding in specifications and telemetry. Source: arxiv.org

Agent & Tool Developments

NPU engine reverse-engineering for llama.cpp: r/LocalLLaMA A developer reverse-engineered the Axera AX8850 NPU engine format (.axmodel) to patch GGUF weights directly into precompiled engines without vendor compilation. The approach stores int8 weights as two nibble planes and achieves 96% token agreement with CPU reference while running at 24.5 tokens per second decode on a Raspberry Pi 5. The same work fixed a previously unused batched-prefill path, reaching 716 tokens per second prompt processing. The full backend is a single 4.5k-line file in a llama.cpp fork; the project repo includes quick-start instructions and on-card harnesses. Edge-agent developers should test the GGML_AXCL build flag on aarch64 hardware this week. Source: reddit.com

TreeGraft speculative decoding: arXiv TreeGraft introduces a multi-drafter framework where drafters of different sizes jointly build a shared draft tree for speculative decoding. A lightweight scheduler distilled from an offline value system decides when to invoke the stronger drafter, and stronger expansions are integrated non-destructively. Across 10 model pairs and 6 benchmarks the method outperforms the better single-drafter baseline by 15.1% on average. The code is available at the linked anonymous repository. Teams running long-horizon agents should benchmark TreeGraft against their current speculative setup. Source: arxiv.org

Practical & Community

FIRSTPASS peer-review dataset: arXiv FIRSTPASS provides 3,668 multi-round editorial dialogues from Nature Communications across biology, chemistry, neuroscience, physics, and earth science, each labeled with the final editorial outcome. The dataset captures initial referee reports, author responses, and updated assessments, enabling training of AI systems that have never seen biology or chemistry review criteria. All parsing pipelines and evaluation scripts are released. Researchers building scientific-judgment benchmarks should start here instead of CS-only corpora. Source: arxiv.org

UPHELD conversational benchmark: arXiv UPHELD supplies hundreds of complete human-to-human dialogues written by professional script writers with 36,000+ per-turn human annotations. Classical automatic metrics and single LLM judges correlate poorly with expert ratings; a Mixture-of-Judges framework improves correlation by approximately 30%. The benchmark targets human-scale multi-turn consistency rather than short-form QA. Builders of long-running agents should adopt it for evaluation beyond factual correctness. Source: arxiv.org

Vagdhenu Sanskrit TTS pipeline: arXiv Vagdhenu adds a vrutta-aware frontend and reference-matching mechanism to an off-the-shelf flow-matching TTS backbone for faithful Sanskrit chant output. The pipeline routes Sanskrit through Kannada orthography to avoid schwa deletion and handles visarga sandhi and aspiration contrasts. Two deployments already cover 5,183 verses and 18,000 verses respectively. Teams working on low-resource or metrical language synthesis should examine the released frontend and dataset. Source: arxiv.org

Under the Hood: One-Token Entropy Regulation

Everyone talks about adaptive thinking in multimodal models as if the model simply decides how hard to reason. In practice the decision lives at a single token whose probability distribution entropy becomes the training signal. High entropy at that token means the model is still exploring whether to engage chain-of-thought; low entropy signals convergence on a policy. The training process therefore moves from high-entropy exploration, where many thinking strategies are tried, to low-entropy convergence where the model confidently chooses when to think. Because the signal is intrinsic, no external difficulty labels are required. The practical payoff appears on mixed workloads: complex questions receive full reasoning while simple ones skip it, cutting unnecessary compute without accuracy loss on easy items. The gotcha that bites most teams is assuming the entropy threshold transfers across domains; a threshold tuned on document QA often needs recalibration when the input distribution shifts to diagrams or tables.

Things to Try This Week

• Test Gemini 3.5 Transcribe batch endpoint on any existing transcription pipeline to measure the 70% faster finalization against your current latency budget.
• Build a small hardware-control prototype against the MHS research preview if you have access to lab or robotics equipment already driven by Claude Code.
• Run the llama.cpp AXCL backend on an aarch64 device with the provided quick-start to compare 24.5 t/s decode against your current edge inference setup.
• Evaluate Ornith 1.5 on a tool-calling loop you currently run with Qwen 3.8 27B to see whether the reported 130 t/s speed justifies switching your daily driver.

On the Horizon

• Anthropic expects to share more MHS safety evaluations once the research preview gathers sufficient partner feedback.
• Google has not yet announced whether Gemini 3.5 Transcribe will receive additional language coverage beyond the current 85+.
• The TreeGraft authors plan to release full training code after the anonymous review period.
• More NPU vendors are likely to face similar reverse-engineering pressure as GGUF adoption grows on edge silicon.

💬 Reply to this email — Patrick reads every one.

Share: X · LinkedIn · WhatsApp

Forwarded this email? Subscribe here — it's free.