Sundar NathanGuestShubhangi DuaHostSo what would the architecture look like instead? And what would it mean to actually make that enterprise data current, consistent, consumable, and contextual?

Great question, right? So today, people have cloud warehouses and those are great for maintaining the historical information, right? But you need a nervous system, not an annual physical or even a weekly full body scan as they have these days, right? The warehouse, data warehouse is your physical or full body scan that you might do once a week or once a year.

In the case of modern, obviously data warehouse environments, it's 20 minutes or so, but In the case of your nervous system, the difference between a nervous system and a physical, your nervous system is conveying something to your brain in milliseconds, and you act immediately.

That's the layer between the systems of record that you have and the systems of reasoning that an agent is going to act on.

So we actually describe what that layer has to be with the four words that you mentioned, the four C's.

Now, the order matters, right? Because when you think about current, current has to be first.

The moment a row changes in a core banking system or a transaction happens, that change is captured from the database's own transaction log, non-invasively, and it's moving within seconds, right? So not polled, not scheduled.
So I recently had a conversation with someone about the semantic layer and how context can be taken out of place, especially with like, for instance, there's an enterprise using different dashboards and different tools.
And they're looking at this particular tool They've asked the AI agent to get the data and present this data or this stat to the boardroom, let's say.
And then when they prompt the agent again to get possibly the same data, the agent presents a different number, but it's not a wrong number.

It's really critical that you have obviously real-time data that is also transactionally consistent.

A raw change event from a mainframe is basically codes and foreign keys that made sense to a programmer in 1994.

Now, the layer that I'm talking about shifts it in flight into something that is answer-shaped, that is consumable by an agent.
So what would the architecture look like instead? And what would it mean to actually make that enterprise data current, consistent, consumable, and contextual?

Great question, right? So today, people have cloud warehouses and those are great for maintaining the historical information, right? But you need a nervous system, not an annual physical or even a weekly full body scan as they have these days, right? The warehouse, data warehouse is your physical or full body scan that you might do once a week or once a year.

In the case of modern, obviously data warehouse environments, it's 20 minutes or so, but In the case of your nervous system, the difference between a nervous system and a physical, your nervous system is conveying something to your brain in milliseconds, and you act immediately.

That's the layer between the systems of record that you have and the systems of reasoning that an agent is going to act on.

So we actually describe what that layer has to be with the four words that you mentioned, the four C's.

Now, the order matters, right? Because when you think about current, current has to be first.

The moment a row changes in a core banking system or a transaction happens, that change is captured from the database's own transaction log, non-invasively, and it's moving within seconds, right? So not polled, not scheduled.
So I recently had a conversation with someone about the semantic layer and how context can be taken out of place, especially with like, for instance, there's an enterprise using different dashboards and different tools.
And they're looking at this particular tool They've asked the AI agent to get the data and present this data or this stat to the boardroom, let's say.
And then when they prompt the agent again to get possibly the same data, the agent presents a different number, but it's not a wrong number.

It's really critical that you have obviously real-time data that is also transactionally consistent.

A raw change event from a mainframe is basically codes and foreign keys that made sense to a programmer in 1994.

Now, the layer that I'm talking about shifts it in flight into something that is answer-shaped, that is consumable by an agent.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.