<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reference Architecture on DataAgentX</title><link>https://e343c64b.dataagentx.pages.dev/en/tags/reference-architecture/</link><description>Recent content in Reference Architecture on DataAgentX</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 04 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://e343c64b.dataagentx.pages.dev/en/tags/reference-architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Build a Data Agent: A Working Map from 23 Articles</title><link>https://e343c64b.dataagentx.pages.dev/en/tech/20261004-data-agent-series-recap/</link><pubDate>Sun, 04 Oct 2026 00:00:00 +0000</pubDate><guid>https://e343c64b.dataagentx.pages.dev/en/tech/20261004-data-agent-series-recap/</guid><description>&lt;p&gt;After surveying many Data Agent products, a team beginning implementation still faces five basic questions: What work should the system own? Which data should it use? How may it execute? How will we prove the result? Who remains accountable when it fails?&lt;/p&gt;&#10;&lt;p&gt;Those questions are more durable than a vendor list. They connect definition, architecture, autonomy, evaluation, and rollout.&lt;/p&gt;&#10;&lt;p&gt;The diagram below maps those questions onto an operating path: how a task enters the system, how semantics constrain planning and execution, and how evidence, approval, read-back, and feedback close the loop.&lt;/p&gt;</description></item></channel></rss>