Chronograph

Graph View

2026-05-10

8 min read

Martin Rosén-Lidholm
Martin Rosén-Lidholm

Daily D4 Digest — 2026-05-10

TL;DR

  • Cloudflare’s new Dynamic Workflows library enables per-tenant, per-agent durable execution at near-zero idle cost — a significant D1/D3/D4 infrastructure primitive.
  • WebRTC’s hard-coded packet-dropping behavior is fundamentally mismatched with voice-AI workloads; alternatives like MoQ are gaining traction for LLM-era real-time audio.
  • Anthropic’s Claude Code team advocates HTML over Markdown as LLM output format, unlocking richer interactive artifacts for engineering workflows.
  • OncoAgent demonstrates a dual-tier multi-agent architecture with privacy-preserving local/cloud split — a pattern applicable far beyond healthcare.
  • Sequoia’s “Services: The New Software” thesis and research-driven agent patterns signal the industry converging on agents-as-service-delivery.

Call to Action

  • Evaluate Cloudflare Dynamic Workflows for your multi-tenant agent orchestration layer — the MIT-licensed library could replace custom durable execution plumbing. Explore here
  • Audit your voice-AI transport layer: if you’re using WebRTC for agent-to-user voice, test whether prompt integrity degrades under packet loss. Consider MoQ-based alternatives. Read the analysis
  • Experiment with HTML-as-output for Claude Code / LLM-assisted code review — request interactive HTML artifacts instead of Markdown for PR reviews and architecture explanations. See examples

D1 — Agentic Engineering

Cloudflare Dynamic Workflows: Durable Execution as an Agent Primitive. Cloudflare has released Dynamic Workflows, an MIT-licensed library extending its durable execution engine so that workflow code can differ per tenant, per agent, or per request at runtime. Built atop Dynamic Workers, it enables platforms to serve millions of unique durable workflows at near-zero idle cost. The headline use cases — CI/CD pipelines and agent plan execution — map directly to D1 concerns. This is the kind of infrastructure that makes “bounded autonomy” practical: each agent’s execution plan is a distinct, durable workflow that can be inspected, replayed, and audited. For teams building agentic engineering platforms, this eliminates a major piece of custom orchestration. (Also D3, D4)

HTML as the Output Medium for Agentic Code Review. Thariq Shihipar from Anthropic’s Claude Code team makes a compelling case that HTML should replace Markdown as the default LLM output format. The practical implication for D1 workflows is significant: when Claude generates an HTML artifact for a PR review, it can include inline SVG diagrams, color-coded severity annotations, interactive diff navigation, and in-page search — all things flat Markdown cannot do. Simon Willison’s experiments confirm this works well with GPT-5.5 and Claude alike. For agentic engineering pipelines, this suggests that agent-generated artifacts (review reports, architecture docs, test plans) should be rich interactive documents, not flat text files. The constraint from the GPT-4 era — token limits favoring Markdown’s compactness — no longer applies with current context windows. (Also D2)

Research-Driven Agents: Read Before You Code. Buried in Andriy Burkov’s AI newsletter #326 is a link to SkyPilot’s work on “research-driven agents” — agents that read documentation and papers before generating code. This pattern is directly relevant to D1: instead of relying purely on pre-trained knowledge, the agent performs explicit information retrieval as a planning step. This is a concrete implementation of the “Specify → Plan → Verify → Apply → Observe” lifecycle, where the Plan phase includes autonomous literature/API-doc review.

D2 — AI in the Product

OncoAgent: Privacy-Preserving Multi-Agent Architecture for Clinical Decision Support. The OncoAgent paper presents a dual-tier multi-agent framework where privacy-sensitive processing happens locally while cloud-based agents handle heavier reasoning. The architectural pattern — splitting agent responsibilities across trust boundaries — is broadly applicable beyond oncology. For any product embedding AI agents that handle sensitive data (legal, financial, healthcare), the local/cloud split with explicit data boundaries is a design template worth studying. The multi-agent orchestration approach also demonstrates how domain-specific agents (radiology, pathology, treatment planning) can be composed into a coherent decision-support workflow. (Also D1)

WebRTC Is the Wrong Transport for Voice AI. Luke Curley’s critique of WebRTC for LLM voice applications, written in response to OpenAI’s post on delivering low-latency voice AI at scale, identifies a fundamental mismatch: WebRTC aggressively drops audio packets to maintain latency for conversational cadence, but for voice-to-LLM pipelines, prompt accuracy matters far more than 200ms of latency. A dropped packet means a corrupted prompt, which means a garbage response from an expensive inference call. Curley notes from his Discord experience that it’s literally impossible to retransmit a WebRTC audio packet in-browser — the implementation is hard-coded for real-time-or-nothing. For any team building voice-first AI products, this is a critical architectural consideration: the transport layer you inherit from video calling is actively sabotaging your AI quality. MoQ (Media over QUIC) is positioned as the alternative. (Also D4)

D3 — Build for Agents

Dynamic Workflows as Agent-to-Platform Interface. Cloudflare’s Dynamic Workflows is also a D3 story: the ability to instantiate unique durable workflows per agent at runtime is precisely the kind of infrastructure needed for B2A (business-to-agent) platforms. An external agent can submit a workflow definition and have it executed durably with full observability. The MIT licensing is notable — Cloudflare is seeding an ecosystem, not locking it down. This could become a de facto execution substrate for agent interoperability, complementing protocol-level standards like MCP and A2A with a runtime-level primitive.

Sequoia’s “Services as Software” Framing. Referenced in Burkov’s newsletter, Sequoia’s thesis that “services are the new software” is a D3 signal: as agents become service consumers, the interface between businesses and AI shifts from APIs-for-humans to APIs-for-agents. The implication is that every SaaS product needs to think about its agent-consumable surface — not just its human UI.

D4 — Performance & Cost at Scale

Near-Zero Idle Cost for Per-Agent Workflows. The most D4-relevant detail from Cloudflare’s Dynamic Workflows announcement is the cost model: millions of unique durable workflows at near-zero idle cost. In an agentic world where each tenant or each agent may have distinct execution logic, the traditional model of always-on compute per workflow becomes prohibitively expensive. Cloudflare’s approach — essentially serverless durable execution — addresses the 10-100x traffic multiplier that agents create. When every API call might spawn sub-agents, each with their own workflow, the cost of idle compute dominates. This is hardware-sympathetic design for the agentic era.

WebRTC’s Hidden Inference Cost. Luke Curley’s analysis has a non-obvious D4 angle: when WebRTC drops audio packets and corrupts prompts, the downstream inference call still runs at full cost — you’re paying for a garbage response. In high-volume voice AI deployments, the effective cost of inference is higher than the per-token price because a percentage of calls are wasted on corrupted inputs. Switching to a reliable transport (even at slightly higher latency) could reduce effective inference cost by eliminating these waste calls.

Software Civil Engineering Lens

Today’s items offer two substantive connections to the SCE thesis:

Durable execution as “building code.” Cloudflare’s Dynamic Workflows is an infrastructure primitive that enforces a key SCE property: observability and auditability of agent execution. Every durable workflow can be inspected, replayed, and debugged — analogous to how civil engineering requires that structural calculations be reviewable and reproducible. The fact that this is now available as a commodity (MIT-licensed, serverless, near-zero idle cost) lowers the barrier to building agent systems that meet the “simulation and verification” pillar. The workflow itself becomes the blueprint — a persistent record of what the agent planned and executed.

The HTML-over-Markdown shift maps to the “formal specification” pillar. When an agent generates a PR review as an interactive HTML document with color-coded severity, inline annotations, and navigable diffs, it’s moving from informal communication toward something closer to a structured engineering deliverable. This isn’t a full formal spec, but it’s a significant step up from flat text. The pattern suggests that agent-generated artifacts will increasingly look like engineering documents rather than chat responses — richer, more structured, more verifiable. This is the kind of toolchain evolution that makes “human on the loop” feasible: you can review a well-structured HTML report in minutes rather than parsing walls of Markdown.

The OncoAgent dual-tier model illustrates “bounded autonomy.” The explicit split between local (privacy-preserving) and cloud (high-capability) agents, each operating within defined boundaries, is a textbook implementation of the SCE principle that agents should operate within spec constraints. The architecture itself encodes the compliance requirements — privacy boundaries aren’t a policy overlay, they’re structural. This is analogous to how building codes aren’t suggestions applied after construction; they shape the design.

Sources