<?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>Paper on OpenAdapt Blog</title><link>https://blog.openadapt.ai/tags/paper/</link><description>Recent content in Paper on OpenAdapt Blog</description><generator>Hugo -- 0.164.0</generator><language>en-us</language><lastBuildDate>Mon, 20 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.openadapt.ai/tags/paper/index.xml" rel="self" type="application/rss+xml"/><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, screen-only checking silently accepted 50 of 90 wrong outcomes; an effect check caught every one.</description></item></channel></rss>