<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Authorization on DataAgentX</title><link>https://e343c64b.dataagentx.pages.dev/en/tags/authorization/</link><description>Recent content in Authorization on DataAgentX</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 08 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://e343c64b.dataagentx.pages.dev/en/tags/authorization/index.xml" rel="self" type="application/rss+xml"/><item><title>The Data Agent Access Layer: Finding the Right Data Before Querying</title><link>https://e343c64b.dataagentx.pages.dev/en/tech/20260908-data-access-and-context-routing/</link><pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate><guid>https://e343c64b.dataagentx.pages.dev/en/tech/20260908-data-access-and-context-routing/</guid><description>&lt;p&gt;“Why did new-customer conversion fall this month?” A warehouse may contain a production funnel model, a similarly named test table, and a spreadsheet from last quarter’s campaign. All three are reachable. All three have plausible columns. If the agent chooses the wrong one, polished SQL and charts only make the error more persuasive.&lt;/p&gt;&#10;&lt;p&gt;Before query generation, the access layer must answer three questions: What may this identity access? What should this task use? Is the selected evidence sufficient for the claim? It is not a pipe that dumps every schema into a prompt. It is a permission-aware discovery and context-routing system.&lt;/p&gt;</description></item></channel></rss>