<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>OpenAdapt Blog</title><link>https://blog.openadapt.ai/</link><description>Recent content on OpenAdapt Blog</description><generator>Hugo -- 0.164.0</generator><language>en-us</language><lastBuildDate>Mon, 27 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.openadapt.ai/index.xml" rel="self" type="application/rss+xml"/><item><title>The write audit: how to measure what your automation actually wrote</title><link>https://blog.openadapt.ai/posts/the-write-audit/</link><pubDate>Mon, 27 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog.openadapt.ai/posts/the-write-audit/</guid><description>Most automation teams report one success number, and that number quietly includes the runs that wrote the wrong thing and said it went fine. Here is a vendor-neutral protocol for separating the two: a four-outcome scorecard, an oracle-strength ladder, seven persistence faults worth injecting, and the sampling math to turn a week of shadow runs into a defensible bound.</description></item><item><title>Contribute data for credits</title><link>https://blog.openadapt.ai/posts/contribute-for-credits/</link><pubDate>Tue, 21 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog.openadapt.ai/posts/contribute-for-credits/</guid><description>An early-access program: when you hit a new way an automation silently fails, share a sanitized, de-identified signature of it and earn run credits, while every OpenAdapt user gets an engine that now refuses that failure. Raw recordings never leave your machine, and you approve every byte.</description></item><item><title>Compile once, govern every repair</title><link>https://blog.openadapt.ai/posts/2026-07-20-compile-once-govern-every-repair/</link><pubDate>Mon, 20 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog.openadapt.ai/posts/2026-07-20-compile-once-govern-every-repair/</guid><description>Reasoning through a known workflow on every run is wasteful and unsafe. Our new technical paper shows a different design: compile one demonstration into a deterministic program, repair targets when the interface drifts, and verify effects against the system of record instead of the screen. In a fault study measured end to end, screen-only checking silently accepted 75.0% of the wrong effects that actually occurred; one out-of-band record oracle cut that to 12.5%.</description></item><item><title>The silent wrong write: your automation should halt instead of guessing</title><link>https://blog.openadapt.ai/posts/silent-wrong-action/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog.openadapt.ai/posts/silent-wrong-action/</guid><description>Screen-only verification silently passed 5 of 7 transactional fault classes — a green banner over a wrong database. We found the failure class in our own engine first, fixed five silent wrong-write modes, and built effect verification against the system of record. Measured end to end: one out-of-band record oracle cuts undetected wrong effects from 75.0% to 12.5%.</description></item><item><title>The 500th run: compiled automation vs. computer-use agents</title><link>https://blog.openadapt.ai/posts/the-500th-run/</link><pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog.openadapt.ai/posts/the-500th-run/</guid><description>Same task, same success check, measured on openadapt-flow 0.1.0 on 2026-07-08: 100/100 for the compiled script, 20/20 for the agent. The difference was 4.9 s vs 37.5 s per run, and $0 vs $0.27.</description></item><item><title>We ran it on a real EMR. The compiler won.</title><link>https://blog.openadapt.ai/posts/openemr-benchmark/</link><pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog.openadapt.ai/posts/openemr-benchmark/</guid><description>Compiled workflows vs. a frontier computer-use agent on real OpenEMR, measured on openadapt-flow 0.1.0 on 2026-07-08: 20/20 vs 10/10 task success, 1.8x faster, $0 vs $0.55 per run in model spend — and with agent fallback, $0.029 vs $0.238 per successful run. Deterministic compilation wins on cost and latency, and never silently writes the wrong thing.</description></item></channel></rss>