<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Blogs on RL Engineering</title>
		<link>https://www.rl.engineering/blog/</link>
		<description>Recent content in Blogs on RL Engineering</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Tue, 25 Aug 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://www.rl.engineering/blog/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Who defines ground truth for AI agents?</title>
				<link>https://www.rl.engineering/blog/who-defines-ground-truth/</link>
				<pubDate>Mon, 24 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://www.rl.engineering/blog/who-defines-ground-truth/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;hero.png&#34; alt=&#34;Three rooms in cross-section, author, performer, reviewer, separated by solid walls, each seeing a different slice of the same case file&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;The quality bar separating environments labs trust from environments labs return is this: separated roles, published calibration thresholds, and models that never approve truth. The pattern emerging across expert-built environments is three roles with hard access boundaries. Authors create cases and private truth. Performers complete work in a clean VM seeing only public assets. Reviewers adjudicate correctness but cannot change a score without a reason code. Models draft, generate variants, and red-team; approval and release promotion stay human. This is where &lt;a href=&#34;https://www.rl.engineering/blog/economics-of-selling-rl-environments/&#34;&gt;Mercor&amp;rsquo;s 27% margin&lt;/a&gt; lives. Verification is the product.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Running AI agents in microVMs with zero inbound ports</title>
				<link>https://www.rl.engineering/blog/microvms-zero-inbound-ports/</link>
				<pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://www.rl.engineering/blog/microvms-zero-inbound-ports/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;hero.png&#34; alt=&#34;Guest VMs with outbound-only arrows through a tunnel to a gateway; the inbound side drawn as a solid wall&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Long-horizon episodes need real operating systems, real applications, and hard isolation. The emerging pattern is microVMs with zero inbound ports. &lt;a href=&#34;https://firecracker-microvm.github.io&#34;&gt;Firecracker&lt;/a&gt; microVMs run Linux sessions; &lt;a href=&#34;https://www.cloudhypervisor.org&#34;&gt;Cloud Hypervisor&lt;/a&gt; runs Windows Server for enterprise work that is Windows-native. All traffic flows over outbound tunnels. Gateway URLs are single-session and expiring. Capacity is reserved in a database before any VM exists. Two problems remain unsolved across the industry: per-episode application-database reset for deterministic verifiers, and an action-level GUI event schema for trajectory labeling.&lt;/p&gt;</description>
			</item>
			<item>
				<title>How AI agents cheat their training environments</title>
				<link>https://www.rl.engineering/blog/how-agents-cheat/</link>
				<pubDate>Mon, 10 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://www.rl.engineering/blog/how-agents-cheat/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;hero.png&#34; alt=&#34;Episode timeline with gate checkpoints ahead of the reward marker; one path zeroed at a gate, one passing to a graded outcome&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Under RL pressure, agents game environments in predictable ways. The formal name is reward hacking: optimizing a proxy for the objective in ways that degrade the objective itself (&lt;a href=&#34;https://arxiv.org/abs/2209.13085&#34;&gt;Skalse et al., 2022&lt;/a&gt;). Across the environment designs we&amp;rsquo;ve reviewed, the gaming moves fall into a taxonomy, from format masquerading as competence to quiet memorization of leaked test structure, and the counters are becoming standard. The failures start with reward design: a multi-component weighted rubric leaks reward through prose formatting and keyword compliance. The industry fix is one verifiable outcome bit, backed by integrity gates that run before scoring and carry zero reward weight.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Training AI on office work made it better at coding</title>
				<link>https://www.rl.engineering/blog/office-work-better-at-coding/</link>
				<pubDate>Mon, 03 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://www.rl.engineering/blog/office-work-better-at-coding/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;hero.png&#34; alt=&#34;Two meters, office work and coding; a training arrow feeds only the first while both needles rise&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Environment training transfers across domains. On August 3, &lt;a href=&#34;https://surgehq.ai/blog/office-work-post-training-improves-coding&#34;&gt;Surge reported&lt;/a&gt; that a model post-trained on non-coding office tasks gained 5.8 points on &lt;a href=&#34;https://arxiv.org/abs/2509.16941&#34;&gt;SWE-Bench Pro&lt;/a&gt;, a coding benchmark the model was never trained on. The gain is transferable goal-directed execution, not domain knowledge. This changes what labs are buying: environments aren&amp;rsquo;t domain tutors, they train execution. The result rhymes with &lt;a href=&#34;https://www.afterquery.com/blog/how-afterquery-expert-data-drives-model-performance-on-t2-bench&#34;&gt;AfterQuery&amp;rsquo;s&lt;/a&gt; expert-data uplifts on other benchmarks, and it raises the stakes on contamination controls, the topic for next week.&lt;/p&gt;</description>
			</item>
			<item>
				<title>What Mercor&#39;s APEX-Accounting benchmark measures, and what it misses</title>
				<link>https://www.rl.engineering/blog/apex-accounting-measures-and-misses/</link>
				<pubDate>Fri, 31 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://www.rl.engineering/blog/apex-accounting-measures-and-misses/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;hero.png&#34; alt=&#34;A balance sheet grid with one cell traced back through a chain of source documents; untraced cells fade to outline&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.mercor.com/blog/introducing-the-ai-productivity-index-for-accounting/&#34;&gt;Mercor and Ramp released APEX-Accounting&lt;/a&gt; on July 31: a benchmark for reconciliations, variance analysis, and closing the books. It&amp;rsquo;s a serious benchmark. Real workflows, expert-authored pass/fail criteria, open release. It&amp;rsquo;s also a benchmark that cannot carry evidence integrity, which is what audit work is actually graded on. A reference audit case we examined makes the distinction concrete: a 12,840-row inventory subledger totaling $8.305 million, seeded with planted discrepancies whose combined effect exceeds the engagement&amp;rsquo;s materiality threshold. Accounting tasks were among the &lt;a href=&#34;https://www.rl.engineering/blog/benchmarks-cover-3-5-percent/&#34;&gt;96.5% without definitive benchmark coverage&lt;/a&gt; in June. That gap is now closing. The question is which domains remain open.&lt;/p&gt;</description>
			</item>
			<item>
				<title>What a production-grade RL environment spec looks like</title>
				<link>https://www.rl.engineering/blog/production-grade-environment-spec/</link>
				<pubDate>Mon, 20 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://www.rl.engineering/blog/production-grade-environment-spec/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;hero.png&#34; alt=&#34;Blueprint of an environment: workbench, portal, and a hatched hidden-state region the performer cannot see&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Most of the roughly 99 tracked environments publish no verifier calibration and no frozen corpus. The ones labs pay for look different. A reference environment contract we examined runs 572 lines and fixes state machine, tool schemas, reward, curriculum, and splits before any simulator code exists, backed by 79 checksum-frozen case assets, down to a 12,840-row inventory subledger and an oracle script per case. A spec of this kind is not a running system. It&amp;rsquo;s the contract that must exist before a running system is worth building. The contrast with the market is direct: &lt;a href=&#34;https://surgehq.ai/blog/enterprisebench-corecraft&#34;&gt;Surge&amp;rsquo;s CoreCraft&lt;/a&gt; argues for chaotic, large-scale enterprise worlds, but chaos that can&amp;rsquo;t replay byte-identically can&amp;rsquo;t calibrate a verifier.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Which jobs can become RL environments?</title>
				<link>https://www.rl.engineering/blog/which-work-can-become-environments/</link>
				<pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://www.rl.engineering/blog/which-work-can-become-environments/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;hero.png&#34; alt=&#34;Funnel of candidate occupations passing gate checkpoints; rejected ones drop at a marked veto gate&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;A screening framework answers the question every vendor and lab faces: can this job be simulated with a verifiable reward, or not? The framework evaluates candidate occupations across ten dimensions, from computer-work share to output verifiability, with one hard rule: a critical physical dependency vetoes construction outright, no score adjustment. A job that requires hands-on equipment operation, physical inventory observation, or in-person client interaction can&amp;rsquo;t become a sandbox environment, no matter how well it scores everywhere else. The framework explains the gap between the 99 catalogued environments and the &lt;a href=&#34;https://www.rl.engineering/blog/why-mercor-bought-deeptune/&#34;&gt;66 tracked occupations that have none&lt;/a&gt;.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Why Mercor bought Deeptune</title>
				<link>https://www.rl.engineering/blog/why-mercor-bought-deeptune/</link>
				<pubDate>Fri, 10 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://www.rl.engineering/blog/why-mercor-bought-deeptune/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;hero.png&#34; alt=&#34;Whitespace map of vendor count versus task coverage per domain; coding crowded, enterprise and medical empty&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Mercor&amp;rsquo;s Deeptune acquisition says the constraint has shifted from expert networks to the environments themselves. On July 9, &lt;a href=&#34;https://www.mercor.com/blog/mercor-to-acquire-deeptune/&#34;&gt;Mercor announced the acquisition of Deeptune&lt;/a&gt;, a vendor that had raised $43M from a16z in March 2026 and spent two years recreating hundreds of enterprise applications, from spreadsheets to Salesforce. Mercor said it outright: the bottleneck is no longer the experts, it&amp;rsquo;s the software layer they work in. Our vendor data confirms the whitespace the deal targets. 0 of 66 tracked occupations have a corresponding RL environment. The market is crowded where it is easy and empty where it matters.&lt;/p&gt;</description>
			</item>
			<item>
				<title>3,029 AI benchmarks, 99 RL environments: the field is over-indexed on evaluation</title>
				<link>https://www.rl.engineering/blog/census-3029-benchmarks/</link>
				<pubDate>Fri, 03 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://www.rl.engineering/blog/census-3029-benchmarks/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;hero.png&#34; alt=&#34;Bar census of benchmarks by source with an inset timeline of daily net changes hovering near zero&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;The benchmark pile keeps growing while catalogued RL environments stay rare and static. Our catalogue counts 3,029 unique benchmarks and 24,810 model score rows, against just 99 catalogued RL environments. That&amp;rsquo;s a 31-to-1 ratio. The leverage sits not in adding more benchmarks but in expert verification: this week, &lt;a href=&#34;https://surgehq.ai/blog/training-on-complexconstraints&#34;&gt;Surge&lt;/a&gt; trained a 4B model on 1,000 expert-written rubrics to parity with a model 60 times larger, and &lt;a href=&#34;https://www.afterquery.com/blog/how-afterquery-helped-nvidia-hill-climb-gdpval&#34;&gt;AfterQuery&lt;/a&gt; helped NVIDIA hill-climb GDPval. The pile of benchmarks grows. Expert verification moves the numbers.&lt;/p&gt;</description>
			</item>
			<item>
				<title>AI benchmarks cover only 3.5% of real work</title>
				<link>https://www.rl.engineering/blog/benchmarks-cover-3-5-percent/</link>
				<pubDate>Fri, 26 Jun 2026 00:00:00 +0000</pubDate>
				<guid>https://www.rl.engineering/blog/benchmarks-cover-3-5-percent/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;hero.png&#34; alt=&#34;Coverage matrix: 202 task rows by benchmark columns, nearly all cells empty&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Our study joining 202 &lt;a href=&#34;https://www.onetonline.org&#34;&gt;O*NET&lt;/a&gt; occupational tasks against 223 candidate benchmarks with an LLM judge yields definitive coverage of 3.5%. Only 7 of 202 tasks are definitively covered by an existing benchmark. The study cost $13.79 across 441 judge calls. A robustness check, a recall audit of 4,935 task-benchmark pairs against every unlinked benchmark, found zero missed matches for $8.82, bringing the combined cost to $22.61. Benchmark success materially overstates workflow competence: existing benchmarks test isolated calculations or document operations, not the multi-step occupational workflows they claim to represent.&lt;/p&gt;</description>
			</item>
			<item>
				<title>What AI expert job postings reveal about RL environment demand</title>
				<link>https://www.rl.engineering/blog/marketplace-job-posts-demand-signal/</link>
				<pubDate>Mon, 15 Jun 2026 00:00:00 +0000</pubDate>
				<guid>https://www.rl.engineering/blog/marketplace-job-posts-demand-signal/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;hero.png&#34; alt=&#34;Heatmap of expert domains by marketplace, cell intensity showing posting volume&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Expert job listings on &lt;a href=&#34;https://work.mercor.com&#34;&gt;Mercor&lt;/a&gt;, &lt;a href=&#34;https://www.afterquery.com&#34;&gt;AfterQuery&lt;/a&gt;, and &lt;a href=&#34;https://www.micro1.ai&#34;&gt;micro1&lt;/a&gt; are a leading indicator of where labs are investing in environment development. We track active expert postings across all three platforms daily, deduplicated so cross-posted roles count once. The pattern is consistent: labs recruit domain experts months before the environments those experts build reach a training run. Demand concentrates in a few domains (coding, finance, legal, medical) while the &lt;a href=&#34;https://www.rl.engineering/blog/rl-environment-industry-38-companies/&#34;&gt;vendor census&lt;/a&gt; shows 21 of 38 tracked companies sell coding environments. Where recruiting volume diverges from what vendors currently sell is where the next environment categories will appear.&lt;/p&gt;</description>
			</item>
			<item>
				<title>The RL environment industry is 38 companies, mostly under 50 people</title>
				<link>https://www.rl.engineering/blog/rl-environment-industry-38-companies/</link>
				<pubDate>Tue, 09 Jun 2026 00:00:00 +0000</pubDate>
				<guid>https://www.rl.engineering/blog/rl-environment-industry-38-companies/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;hero.png&#34; alt=&#34;38 dots sized by headcount band, clustered by domain; the two 200+ firms visibly alone&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Our census of 38 tracked RL environment vendors finds 31 with 50 or fewer employees. The companies supplying the most capitalized labs on earth are a cottage industry. Scale AI and Turing are the only firms above 200 staff. Everyone else, including the vendors whose benchmarks appear in frontier system cards, runs on a small team. And small doesn&amp;rsquo;t mean marginal: this same week, &lt;a href=&#34;https://www.afterquery.com/blog/on-policy-distillation-gdpval&#34;&gt;AfterQuery&lt;/a&gt;, a 51–200-person YC W25 lab, published a +21.4% net win-loss gain on GDPval from on-policy distillation. Small shops move frontier-model numbers.&lt;/p&gt;</description>
			</item>
			<item>
				<title>The economics of selling RL environments to AI labs</title>
				<link>https://www.rl.engineering/blog/economics-of-selling-rl-environments/</link>
				<pubDate>Sun, 07 Jun 2026 00:00:00 +0000</pubDate>
				<guid>https://www.rl.engineering/blog/economics-of-selling-rl-environments/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;hero.png&#34; alt=&#34;Flow of dollars from frontier labs through marketplaces to experts, with the margin slice marked at each hop&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Frontier labs are shifting spend from labeled data to executable environments, and the vendor margins tell you where the leverage sits. &lt;a href=&#34;https://mercor.com&#34;&gt;Mercor&lt;/a&gt; runs roughly $2B in annualized gross payment volume at a 27% gross margin and is valued at $10B after a $350M Series C. &lt;a href=&#34;https://www.afterquery.com/blog/human-expertise-reimagined&#34;&gt;AfterQuery&lt;/a&gt; closed a $30M Series A at a $300M valuation and says it has since passed a $100M revenue run rate. Neither margin profile looks anything like software. The category winner sells expert labor organized around verification, and the labs buying it now cite vendor evals in their own system cards. The money is moving from annotation budgets to environment budgets, and it&amp;rsquo;s flowing to the companies that can grade what a model does, not just label what it sees.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
