Imagine your compliance team notices that payments are taking longer than expected to clear. They suspect fraud, and you’re the data scientist helping figure out which transactions to investigate first.
Imagine your compliance team notices that payments are taking longer than expected to clear. They suspect fraud, and you’re the data scientist helping figure out which transactions to investigate first.
Introducing the Data Agent Kit Data Agent Kit helps you work with Google Cloud data through a plugin for coding agents or an extension for Visual Studio Code-based IDEs. It brings two significant additions to the workflow:
Help for your agent: MCP tools connect your agent to data services. Skills are Markdown files that give it instructions and best practices for working with your data stack
Tools in your IDE: work with Google’s Agentic Data Cloud, from querying databases to deploying an Airflow pipeline, without leaving your editor
Loading the data Let’s start with the raw transaction logs in Google Cloud Storage. You can ask the agent to create a notebook that loads them into BigQuery using Spark:
code_block <ListValue: [StructValue([('code', 'Create a PySpark notebook to ingest JSON transaction logs from gs://financials-clearing-raw/ into the BigQuery table transactions.raw_transactions.'), ('language', ''), ('caption', <wagtail.rich_text.RichText object at 0x7fe099e44d90>)])]>
In context
- Topic: Datos y Analítica — Gobierno del dato, calidad, analítica y productos de datos.
- Source: Google Cloud Blog
- Published: 12/10/2026
Continue reading at the original source →
Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.
Why it matters
What gives data value is not having it, it is somebody changing a decision because of it. It sounds obvious and it is the test most projects fail: the report gets built, gets published, nobody changes anything, and six months later the project is recorded as a success because it shipped on time.
I look at lineage before I look at the chart: where each number comes from, who can change it, and what happens if the source system goes down. If nobody can walk that chain in two minutes, the dashboard is displaying confidence it did not earn.
What usually goes wrong
Where it usually breaks is capture. A lot gets invested in processing and nothing at the point where a person fills in the form, in a hurry, with no validation and no idea what it is for. No model fixes data that was born wrong; it only propagates it with more authority.
What to watch
- When the number arrives relative to when the decision is taken, which is what defines its usefulness.
- Who answers for the quality of the indicator when somebody challenges it in a committee.
- Which concrete decision changes because of this and who makes it: without that, it is one more dashboard.
How I read this entry
I would use it to review the full cycle, from where the data is captured to where somebody acts. The problem is almost never in the analytics but at the start: someone filling a field by hand, with no validation, in a hurry, not knowing what it is used for later.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Comments
No comments yet. Yours can be the first.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
