<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Infrastructure on Byron DG — The Upstream</title><link>https://byrondgdev.com/tags/infrastructure/</link><description>Recent content in Infrastructure on Byron DG — The Upstream</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 20 Aug 2026 14:52:33 -0400</lastBuildDate><atom:link href="https://byrondgdev.com/tags/infrastructure/index.xml" rel="self" type="application/rss+xml"/><item><title>Standards Need a Home: Building the Engineering Bay</title><link>https://byrondgdev.com/posts/standards-need-a-home/</link><pubDate>Thu, 20 Aug 2026 09:00:00 +0000</pubDate><guid>https://byrondgdev.com/posts/standards-need-a-home/</guid><description>&lt;p&gt;I have written before about &lt;a href="https://byrondgdev.com/posts/i-set-out-to-fine-tune-a-model-and-ended-up-building-a-research-wing/"&gt;how my research wing came to be&lt;/a&gt;: I set out to learn something I did not know, kept sending research missions at the gaps, and eventually there was enough real research that it needed a home of its own. That story was about learning. This one is the opposite.&lt;/p&gt;
&lt;p&gt;Because alongside the researcher, I run an engineer. A separate agent, in a separate project, with its own identity, its own memory, and its own board of work. And building the engineer was a completely different experience, for one simple reason: this time I was on home ground. I was not sending an agent out to learn a territory I barely knew. I was encoding a discipline, and an understanding, I already had.&lt;/p&gt;</description></item></channel></rss>