<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Lakehouse on DataAgentX</title><link>https://e343c64b.dataagentx.pages.dev/en/tags/lakehouse/</link><description>Recent content in Lakehouse on DataAgentX</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 29 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://e343c64b.dataagentx.pages.dev/en/tags/lakehouse/index.xml" rel="self" type="application/rss+xml"/><item><title>Inside DataBuddy: Why Data Agents Need a Shared Data Foundation</title><link>https://e343c64b.dataagentx.pages.dev/en/products/20260929-tencent-databuddy-shared-foundation/</link><pubDate>Tue, 29 Sep 2026 00:00:00 +0000</pubDate><guid>https://e343c64b.dataagentx.pages.dev/en/products/20260929-tencent-databuddy-shared-foundation/</guid><description>&lt;p&gt;An analytics agent reports 120,000 new users. The operating dashboard says 108,000. Both can show their SQL, and both claim to use current data. The problem is larger than one wrong answer: do the agent and the existing data products share the same assets, semantics, identity, and controls?&lt;/p&gt;&#10;&lt;p&gt;That question makes DataBuddy’s architecture more interesting than its three visible roles—data engineering, analytics, and governance agents. Underneath them, the product connects ingestion, lakehouse storage, catalog, unified semantics, and AI-ready data knowledge into a shared chain. An Agent Harness ties that chain to context, tools, security, and evaluation.&lt;/p&gt;</description></item></channel></rss>