For years, enterprise architecture has offered us a reassuring picture of how organizations work. We draw clean boxes around ERP, GIS, CRM, finance, asset management and work management, connect them with tidy arrows, and somewhere in the middle we place a system confidently labelled “source of truth,” as though the messy reality of an operating organization can be reduced to a single authoritative repository.
It is an elegant idea, but it has never been entirely true.
A work order can be complete in the field while labour is still being corrected. GIS can be authoritative about an asset’s location and condition while ERP is authoritative about its financial treatment. Operations may be entirely correct to move forward while Finance is equally correct to wait until a payroll cycle or accounting period has closed.
None of those systems is necessarily wrong. The truth is simply distributed across them.
Humans have managed this ambiguity for years with a mixture of experience, judgement, timing, exception handling and institutional memory. We know, often without writing it down, which record to trust in which circumstance, when a status should trigger action, when a process should pause, and when “complete” means something slightly different depending on who is looking at it.
That arrangement has survived largely because people have been quietly filling in the gaps.
AI agents are about to make those gaps impossible to ignore.
When AI Stops Observing and Starts Acting
The first generation of enterprise AI was largely asked to observe. It could summarize a document, surface information, classify a request or suggest an action, but a human remained between the model and the operating system.
The next generation is different.
Agents are increasingly being asked to create work, change records, trigger processes, initiate approvals, update systems and move decisions across applications. The moment that happens, the question is no longer whether the AI can understand the data. The question becomes whether the organization has ever clearly defined what that data means in context, who has authority over it, and what must be true before action is allowed to occur.
That is a much harder problem.
An AI agent does not merely need access to the enterprise. It needs to understand the rules that make the enterprise coherent.
If it reads a work order marked complete, should it post cost immediately, wait for payroll to finalize, reopen the work if a time entry changes, update the asset record, or trigger another process entirely?
The answer depends on business state, timing, authority and context, not simply on whether the data exists.
This is where the comforting idea of a single “source of truth” begins to break down.
The Problem Was Never Simply Data
Enterprise technology has spent decades trying to improve data quality, system integration and application interoperability, and all of that work has been necessary, but the persistence of reconciliation, manual intervention and operational ambiguity suggests that something deeper has always been happening underneath.
The problem is not merely that systems fail to share data.
The problem is that the meaning of the data changes as it moves.
A work order in the field is an operational event. The same work order in payroll becomes labour. In inventory, it becomes material consumption. In finance, it becomes recognized cost. In asset management, it becomes part of an asset’s history.
Those are not five versions of the same record. They are five interpretations of the same business event.
That distinction matters enormously once AI is allowed to act across them.
If an agent is going to operate reliably, it must know not only what the object is, but what the object means in the current context, which system is authoritative for which part of the truth, what state the object is in, and whether the timing of the action is valid.
Without that structure, AI does not remove ambiguity. It simply encounters it faster.
Source of Truth Is Usually a Set of Rules
This is the uncomfortable part.
In many organizations, “source of truth” was never really a system. It was a set of operating rules that people understood implicitly.
The field system owned completion. Payroll owned approved labour. GIS owned location. ERP owned cost. Finance owned recognition. The organization worked because experienced people understood how those truths related to one another and, more importantly, when one should take precedence over another.
That logic may have existed in process documents, but much of it lived in practice rather than architecture.
It lived in the supervisor who knew not to push a transaction until payroll closed. It lived in the analyst who understood why two systems appeared to disagree. It lived in the finance team that knew when a number was available but not yet financially valid. It lived in the operations manager who understood that “complete” meant the crew was done, not that the financial lifecycle was finished.
AI agents will force organizations to surface those rules because machines cannot safely operate on implied context.
If an agent is going to act independently, the organization must be able to explain exactly what authority means, exactly when state changes, exactly which system controls which decision, and exactly what should happen when legitimate systems disagree.
That is not simply an AI governance exercise. It is an operating-model exercise.
Why Workflow Governance Becomes the Real Constraint
As AI becomes more capable, the constraint on adoption may not be intelligence at all.
It may be confidence.
Can the organization trust an agent to create work because it knows precisely when that work should exist?
Can it trust the agent to update an asset because the source and state are unambiguous?
Can it allow an agent to move a cost toward Finance because the timing rules are understood and enforced?
Can it explain, after the fact, why the action occurred and which authority permitted it?
These questions sit underneath almost every meaningful enterprise use case for agentic AI, and they are especially important in cities, utilities and infrastructure organizations where operational systems, financial systems, GIS, work management and customer platforms all describe different parts of the same real-world event.
The more autonomous the system becomes, the less tolerance there is for ambiguity.
That is why the next generation of enterprise automation will require more than integration and more than intelligence. It will require a clear operating model that can be executed consistently across systems.
The Five Things That Must Be Explicit
For an AI agent to act reliably, five things that humans have traditionally carried in their heads need to become explicit.
1. Meaning
The first is meaning. The organization has to define what the business object actually represents as it moves from one system to another, because a “work order,” “asset,” “customer,” “meter” or “cost” can carry very different implications depending on where it sits in the workflow.
2. Authority
The second is authority. No single system is authoritative for everything, and pretending otherwise creates false simplicity. The useful question is not “what is the source of truth?” but “which system is authoritative for this part of the truth, at this point in the lifecycle?”
3. State
The third is state. A business object can be complete operationally, pending financially and unresolved administratively at the same time. The system has to understand that these states are not contradictions; they are different stages in the same process.
4. Timing
The fourth is timing. Some actions should happen immediately while others must wait for payroll cycles, accounting periods, approvals or regulatory conditions. Automation that moves quickly without understanding timing can create errors faster than people can repair them.
5. Repeatability
The fifth is repeatability. AI agents will retry, re-evaluate and revisit decisions, which means the operating model must define what happens when the same process runs twice, when data changes after an action, or when one event is replayed across several systems.
These are not theoretical concerns. They are the difference between automation that merely moves data and automation that can be trusted to operate.
AI May Finally Force Us to Document the Real Enterprise
There is an irony here.
For years, companies have invested enormous effort in digital transformation while leaving large parts of their operating logic undocumented. We have mapped applications, interfaces, data models and processes, but the real operating model often remained embedded in people.
AI may finally force us to confront that.
If an agent is going to take action rather than simply recommend it, the organization has to externalize what used to be tacit. It has to define which truth matters, when it matters, who owns it, and what the next valid action is.
In that sense, AI may not simply automate the enterprise.
It may expose the enterprise to itself.
That could be one of the most valuable outcomes of the entire transition.
From Systems of Record to Systems of Action
For decades, the enterprise technology stack was built around systems of record. Their purpose was to store authoritative information about customers, assets, employees, work, transactions and financial activity.
Agentic AI moves us toward something different.
It moves us toward systems of action.
The value is no longer simply in recording what happened. It is in understanding what should happen next and executing that decision safely across the organization.
But the move from record to action is not trivial. The more authority we give software, the more precisely we need to define the rules around that authority.
This is the part of enterprise AI I find most interesting.
Not whether AI can generate a better prediction or a better recommendation, because it increasingly can.
The harder question is whether the organization can carry that intelligence through ERP, GIS, work management, finance, customer and asset systems without losing its meaning somewhere along the way.
The Next Competitive Advantage May Be Operational Confidence
The current AI race is understandably focused on capability. Better models, better agents, more tools, more autonomy.
But capability may not be where the real competitive advantage settles.
The organizations that move fastest may eventually be the ones that can trust their own operating logic.
They will know which system has authority, which state is valid, which rules control timing, and what should happen when the same business event appears differently across several systems. They will be able to let AI act because they have made the organization’s own logic explicit enough to govern that action.
That is where the conversation becomes especially relevant to the work we do at Spatial DNA.
We have spent years working in the space between enterprise systems, where work changes state, where business meaning shifts, where operational decisions become financial facts, and where organizations often depend on people to keep the process coherent.
AI agents do not make that space disappear.
They make governing it more important.
Before an enterprise can confidently become more autonomous, it may first have to become more explicit about how it actually works.
And when that happens, many organizations may discover that their “source of truth” was never really a box in an architecture diagram.
It was the set of rules that determined which truth mattered, when it mattered, and what the organization was allowed to do next.
That is the operating model.
And in the age of AI agents, it may become the most important thing to get right.