Coherence is produced, not imposed
Architecture often tries to treat coherence as an imposed condition.
A target architecture is approved. A governance structure is established. A capability map is maintained. A repository is populated. A standard is published. A process is described. A decision forum is created.
These things may be useful. They may even be necessary.
But they do not produce coherence by themselves.
A design can describe how work should hold together without making it hold in practice. A governance body can approve an arrangement without resolving how responsibilities cross boundaries. A repository can contain descriptions that no longer match embodied practice. A standard can reduce variation while leaving meaning, timing, and consequence unresolved.
Coherence is not a property that architecture installs into the enterprise.
It is a condition that re-emerges through participation. Agents interpret, coordinate, contest, repair, adapt, and act across grounded relations. They carry promises from one practice into another. They recognise when a rule no longer fits a situation. They decide which document is authoritative. They notice when status is visible but not trusted. They repair the gap between what has been described and what is actually happening.
The enterprise becomes coherent when agents can understand what they are part of, act on that understanding, and adapt when conditions change.
Participation is not stakeholder involvement
Participation is easily misunderstood.
It is not merely consultation. It is not asking stakeholders for input. It is not collaboration as a soft value. It is not buy-in after the architecture has already been formed.
Participation is the situated contribution of agents to the relations through which enterprise work becomes understandable, coordinated, constrained, adapted, and acted upon.
A sales person participates when a customer promise is made in a way that delivery can actually honour. A planner participates when production capacity, material availability, and delivery commitments are reconciled. A service team participates when it interprets a customer situation not only as a case, but as a consequence of promises, products, contracts, and prior decisions. A regulator participates when an obligation changes what evidence must be kept, what decisions can be made, and what actions are permitted.
Participation also happens in less visible ways. Experienced people translate between meanings. Local coordinators repair gaps between routines. Managers interpret status against what they know of the work. Practitioners maintain distinctions that formal descriptions collapse.
This is not secondary to architecture. It is not soft. It is structural.
Relations do not hold themselves
The previous coherence articles established that coherence lives in relations, not isolated entities. Dependencies, obligations, meanings, practices, flows, constraints, and responsibilities bring parts of enterprise reality together.
But relations do not hold themselves.
Agents hold them.
A dependency must be recognised. An obligation must be honoured. A meaning must be interpreted. A responsibility must be owned. A timing relation must fit the rhythm of decisions and work. A manifestation must be understood as intended, actual, authoritative, provisional, local, obsolete, explicit, embedded, or embodied.
A promise may move from sales into delivery without remaining coherent. A responsibility may cross a boundary without being owned. A rule may be enforced without still being valid. A document may be available without being authoritative. A machine event may trigger action without being correctly interpreted.
The relation exists.
The enterprise still needs participation to make it meaningful, actionable, and adaptive. Architecture cannot participate on behalf of the enterprise; it can only shape the conditions in which participation becomes capable of producing coherence.
Participation can also fragment
Participation is necessary for coherence, but not all participation creates coherence.
Agents can participate in ways that preserve local coherence while weakening enterprise coherence.
A sales team may protect a customer promise that production cannot fulfil. A service team may repair a customer situation without changing the product understanding, delivery assumption, or obligation that caused the situation. A local practice may use a workaround that keeps work moving while hiding the fact that the explicit description, embedded arrangement, and embodied practice no longer agree.
This risk is not limited to human agents. A machine event may trigger action without being correctly interpreted. An embedded rule may enforce a decision whose organisational meaning has changed. An AI-shaped agent may summarise connected sources without knowing whether they are authoritative, obsolete, local, intended, actual, or mutually consistent.
The same applies to formal architectural participation. A governance body may impose intent without grounding it in operational reality. An architect may produce models that are internally consistent but unusable in the situations where work, decisions, obligations, and consequences appear. A manager may treat visible status as reliable when the people doing the work know that it no longer matches reality.
Some participation repairs fragmentation. Some hides it. Some accelerates it.
The architectural question is whether participation is anchored, grounded, and intelligible enough to hold across boundaries.
Human and automated agents participate differently
Modern enterprise action is not produced by human agents alone.
Customers, suppliers, partners, regulators, organisational units, systems, machines, embedded rules, automated routines, and AI-shaped agents all participate in what the enterprise does.
They do not participate in the same way.
Some agents interpret. Some decide. Some approve. Some carry obligations. Some enforce rules. Some move materials. Some produce events. Some calculate. Some classify. Some recommend. Some monitor. Some execute established routines. Some adapt when the situation no longer fits the description.
Human participation involves judgement, responsibility, accountability, and situated understanding. Organisational participation involves roles, mandates, authority, practices, and commitments. Material and technical participation may involve machine behaviour, event production, physical movement, embedded constraints, or operational capacity.
The practical question is simple: if something contributes to how enterprise work is interpreted, constrained, routed, decided, adapted, or acted upon, then its participation matters for coherence.
Architecture therefore needs to account for participation across human, organisational, material, technical, and automated agents.
Not because all agents are the same.
Because their differences shape whether enterprise action can hold together.
The two-eyed condition
Architecture often sees from the producer’s perspective.
It sees the design, the model, the repository, the governance structure, the decision forum, the intended arrangement.
That perspective matters.
But coherence also requires the perspective of those who must act within what has been designed.
The person carrying a customer promise sees something the target architecture does not see. The operator responding to a machine event sees timing and consequence differently from the dashboard. The customer experiences whether the enterprise action actually holds together.
Coherence that holds across boundaries requires both eyes.
One eye sees from the perspective of design, governance, and representation. The other sees from the perspective of situated action, interpretation, responsibility, and adaptation.
Participation makes this two-eyed condition possible because it exposes how architectural intentions meet enterprise reality.
AI-shaped participation must be treated carefully
AI and other automated agents can participate in enterprise action without producing coherence. They can retrieve, classify, summarise, recommend, monitor, trigger, and enforce. But coherence requires more than participation as activity. It requires participation that is anchored in practice, grounded in relevant dependencies, intelligible to the agents affected, and accountable within the enterprise. AI-shaped participation may strengthen coherence when those conditions are present. It may also accelerate incoherence when it acts on divergent meanings, obsolete rules, weak grounding, unclear responsibilities, inconsistent manifestations, or locally optimised objectives.
What architecture contributes
Architecture cannot mandate coherence.
It can create the conditions in which participation sustains it.
That contribution requires making enterprise realities intelligible to the agents who must act with them: anchoring knowledge in the practices where it is used, grounding knowledge in the dependencies that give it validity, and exposing the relations that hold enterprise realities together across boundaries.
It also requires making status visible. Which knowledge is intended? Which is actual? Which is authoritative? Which is provisional? Which is local? Which is obsolete? Which is explicit in documents, embedded in systems and rules, or embodied in practice?
Without those distinctions, participation becomes guesswork. With them, agents can better understand what they are part of, what their actions depend on, and where coordination is required.
Architecture does not produce coherence by standing above the enterprise.
It contributes when it helps agents participate more coherently within it.
Where the deeper problem begins
If integration connects the enterprise, participation tests whether those connections can actually hold in practice.
But participation only produces coherence when agents can understand what they are part of, recognise the relations that matter, and act across boundaries without losing grounding.
The architectural challenge is therefore not only to connect, govern, or represent the enterprise more completely. It is to create the conditions in which distributed participation can hold enterprise reality together.
That is where the deeper coherence problem begins.
/Anders W. Tell
Reimagine Architecture through Reimagining Architectural Understanding using Interweaving
