<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Research-Factory on Byron DG — The Upstream</title><link>https://byrondgdev.com/tags/research-factory/</link><description>Recent content in Research-Factory on Byron DG — The Upstream</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 23 Jun 2026 21:53:58 -0400</lastBuildDate><atom:link href="https://byrondgdev.com/tags/research-factory/index.xml" rel="self" type="application/rss+xml"/><item><title>Research Once, Render Many</title><link>https://byrondgdev.com/posts/research-once-render-many/</link><pubDate>Tue, 23 Jun 2026 09:00:00 +0000</pubDate><guid>https://byrondgdev.com/posts/research-once-render-many/</guid><description>&lt;p&gt;In the last post I landed on a rule: tooling is hygiene, workflow is leverage. This post is about a piece of that workflow, and it starts with something I bet you have done. You ask an AI a real question, the kind that takes some digging, and you get back a genuinely good answer. A few days later you need that same material as a short summary for a colleague. Then someone wants it as slides. Then you want a version you can actually read on your phone.&lt;/p&gt;</description></item></channel></rss>