06-reference

dataengineeringweekly 288 agentic data stack dbt summit

2026-09-20·reference·source: Data Engineering Weekly·by Ananth Packkildurai
data-engineeringagentic-data-stacksemantic-layerdbtdata-platform-ops

Why this is in the vault

Issue #288 curates dbt Summit takeaways plus eight engineering write-ups (Airbnb, Canva, Booking.com, Orb, Bolt, an infra-cost tip, and a "big data or not" essay) — the sharpest item is a proposal for governing AI-agent data access via version-controlled semantic context, a direct hit on RDCO's own agent-governance framing.

Mapping against Ray Data Co

The load-bearing item is Joanna He's "Beyond the Semantic Layer: Engineering the Agentic Data Stack": agents can't reliably work from raw tables and undocumented business rules, so the proposed fix keeps metrics, relationships, permissions, and business context as version-controlled files that agents read through a controlled gateway before querying — the same shape as RDCO's own vault + knowledge-graph discipline (qmd + graph-ingest) enforcing that an agent's working context is explicit and versioned rather than tribal knowledge re-guessed each session. This is the second consecutive DEW issue converging on "agent reads the mess, writes/reads the governed version" (see #287's BlaBlaCar item) — worth treating as a recognized pattern when RDCO pitches agent-deployment work to a technical buyer, not a one-off. Secondary relevance: the editor's own skepticism of the DAVE-stack article ("do we really have a big data problem?") is a useful gut-check against over-architecting RDCO's own tooling before the actual data volume justifies it — a discipline note more than a technical one.

Curation section

No deep-fetches this issue — each blurb (Joanna He's included) already names the concrete mechanism and result, enough to assess relevance without following the link.

⚠️ Sponsorship

One paid third party plus one house self-promo:

Related