Five issues have built the case.

Vol. 1 asked the question. Vol. 2 returned the evidence. Vol. 3 named the architecture. Vol. 4 measured the execution gap. Vol. 5 proved that running two transformations sequentially is now structurally fatal.

Every issue has ended with the same implicit question from the practitioner reading it: *Fine. But what do I actually do?*

Vol. 6 answers it.

---

**The four words I hear most often from tech leaders:**

*”We’re being careful.”*

I understand the instinct. You are responsible for systems that process $1M+ transactions daily. You cannot afford a production failure. Caution is not incompetence — it is experience.

But I want to be precise about what “being careful” is not.

It is not posture.

Posture is not a feeling of appropriate caution. It is not a team meeting about AI readiness. It is not a vendor evaluation that ends with no decision. It is not a pilot that never reaches production.

**Posture is architecture.** It is four interlocking layers, each of which must be built deliberately, and none of which assembles itself.

---

## The Four Layers

**Governance.** The measurement framework that allows you to evaluate what an agent is doing in your environment. For IBM i organizations, this starts with one question: how do you define correctness for a system that contains forty years of business logic not documented anywhere except the RPG source code?

EvoScore is the answer that has emerged from production deployments — correctness measured by business-logic fidelity, not just compilation or test coverage. The governance layer runs before deployment, at every production boundary crossing, and continuously in production. Without it, you are not being careful. You are hoping.

Signal 06 documented this directly: 75%+ of AI-generated code regresses within eight months of production deployment. The organizations that found that out from their own production data were not unlucky. They were ungoverned.

---

**Human capital.** The knowledge transfer problem IBM i organizations have been living for fifteen years is not solved by the arrival of AI agents. It is made more urgent by it.

The senior practitioner who understands the business logic is not replaceable by the agent. They are the person the agent needs to function correctly. The human capital layer is the documented transfer of that knowledge — not to a successor human, but to the agent architecture itself. Business logic documentation. Decision trees. Escalation criteria. The institutional knowledge that has lived in one person’s head for thirty years needs to live somewhere the agent can reach it.

The tandem thesis from Vol. 5 applies here directly. You cannot finish documenting knowledge before you start building agents. The two tracks must run simultaneously.

---

**Deployment infrastructure.** The production boundary question. What can an agent do without human approval? What triggers review? Who owns the agent’s behavior when it fails?

Most organizations running agents today have never explicitly answered these questions. They are operating without a production boundary — which means they are operating without a governance layer.

Signal 13 put the number on it: 77% of organizations have no committed agentic strategy. That is not caution. That is a policy vacuum.

The deployment infrastructure layer is the written answer to those four questions, applied to your specific environment, and reviewed before the first agent touches production code.

---

**Documented frameworks.** The agent charter. The evaluation cadence. The escalation path. The record that allows a different practitioner — or a different agent — to understand what the first one was authorized to do, and how it was performing against that authorization.

Documented frameworks are not bureaucracy. They are the governance architecture that allows the hierarchy to come down safely.

---

## What the Ratio Tells You

Signal 116 named the destination: Jensen Huang’s 100:1 ratio — 75,000 employees managing 7.5 million agents — is not a projection. It is a current operational reality at Nvidia.

At 100:1, you cannot govern at the action level. You cannot review what each agent did. You govern at the policy level: what agents are authorized to do, what they are prohibited from doing, and what triggers human review.

The organizations that build policy-level governance now are positioned differently at 100:1 than the organizations that wait until the ratio forces the conversation.

For IBM i shops, this is the RPG boundary question: what business-logic changes can an agent make autonomously, and what requires the senior practitioner’s review? That boundary is not set by the technology. It is set by whoever builds the governance layer first.

---

## What Dorsey Just Named

Signal 121 arrived on April 2. Jack Dorsey announced the elimination of middle management layers at Block as a transition to an intelligence-based organizational structure.

This is not a cost-cutting exercise dressed as a vision statement. It is the structural answer to the 100:1 ratio problem. Middle management in the old hierarchy served as the human approval chain. Agents remove the need for the approval chain — but only if you have replaced it with a governance architecture that can do the same work at scale.

Organizations that remove the hierarchy without building the governance layer are not becoming leaner. They are creating the governance void.

The posture blueprint for IBM i is the answer applied to your environment: when you remove the human approval chain from your RPG modernization process, what replaces it? EvoScore. Production boundaries. Agent charters. Documented escalation paths. Those are not bureaucracy. They are what makes the transition safe.

---

## The Blueprint

Posture is not a destination you arrive at. It is an architecture you build, layer by layer, before you need it.

The four layers are not sequential. They are tandem — which is what Vol. 5 established. The governance framework informs the deployment infrastructure. The human capital layer informs the governance framework. The documented frameworks hold all three together.

The organizations in Yang’s 1–3 year window that are building governance layers now are not the ones who were least afraid. They are the ones who understood that caution without architecture is not safety.

It is exposure with better intentions.

---

**Vol. 7 — The Decision Window **

Yang said 1–3 years. What IBM i organizations do in the next 90 days matters more than what they do in the next 3 years. The window is open. Seven issues of signals have documented how long it stays that way.

---

*Signal4i is a practitioner-facing publication tracking AI signals that matter for IBM i organizations. Not predictions. Not vendor positioning. Events that have happened, data that has landed, and what they mean for the organizations running the the IBM i enterprise platform.*

*Published by a CTO who has spent 30 years on the platform — and is watching what’s coming.*

There is a version of the AI transformation story that goes like this: first you modernize the technology, then you train your people, then you redesign the organization. One after another. Manageable. Sequenced. Safe.

That version is wrong.

Not strategically wrong. Not slightly mistimed. Structurally wrong — in a way the data now confirms, and in a way that organizations are discovering too late to recover from at the pace AI is moving.

This is what Signal4i Vol. 5 is about. The tandem thesis. Why the three transformations — technology, human, organizational — cannot run one after another. And why the IBM i practitioner who grasps this is not just better positioned than the one who doesn’t. They are operating in a different competitive category entirely.

---

## The sequential story feels right. The data disagrees.

Most transformation programs are built around sequence because sequence is comfortable. You know where you are. You can manage a milestone. You can tell a board “we’re in Phase 1.”

McKinsey studied what separated organizations that captured AI’s gains from those that didn’t. The finding was not about which tools they chose. It was about when they built readiness.

**Signal #12 — Readiness-Before-Deployment Imperative**

> *McKinsey: winners solved data and system integration before deploying AI tools. Not the most AI tools — the most AI-ready architecture.*

The winners didn’t sequence readiness after deployment. They treated readiness as the precondition. The organizations that deployed AI tools first and planned to “figure out the org stuff later” found themselves in the execution gap — not because the technology failed, but because the organization was never ready to use what the technology could do.

This is not a niche finding. It is the same pattern Signal #7 documents at the population level: 94% of organizations have adopted AI in some form. 44% have secured what they built. 72% have scaled an AI experiment. 33% have governed what they scaled. The gap between adoption and readiness is not closing. It is widening — because the technology keeps moving and the organizations keep sequencing.

**Signal #7 — Readiness Gap Compression**

> *94% adopt AI, 44% secure. 72% scaled, 33% governed. The gap between adoption and readiness is measurable and widening.*

Notice what that data is actually measuring. Every pair — adopt/secure, scale/govern — is a sequencing failure. The organization ran track one before it ran track two. And every time it does, it compounds the gap.

---

## Sequential transformation has a deadline. It has now passed.

For most of the last three years, you could argue that sequencing was acceptable — not optimal, but survivable. The technology wasn’t moving fast enough to make the organizational lag fatal. You could afford to catch up.

That window is closing. Salim Ismail — who built the Exponential Organizations framework and has spent twenty years studying how organizations fail to adapt to exponential change — named the threshold in March 2026.

**Signal #113 — The Organizational Singularity**

> *Salim Ismail publicly named the threshold at which recursive self-improvement in agentic workflows makes human-to-human workflow competition structurally unwinnable. Triggered by Nvidia enterprise agent infrastructure and population-scale agentic adoption.*

The Organizational Singularity is not a prediction. It is a structural threshold — the point at which an organization running AI-native workflows at scale can improve those workflows faster than a human-staffed organization can match through any amount of hiring, training, or reorganization. Once you are on the wrong side of that threshold, catching up is not a matter of effort. It is a matter of physics.

Ismail triggered this signal in response to two things happening simultaneously: Jensen Huang’s declaration at NVIDIA GTC that his internal operating model targets 100 AI agents per employee, and the viral population-scale deployment of autonomous agents in China — bypassing enterprise governance, IT procurement, and readiness infrastructure entirely. Both signals in the same 30-day window.

The Organizational Singularity is what makes sequencing fatal. If your technology transformation is running ahead of your organizational readiness, you are deploying into a structure that cannot absorb what you are deploying. And the recursive improvement loop means the gap between what your technology can do and what your organization is ready to use widens automatically — without any further action on your part.

---

## The penalty for delay is not linear. It compounds.

The Anthropic Economic Index v5, released March 24, 2026, is the most important empirical signal to land in the readiness gap category since the McKinsey data. It is first-party data from 2 million+ conversations. And it documents something that fundamentally changes the stakes of the sequencing question.

**Signal #121 — AI Fluency Compounding Effect**

> *Six or more months of AI experience yields 10% higher task success rate. Each additional year correlates with roughly one additional year of schooling in prompt sophistication. Delay compounds: the readiness gap is not static — it widens exponentially.*

Read that carefully. The gap is not static. The organizations that started earlier are not just ahead — they are compounding their lead at a rate that later starters cannot match through accelerated effort. The fluency curve is self-reinforcing. The practitioner who started in 2024 is not six months ahead of the practitioner who starts today. They are a compound interest curve ahead.

This is what makes the tandem thesis urgent rather than theoretical. If you are sequencing — if you are waiting for the technology track to finish before you start the human track, or waiting for both to finish before you restructure the organization — you are not just behind. You are watching the distance grow while standing still.

The data also contains a counterintuitive finding. Organizations with 80% AI task coverage report minimal gains. Organizations with 30% coverage report transformational results. The difference is not how broadly AI is deployed. It is whether the humans using it have developed the fluency to extract what it can actually do. Breadth without readiness produces noise. Depth with readiness produces transformation.

---

## The destination requires all three tracks. Not one after another.

Jensen Huang’s 100:1 ratio is not a prediction for some other organization. It is his declared operating target for NVIDIA — 75,000 employees, 7.5 million AI agents. The ratio is the destination.

**Signal #116 — Executive Anchoring of Human-Agent Ratio at Scale**

> *Jensen Huang targets 100 AI agents per employee as internal operating aspiration. First CEO-scale ratio declaration. Ratio-based workforce framing moves from analyst speculation to executive benchmark.*

Think about what it takes to reach that destination. You cannot get to 100:1 by modernizing technology and then training people. The ratio requires technology capable of running agents at scale. It requires humans fluent enough to direct, govern, and improve 100 agents each. And it requires an organization structured to operate at that ratio — with decision rights, accountability, and governance architecture that does not exist in any organization built around a 1:1 human-to-work model.

That is three transformations. Running simultaneously. Because each one is a precondition for the others to function.

Technology without human fluency gives you deployed agents that no one knows how to use. Human fluency without organizational redesign gives you capable individuals trapped in a structure that prevents them from operating at ratio. Organizational redesign without technology gives you a skeleton with nothing to run on. All three, or none of it compounds.

---

## What this means for the IBM i practitioner

You have spent your career at the intersection of all three.

You have built, maintained, and evolved the technology layer — not as a vendor implementation, but as an integrated architecture that runs actual business operations. You understand the system at a depth that no consultant walking in with a stack recommendation can replicate.

You have been the human layer. The one who translated between what the system could do and what the business needed. The one who earned the trust of the people whose knowledge had to be encoded into every program you wrote. The FDE role Anthropic invented to close the deployment gap — you have been living it for thirty years.

And you have operated inside the organizational layer. You know how decisions get made, where authority actually sits, which processes are documented and which are tribal, and why every transformation initiative that came before stalled where it did. You are not observing the organization from outside. You are embedded in it.

The tandem thesis does not create a new opportunity for you. It names the opportunity you have always been positioned for. The IBM i practitioner who sees this clearly is not just a modernization resource. They are the synchronization layer — the person who can run all three tracks at once because they have always been running all three at once.

The question is whether you name it before the market names it for you.

---

**Signal4i · Vol. 5 · March 29, 2026**

*Signals featured: #7 · #12 · #113 · #116 · #121*

*Signal Stack v7.5 · 121 signals · 10 categories*

---

*Signal4i is a practitioner-facing publication tracking the AI signals that matter for IBM i organizations. Not predictions. Not vendor positioning. Events that have happened, data that has landed, and what they mean for the organizations running on the IBM i platform.*

There is a version of this moment where the IBM i community spends the next three years watching AI happen to other platforms.

That version is over.

IBM has built the bridge. The stack is named. The tools are available today. And the people best positioned to use them are the ones who already know the business the stack is built to run.

This issue is about the architecture. Not a roadmap. Not a beta. What exists right now, how the layers connect, and why this platform is not behind — it is ahead of where every other enterprise stack is trying to get.

---

## SIGNAL 09 · THE PROTOCOL SIGNAL

### The Bridge Has a Name. It’s Live.

*IBM, October 2025 → 2026 — IBM releases the IBM i MCP Server. Tech preview shipped at TechXchange 2025. Production-ready documentation published. 500 tools targeted for 2026.*

For years, the practical barrier to connecting IBM i to the modern AI ecosystem wasn’t the data or the logic — it was the interface. There was no standard way for an AI agent to reach into a system running RPG and Db2 and call what it needed. Every integration required a custom connector. Every AI experiment required building the plumbing from scratch.

Model Context Protocol changes that. MCP is the tool protocol — the layer that defines what an agent is authorized to access, execute, and observe. Anthropic designed it as a universal standard, what they call a USB-C port for AI applications. Instead of custom connectors for every tool and data source, one protocol. Any agent. Any framework.

IBM shipped the IBM i MCP Server. First released at TechXchange in October 2025, it has since moved to production-ready documentation and active development under an Apache 2.0 open source license. The goal: 500 tools in 2026. SQL Services. CL Commands. System monitoring. Security auditing. All exposed as callable tools to any MCP-compatible agent.

> “Our team has made an initial version of an IBM i MCP server available, and we’ve set a goal to produce at least 500 tools in 2026.”

*— IBM i MCP Server documentation · IBM · 2025–2026*

The supported client list tells you how seriously IBM is taking this: Claude Code, Claude Desktop, VSCode, Cursor, Windsurf, Roo Code, LM Studio, Gemini CLI, Cline. IBM is not picking winners on the client side. They’re building for the whole ecosystem.

The bridge isn’t coming. It’s here. The question is whether your organization walks across it.

---

## SIGNAL 10 · THE API SIGNAL

### Mapepire: The Db2 You Already Have, Now Callable.

*IBM, 2024–2025 — Mapepire ships as IBM’s open-source database access layer for IBM i. Db2 data and business logic exposed over WebSocket connections. No disruption to what’s running. Multiple agentic frameworks confirmed working.*

The fear that stopped most IBM i modernization conversations was legitimate: you can’t touch what’s running. The business depends on it. Any API layer that requires rewriting the core to expose it isn’t a bridge — it’s a migration in disguise.

Mapepire is different. It sits above the Sovereign Core — RPG and Db2 stay exactly as they are. Mapepire makes them callable via WebSocket, optimized for the request-response patterns AI agents actually use. Traditional access methods like ODBC and JDBC weren’t designed for the frequent, short-lived queries that agentic systems require. Mapepire was.

Multiple agentic frameworks are confirmed working with IBM i via Mapepire today: LangChain, Agno, and the MCP protocol itself. BeeAI and CrewAI are in progress. The ecosystem is not locked to a single vendor or approach. The platform is connectable to wherever the agentic world is going — and more frameworks are joining the list.

The IBM i MCP Server requires Mapepire as its foundation. They are not separate tools — they are the two layers of the same bridge. Mapepire handles the database connectivity. MCP handles the agent interface. Together they are the integration layer the IBM i community has been waiting for.

> “Mapepire bridges the gap by providing a modern, WebSocket-based SQL query interface that’s optimized for the request/response patterns of AI agents and MCP tools.”

*— IBM i MCP Server documentation · IBM · 2025–2026*

Seiden Group, one of the IBM i community’s most respected independent consultancies, announced production support for Mapepire in July 2025 — noting that many developers are already relying on it as the back-end to the Db2 for i extension for VS Code, sometimes without realizing it. That is what mainstream adoption looks like: it arrives quietly, then all at once.

The data didn’t have to move. The bridge came to it.

---

## SIGNAL 11 · THE STACK SIGNAL

### The Four Layers Are Named. All of Them Exist Today.

*IBM · Open Source and AI — The complete IBM i agentic stack specified and demonstrated. Four layers. Each named. Each available now.*

The conversation about modernizing IBM i used to require an act of imagination. What would the architecture look like? What would it cost to build? How long would it take?

That conversation is over. The stack is specified. Here are the four layers, from the ground up:

**Layer 1 — The Sovereign Core.** RPG and Db2. Untouched. Thirty years of business logic, transaction integrity, and operational reliability. This is the moat. It doesn’t move. No competitor can buy it. No migration preserves it.

**Layer 2 — The API Layer.** Mapepire. Node.js on PASE. The Sovereign Core becomes callable. Business logic and Db2 data exposed over modern interfaces without disturbing production operations. The bridge runs alongside the system — not through it.

**Layer 3 — The Agentic Layer.** Python orchestration — LangChain or Agno. An Orchestrator Agent that routes, plans, and reasons. Specialist agents that execute. The MCP protocol bridge connects agents to the tools they’re authorized to use. The overnight batch job becomes an observable, auditable, agent-driven process. The Think → Act → Observe loop runs against your own data, in your own environment, under your own governance.

**Layer 4 — The Modern Surface.** React or Next.js. Business users interact with the system through an interface that speaks their language. Configuration in hours, not tickets. System behavior changes without requiring a development cycle. The prompt is the interface.

> “Each layer has a distinct responsibility. MCP is the protocol bridge, not the orchestrator. Nothing bleeds across the boundary.”

*— IBM i Agentic Architecture · IBM · 2025–2026*

This is not a future state. It is the current state for organizations that have made the decision to move. The stack is here. The question is the decision.

---

## SIGNAL 12 · THE NATIVE SIGNAL

### The Stack Is Still Expanding.

*IBM, 2025 — IBM develops an experimental SDK that lets RPG programs call AI models directly via embedded SQL. No new language. No new architecture. One SQL function connects existing business logic to any LLM endpoint. Currently in active development.*

The four-layer stack above is deployable today. But the ecosystem around it is still growing — and the signal worth watching is what happens when the integration moves from the outside in.

IBM is developing an experimental SDK that would let developers call AI models directly from Db2 for i — and by extension from RPG via embedded SQL. The concept: a SQL function call connects existing business logic to any LLM endpoint. IBM watsonx, Ollama, any OpenAI-compatible solution, on-premise inference options — all reachable from inside the RPG codebase itself. No new language. No new architecture layer. One function call.

The SDK is currently documented as experimental and not yet production-ready. IBM’s own GitHub describes it as “in bringup state.” But the direction is clear, and the implication matters:

If this ships, existing RPG code participates in AI workflows without a rewrite. The 30 years of business logic encoded in that codebase doesn’t have to be migrated, translated, or replaced to become part of an agentic system. It calls the agent. The agent calls it back.

The organizations that understand the four-layer stack now will be best positioned to extend it when this capability arrives. The ones that wait for the complete picture will be starting from scratch at that point.

The core stack is here. The ecosystem is still expanding. This is the signal that tells you both things are true.

---

## What This Means

Four signals. One conclusion.

The IBM i MCP Server is live and in active development. Mapepire is the foundation multiple frameworks already run on. The four-layer stack is specified and deployable today. And IBM is building the next layer — native AI calls from RPG — with production readiness on the horizon.

The bridge is built. The stack is named. The tools are available.

What’s missing is not technology. It is not the platform. It is not the people.

What’s missing is the posture. The organizational decision to treat this as the moment it is — and to move before someone else names what you have and builds on top of it without you.

---

## Vol. 4 — The Execution Signal

Architecture doesn’t deploy itself.

The gap between a named stack and a running agent is where most organizations stall. The technology is ready. The platform is ready. And yet 95% of GenAI pilots are failing. 26% of scaled experiments reach production. 77% of organizations have no committed agentic AI strategy.

That gap has a name now too: the Forward Deployed Engineer. The market has begun quantifying the distance between AI architecture and AI deployment — and pricing it accordingly. Vol. 4 is about what the execution gap actually looks like, what closes it, and why the IBM i practitioner is already holding the most important piece.

Next issue: The Execution Signal.

Vol. 1 asked: *The technology has arrived. Is your organization ready?*

Vol. 2 is the data coming back.

In the six weeks since that question was published, four signals landed that shift the frame from prediction to evidence. The February jobs report. A research paper that measured AI agents across 233-day production timelines and found 75% regression rates. Andrew Yang at the Abundance Summit naming a 1–3 year window and calling it the most urgent policy moment of his career. And a structural finding about the knowledge pipeline that IBM i practitioners have been watching erode for a decade — now accelerating.

These are not projections. They are readings. The experiment has been running. The data is coming in.

Here is what the data says.

---

## Signal 05 — The Labor Signal

### The Posture Gap Made Visible

**February 2026:** The U.S. economy loses 92,000 jobs against a consensus forecast of +59,000. A miss of 151,000 in a single month.

The coverage split immediately — AI displacement versus federal cuts versus macro noise. The debate about which cause dominates misses the more useful observation: the organizations shedding workers are not the ones that moved too slow. They are the ones that moved without a posture.

IBM i shops have been called “behind” on AI adoption for three years. This signal reframes that characterization entirely.

The organizations that deployed AI at speed — that scaled without governing, that adopted without building the readiness infrastructure to sustain adoption — are the ones appearing in the February data. They ran the experiment. The results are in the labor market now.

IBM i practitioners are not behind. They have time. Not much, but some. The question is not whether to move — the question is what posture to build before the window closes.

The platform is not the liability. Deploying AI agents at speed into the platform that runs half the world’s financial transactions, without the governance architecture to sustain them, is the liability.

---

## Signal 06 — The Governance Signal

### Long-Horizon Governance Collapse

**March 4, 2026:** Researchers from Alibaba Group and Sun Yat-sen University publish SWE-CI — the first AI coding benchmark built on real production codebases across 233-day, 71-commit timelines.

Most models achieve a zero-regression rate below 0.25.

Read that again. In more than 75% of cases, AI agents that pass standard coding benchmarks introduce regressions when they maintain real production code over 8 months of evolution.

IBM i practitioners understand this signal in their bones. There is a difference between “it passed the test” and “it held up over time.” Every practitioner who has maintained RPG code across decades of business requirement changes understands exactly what SWE-CI is measuring — and exactly why a benchmark that only measured point-in-time correctness was never telling the full story.

The paper introduces a metric called EvoScore: the extent to which an AI agent can support the *future advancement* of code, not just its current functional state. This is the first benchmark metric that captures what IBM i organizations actually need from an AI coding assistant. Not a demo. Not a one-shot solution. Sustained maintainability across the evolution of a production codebase.

The failure mode this signal documents brackets with a signal from Vol. 1: the CENTCOM same-day AI deployment. CENTCOM showed governance void at the moment of adoption — capability deployed in hours before policy caught up. SWE-CI shows governance void at the maintenance horizon — capability that passes initial tests, then degrades real codebases over 8 months when the governance infrastructure to sustain it does not exist.

Both failure modes are operational hazards, not theoretical risks. Both are now empirically documented and datable.

IBM i shops considering AI-assisted modernization have a sharper question to ask: not whether the agent can write RPG or CL, but whether it can maintain the codebase 8 months after the demo. SWE-CI is the first benchmark that can answer that question. The answer, for most models today, is no.

The platform is not the problem. Deploying agents without the governance posture to sustain them is the problem.

---

## Signal 07 — The Human Signal

### The Pulled Rung

**March 8, 2026:** At the Abundance Summit, Andrew Yang documents three simultaneous instances of the same structural event across industries: the elimination of the knowledge worker on-ramp.

Instance one: A large private equity firm opens a company-wide meeting with a single slide, first topic: *”We don’t need associates anymore.”* Entry-level finance roles — the aspiration of a generation of business graduates — eliminated not for performance reasons but as a structural operating model update.

Instance two: At Yang’s own company, the CTO cancels a hiring process mid-stream. A role had been opened, candidates interviewed, offers prepared. Then a capability update in available tooling changed the math. The role did not become less necessary. The human performing it did.

Instance three: Block cuts 4,000+ employees. Stock jumps 24%. Wall Street rewards the subtraction. A tech CEO tells Yang off the record: his plan is 15% cuts now, 20% two years later, 20% after that. “I take him at his word. Especially after the Block example.”

The structural consequence Yang names: the workforce has shifted from pyramids to columns. Three junior engineers per senior engineer enabled training, mentorship, and the accumulation of institutional knowledge across generations. The column model — one senior, one junior, maybe — eliminates the developmental pipeline. The next cohort of senior talent does not form.

IBM i practitioners know this story. It has been running on the platform for fifteen years. Senior practitioners aging out. Junior practitioners not entering in sufficient numbers. The knowledge transfer problem is not new — but the agentic acceleration is making it acute.

Here is the signal beneath the signal: AI agents cannot replace what IBM i practitioners carry. The decades of business logic, the organizational context, the domain specificity accumulated across thirty years of production maintenance — no model was trained on it. It lives in people. And the column model is eliminating the pipeline that would transfer it to the next generation before the transfer happens.

Yang’s summary: *”If you’re a young person, you never make it into one of these environments to get trained, to learn, to develop, to ascend. Steps three and four are disappearing.”*

For IBM i organizations, the urgency is doubled: the talent pipeline problem predates agentic AI, and agentic AI is accelerating it.

---

## Signal 08 — The Workforce Signal

### Social Contract Rupture Threshold

**March 8, 2026:** Also at the Abundance Summit, Yang names a datable cultural threshold.

A healthcare CEO is assassinated on a New York City street. The perpetrator becomes a folk hero across large segments of online culture. Yang’s framing: *”Young people now regard a lot of successful people as bad. Anyone who’s done well must have stepped on people or done something malignant.”* He calls this *”the foundation cracking.”*

He declares a 1–3 year window requiring policy intervention — UBI as a bridge, Universal Basic Services as the medium-term build, Universal High Income as the destination. He says he would take that intervention *”a hundred times out of a hundred”* — meaning even the optimistic scenario requires action that is not currently being taken.

Washington, Yang observes, operates on a multi-decade tape delay. Legislators in their 70s and 80s are regulating technology accelerating faster than they can comprehend. What was previously institutional lag is now, in his framing, catastrophic.

Signal 08 is not a macro observation filed under “things IBM i shops cannot control.” It is the environment IBM i organizations are navigating — and the IBM i platform sits at the center of the institutions this signal is about.

Financial services. Insurance. Healthcare. Manufacturing. These are the sectors running on IBM i. These are also the sectors at the center of the displacement story Yang is describing. The organizations running this infrastructure that can demonstrate governance posture — that can show they are managing the technology rather than being managed by it — are positioned differently in the window Yang is naming than the organizations that cannot make that case.

The posture question is not only operational. It is the question of what kind of organization you are building in a period when the answer to that question has consequences beyond the balance sheet.

---

## The Through-Line

Four signals. One observation: the experiment has been running, and the data is coming back with a consistent finding.

The February jobs report is the labor market reading on what happens when deployment outruns governance. The SWE-CI paper is the technical reading on what 75%+ regression rates look like across 8-month production timelines. The Pulled Rung is the human capital reading on what column-model organizations do to the knowledge pipeline. The Social Contract Rupture Threshold is the cultural reading on where this all lands if the governance posture problem is not addressed.

IBM i organizations did not create this environment. But they are operating inside it, running infrastructure that sits at the center of the institutions it is stress-testing.

The platform is not the problem. The platform is exactly what the agentic economy needs: proven, stable, transactionally reliable, carrying decades of business logic that no greenfield AI build can replicate.

The question is whether the organizations running it build the posture to match.

That window is open. The signals in this issue are telling you how long it stays that way.

Subscribe now