Architecture Is Not Deployment
Vol. 3 closed with a precise statement: the IBM i agentic stack exists, all four layers are available today, and what's missing is not technology. What's missing is the posture — the organizational decision to treat this moment as the moment it is.
That framing was right as far as it went. But it left the hardest question unanswered: what actually happens in the space between naming the architecture and running agents in production?
That space has a structure. It is not random. It is not simply "organizational friction" or "change management." It is a specific, measurable gap — and Harvard and Stanford just ran the experiment that named it precisely.
The variable that determines whether AI deployment succeeds or fails at the execution layer is not the model, the prompt, or the compute. It is the distance between the people doing the work and the domain the AI is being asked to operate in.
This is the Knowledge Distance Problem. KD is the binding constraint at the execution layer. It is why 94% of organizations have adopted AI and 6% have bottom-line impact. It is why the architecture gets named and the agents don't get deployed. And for IBM i practitioners, it is the specific variable that places them structurally ahead of nearly every other enterprise technology group — before they've written a single line of agent code.
The GenAI Wall — Measured Precisely
Researchers from Harvard Business School, Stanford University, and the Stanford Digital Economy Lab ran a controlled field experiment inside a major professional services firm. Three groups — domain insiders, adjacent professionals, and distant outsiders — were given identical tasks with identical AI tools.
Performance gap between groups on conceptualization tasks. For structuring, outlining, and ideating, AI equalized performance completely. Every group performed at specialist level. The gap disappeared entirely.
Then the tasks shifted to execution — writing, building, producing. The results split sharply. Domain insiders and adjacent professionals matched. Distant outsiders consistently underperformed. In many cases they made outputs measurably worse than if they had worked without AI at all.
The researchers named this the GenAI Wall Effect: a threshold defined not by the technology but by the human's distance from the execution domain, beyond which AI cannot bridge the gap.
This is the execution gap. Not a training deficit. Not a tooling deficit. A proximity deficit. The people closest to the domain can execute with AI. The people furthest from it cannot — and their attempts actively degrade output quality.
Six Root Causes That Collapse to One
Every standard explanation for why AI deployments fail at the execution layer is a symptom. The root cause is always Knowledge Distance.
of GenAI pilots fail to reach production scale. KD is the root cause operating underneath every reported reason — skills, costs, tools, complexity. Each is a KD gap with a different label on it.
KD at Autonomous Scale
KD was always present in AI deployments. Agentic AI makes it dangerous at scale. The distinction is precise.
When AI generates a document or a summary, a human reviews it before anything happens. The KD gap shows up as review time, rework, or a poor output that gets corrected. Manageable.
When AI agents execute decisions autonomously — pricing, routing, approvals, workflow orchestration — the KD gap shows up as compounding errors at autonomous scale, without a human in the evaluation loop to catch the drift.
AI-related security incidents are up 55% year-over-year. The Foundation Model Transparency Index dropped from 58 to 40. The incidents aren't technology failures. They are KD failures operating at agentic speed — systems executing in domains they don't understand, without humans close enough to the domain to catch the drift.
This is the governance gap. And it is the gap Vol. 5 proves cannot be closed sequentially — technology transformation, human fluency, and organizational redesign must run simultaneously, because each one is a precondition for the others to hold at agentic scale.
Structurally on the Right Side
The Harvard/Stanford finding has a specific application for IBM i practitioners that most are underestimating.
IBM i organizations hold something most enterprises are desperately trying to acquire: 30 to 40 years of encoded domain expertise in production systems. The business logic in RPG programs, the data governance baked into Db2, the workflow intelligence in the job stream and subsystem architecture — all of it is proximity, encoded.
That is the specific variable the experiment identified as the determinant of AI output quality at the execution layer.
IBM i practitioners don't need to acquire domain knowledge. They are the domain knowledge. The Knowledge Distance Problem — the binding constraint at the AI execution layer — is the specific gap they close by definition.
The execution signal is not that IBM i is "ready for AI." It is that the people running IBM i are structurally positioned on the right side of the variable that determines whether AI deployments succeed or fail — before anyone else in their industry recognized it as a variable.
Vol. 5 picks up from here: why the three tracks required to move from this position to the Human Agentic state — technology, human, organizational — cannot run sequentially, and what happens to organizations that try.