<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>thepragmaticquant</title><description>Building tools and writing about them honestly.</description><link>https://thepragmaticquant.com/</link><item><title>When is the swarm actually done?</title><link>https://thepragmaticquant.com/when-is-the-swarm-actually-done/</link><guid isPermaLink="true">https://thepragmaticquant.com/when-is-the-swarm-actually-done/</guid><description>Three services across a network, one dropped task, and a question nobody on the wire can answer: did the work actually get done? A copy-paste demo that exits 0 and prints SUCCESS while the real job dies unseen.</description><pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate><category>agents</category><category>distributed-systems</category><category>the problem</category><category>swarm</category></item><item><title>Task was destroyed but it is pending</title><link>https://thepragmaticquant.com/task-was-destroyed-but-pending/</link><guid isPermaLink="true">https://thepragmaticquant.com/task-was-destroyed-but-pending/</guid><description>A teardown deadlock I diagnosed in Google&apos;s A2A reference SDK — Issue #1101, PR #1105 (313 lines, tests, CI green, open for review) — turned out to be one symptom of a primitive the whole agent ecosystem is missing: a sound signal that an async mesh has actually settled.</description><pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate><category>a2a</category><category>agents</category><category>structured-concurrency</category><category>the problem</category></item><item><title>The first file an agent reads</title><link>https://thepragmaticquant.com/the-first-file-an-agent-reads/</link><guid isPermaLink="true">https://thepragmaticquant.com/the-first-file-an-agent-reads/</guid><description>Coding agents read your library before they use it, and they start with the code — `__init__.py`, the type hints, the tool schemas — not your docs site. Here is how I made waitbus speak to that reader, and the one piece of documentation I deliberately did not ship.</description><pubDate>Fri, 19 Jun 2026 00:00:00 GMT</pubDate><category>waitbus</category><category>agents</category><category>documentation</category><category>mcp</category></item><item><title>Your AI coding agents can&apos;t hear each other — not even across vendors</title><link>https://thepragmaticquant.com/coding-agents-cant-hear-each-other/</link><guid isPermaLink="true">https://thepragmaticquant.com/coding-agents-cant-hear-each-other/</guid><description>Your Claude Code, your Cursor, your tests, your CI — all on one box, none able to hear the others finish or fail. Here&apos;s the problem, and the proof: five real LLM agents on one bus, one fails, all wake.</description><pubDate>Sun, 14 Jun 2026 00:00:00 GMT</pubDate><category>waitbus</category><category>agents</category><category>the problem</category><category>swarm</category></item><item><title>How waitbus works: from event source to a waiting agent, over MCP</title><link>https://thepragmaticquant.com/source-to-subscriber-milliseconds/</link><guid isPermaLink="true">https://thepragmaticquant.com/source-to-subscriber-milliseconds/</guid><description>The architecture end to end — how an event gets from a source to a waiting agent in single-digit milliseconds, how an agent actually talks to the bus over MCP, and the decisions behind the build with what each one cost.</description><pubDate>Sun, 14 Jun 2026 00:00:00 GMT</pubDate><category>waitbus</category><category>latency</category><category>mcp</category><category>engineering</category></item><item><title>The numbers and the trust trail: benchmarking waitbus honestly</title><link>https://thepragmaticquant.com/why-my-benchmarks-lied/</link><guid isPermaLink="true">https://thepragmaticquant.com/why-my-benchmarks-lied/</guid><description>Two kinds of trust in one place — the benchmark methodology that makes the speed numbers survive a skeptic (Coordinated Omission, a bimodal p99, costs published as losses), and the supply-chain trail that lets you trust the artifact you install (SLSA provenance, sigstore, reproducible builds, and an honest list of the gaps).</description><pubDate>Sun, 14 Jun 2026 00:00:00 GMT</pubDate><category>waitbus</category><category>benchmarks</category><category>supply-chain</category><category>security</category></item><item><title>Thirty-one papers, zero error analyses</title><link>https://thepragmaticquant.com/thirty-one-papers-zero-error-analyses/</link><guid isPermaLink="true">https://thepragmaticquant.com/thirty-one-papers-zero-error-analyses/</guid><description>A sliding-window inner product updated one product at a time is the streaming similarity engine under motif and anomaly mining — its rounding error grows linearly in stream length, and across thirty-one matrix-profile papers nobody had ever done the forward-error math, or turned the fix into a config knob.</description><pubDate>Fri, 12 Jun 2026 00:00:00 GMT</pubDate><category>floating-point</category><category>time-series</category></item><item><title>The accumulator that never moved</title><link>https://thepragmaticquant.com/the-accumulator-that-never-moved/</link><guid isPermaLink="true">https://thepragmaticquant.com/the-accumulator-that-never-moved/</guid><description>An adversarial input where round-to-nearest throws away every increment in the same direction while the true sum climbs — and the coin flip that breaks the adversary&apos;s one weapon, measured across 20,000 seeds.</description><pubDate>Fri, 12 Jun 2026 00:00:00 GMT</pubDate><category>floating-point</category><category>formal-methods</category><category>time-series</category></item><item><title>The error analysis everyone cites is for a kernel nobody runs</title><link>https://thepragmaticquant.com/the-kernel-nobody-analyzed/</link><guid isPermaLink="true">https://thepragmaticquant.com/the-kernel-nobody-analyzed/</guid><description>SCAMP and STUMPY accumulate a mean-centred covariance, not the textbook inner product — and the centred case is structurally different floating-point mathematics, not a special case at mu = 0.</description><pubDate>Fri, 12 Jun 2026 00:00:00 GMT</pubDate><category>floating-point</category><category>time-series</category><category>formal-methods</category><category>evals</category></item><item><title>Green is not evidence</title><link>https://thepragmaticquant.com/green-is-not-evidence/</link><guid isPermaLink="true">https://thepragmaticquant.com/green-is-not-evidence/</guid><description>An experiment can validate the wrong quantity against the wrong envelope and pass, a self-test canary can fail identically whether the gate works or not, and an audit command can print nothing and exit 0 — three gate designs that read green while checking nothing.</description><pubDate>Fri, 12 Jun 2026 00:00:00 GMT</pubDate><category>formal-methods</category><category>evals</category></item><item><title>Three axioms and one disclosed seam</title><link>https://thepragmaticquant.com/three-axioms-and-one-disclosed-seam/</link><guid isPermaLink="true">https://thepragmaticquant.com/three-axioms-and-one-disclosed-seam/</guid><description>Four verification tools, one certificate: every machine-checked theorem mechanically reduced to three classical axioms with zero unfinished proofs — and the one place two provers cannot talk to each other, named right in the theorem statements.</description><pubDate>Fri, 12 Jun 2026 00:00:00 GMT</pubDate><category>formal-methods</category><category>lean</category><category>floating-point</category><category>evals</category></item><item><title>One earthquake pinned my error bound forever</title><link>https://thepragmaticquant.com/one-earthquake-pinned-my-bound/</link><guid isPermaLink="true">https://thepragmaticquant.com/one-earthquake-pinned-my-bound/</guid><description>A seismic stream, a global magnitude bound wrecked by a single mainshock, a windowed bound that heals — and a scoreboard where the headline empirical legs of two papers report zero violations.</description><pubDate>Fri, 12 Jun 2026 00:00:00 GMT</pubDate><category>floating-point</category><category>time-series</category><category>evals</category></item></channel></rss>