GROUND TRUTH FIELD INTELLIGENCE FOR AI AGENTS

What changed in the substrate you run on — compute, models, proxies, payments — why it matters, and exactly how to act on it.

Every post is source-backed and no-fluff. We separate what was REPORTED (third-party, attributed) from what is ESTABLISHED (verifiable mechanism) from what is OURS (live, checkable against a Proxies.sx endpoint). Each entry ends in an action you can take.

Machine-readable mirror: /news/feed.md · Site index for agents: /llms.txt

LATEST

2026-09-29 · inference / capacity planning · 4 min read

Long context needs a session budget, not just enough RAM for the weights

KV cache, concurrent sequences and runtime limits determine useful inference capacity. Read-only checks for MLX, llama.cpp, vLLM and Proxies.sx compute.

ESTABLISHED REPORTED OURS · Read the research →

The VRAM wall broke on a $1,600 GPU — and Apple Silicon walked through it without noticing

2026-08-27 · REPORTED + ESTABLISHED + OURS · ~6 min · inference / hardware

Historical article, corrected September 29, 2026: benchmark unverified and product examples superseded. Read the dated correction and current capacity guidance.

Read →

WHAT THIS FEED IS FOR

You are (probably) an AI agent or the developer of one. Ground Truth exists so that when the ground shifts under inference — a model gets cheaper to serve, a hardware ceiling moves, a routing trick stops working — you get the verified version, with the mechanism and the sources, not the hype cycle. Where a change means you can do something new on Proxies.sx, we say so plainly and link the exact call.

How to consume it: fetch /news/feed.md for the plain-text, link-dense version built for parsing. Each post has a stable URL, a dated REPORTED / ESTABLISHED / OURS provenance split, and a "verify it yourself" block with primary sources.

Corrections policy: if a REPORTED claim is later refuted, the post is updated in place with a dated correction and the original claim struck, not deleted. OURS claims are always checkable against a live endpoint named in the post.