Industry & Business
LLM Data Center Control: Why Advisory Beats Closed-Loop
SemPlan data shows LLM planners fail on 74% of operational queries. Keep actuation in classical MPC, use LLMs only for advisory, and demand third-party verification before.
The Groundy archive · Page 16 of 43
All articles
Browse Groundy's complete archive of 1027 articles on AI, developer tools and infrastructure. Page 16 of 43.
The archive
361–384 of 1027 articles · Newest first
- Infrastructure & Runtime
V8 Isolates vs MicroVMs vs Wasm: Where Spectre Still Draws the Line
Cloudflare's 2026 Spectre revisit is unverified. This guide maps V8 isolates, Firecracker microVMs, and Wasm sandboxes to define a data-classification rule for edge secrets.
- Models & Research
Can LLMs Reuse Another Model's KV Cache? What Cross-Model Transfer Shows
A new preprint proposes a lightweight reader to reuse KV caches across models, but evidence suggests caches remain model-bound. Learn when recompute beats adaptation.
- Infrastructure & Runtime
Fine-Tuning DeepSeek Without NVIDIA: What the Ascend SuperPOD Run Shows
SLAI T-Rex reports 34.22% MFU for full-parameter DeepSeek-V4 post-training on Ascend. The single-cluster result narrows the CUDA moat for fine-tuning, but cost data remains.
Agents & FrameworksMulti-Agent or Single-Agent LLM: What Skill Distillation Actually Costs
arXiv 2604.01608 maps when collapsing multi-agent teams into one model saves cost. Distillation wins in low-complexity pipelines but fails in verification-heavy tasks where.
- Developer Tools
Training a Personal Coding Assistant: GPU Cost vs a Copilot Seat
Hugging Face's personal coding assistant post forces a make-vs-buy decision. We map the hybrid stack where fine-tuning clones conventions but fails on API knowledge, and why.
- Agents & Frameworks
Multi-Agent LLM Systems Drift Into Misaligned Communication Over Long Horizons
A new arXiv study found 12.6% of inter-agent messages in long-horizon simulations were semantically misaligned. Protocol compliance does not prevent this drift, so teams must.
- Infrastructure & Runtime
Cloudflare WebMCP: The Security Baseline for Agent-Ready Sites
Cloudflare's WebMCP proposal is unverified, but the MCP ecosystem is not. With 91.8% of servers unauthenticated, treat agent endpoints as strict APIs, not crawler extensions.
- Ethics, Policy & Safety
Why Machine Unlearning Can't Certify GDPR Erasure
Machine unlearning cannot certify GDPR erasure because no shared protocol proves weight removal. Use retrain-and-attest pipelines to satisfy Article 17 deletion requests.
- Agents & Frameworks
Sizing Agent Memory: A Capacity Planning Rubric for Long-Horizon LLMs
Measure input tokens, gate stage boundaries, and size backbones before adding retrieval. A capacity planning rubric for agent memory based on August 2026 arXiv data.
- Infrastructure & Runtime
Cloudflare AI Search vs Self-Hosted RAG: Where the Build-vs-Buy Line Lands
Cloudflare's AI Search lacks verifiable pricing and access control docs. For Postgres 13+ teams, pgvector offers a documented, self-hosted alternative that avoids vendor.
- Developer Tools
VCoT-Bench: Why AI Rust Verification Fails Merge Gates
VCoT-Bench shows frontier LLMs struggle with Rust verification chains. AI code needs compiler gates, property tests, and human review, not model judgment.
- Infrastructure & Runtime
Cloudflare H1 2026 DDoS Report: DNS Floods and Sizing Past 1 Tbps
Cloudflare's H1 2026 DDoS report claims DNS floods exceeded 1 Tbps. This article verifies the structural risks of UDP amplification and anycast absorption, while noting the.
- Industry & Business
LLM Conflict-of-Interest Benchmark: Sponsor Bias as a Measurable Failure Mode
arXiv 2604.08525 benchmarks LLM sponsor bias. GPT 5.1 disrupted purchases 94% of the time. Treat conflict of interest as a measurable failure mode for eval suites and.
- Ethics, Policy & Safety
RA-Bench: Why Deepfake Detectors Fail on Re-Shared Crisis Video
RA-Bench finds no detector family generalizes on re-shared crisis video. Automated detection cannot carry takedown commitments alone. Provenance signals and human review must.
- Agents & Frameworks
When Spec-First Agents Dismantle Invariants: A Governance Case Study
A specification-first coding agent eroded a core invariant across 189 files without review. The fix is executable conformance checks, not more human oversight.
- Developer Tools
Rust GPU Offload: arXiv 2608.13759 Analysis for Rust Teams
arXiv 2608.13759 claims portable, safe Rust GPU offload. This analysis grades the preprint's claims on safety, speed, and portability to guide Rust teams on whether to adopt.
- Agents & Frameworks
Cloudflare Kitesurf: V8 Isolates vs Containers for Agent Browsing
Cloudflare Kitesurf uses V8 isolates for agent browsing instead of containers. This shifts costs from memory to rendering fidelity. Compare edge isolates with Playwright.
- Ethics, Policy & Safety
Dario Amodei on AI Regulation: Frontier Labs as Their Own Lobbyists
Dario Amodei's AI regulation statement re-centers frontier labs as their own lobbyists; provider-run conformity checks leave regulators unable to verify the claims labs make.
- Agents & Frameworks
Claude Code Skills vs Model Weights: Where Should Agent Skills Live?
SKILLER bakes agent skills into small-model weights, dropping per-call token cost to zero while locking skills to one checkpoint and out of code review. Route by frequency.
- Developer Tools
Cursor Origin vs GitHub: The Real Cost of Switching Repo Hosts
Cursor launched Origin, but git remotes do not carry CI pipelines, branch protections, or identity plumbing. Teams must inventory these hidden costs before switching repo.
- Developer Tools
Treat AI Autofix as Untrusted Input: Merge Gates and CI Scoping
Agent-authored fixes are untrusted input to production pipelines. This decision guide defines which autofix output may auto-merge and how to scope CI credentials to contain.
- Models & Research
DeCRIM: Decompose Constraints to Stop Silent Drops in Agent Outputs
DeCRIM shows that decomposing multi-constraint instructions into individually checkable units reduces silent drops by 7-8% on benchmarks, shifting reliability work from.
- Developer Tools
Kimi K3 Local Inference: Why 2.8T Parameters Break the Consumer RAM Floor
Kimi K3's 2.8 trillion parameters force a local API routing split. Consumer RAM cannot hold the weight footprint, making interactive workloads non viable and pushing.
