The IBM i AI readiness framework — adopted by COMMON as the community standard for measuring where organizations stand in the agentic transition.
Every signal in the agentic transition belongs to one of three domains. Not because technology, organizations, and people are separate problems — they aren't — but because they fail in different ways, on different timelines, and require different responses.
HOT was developed by Reggie Britt as the organizing framework for the COMMON AI Initiative — the IBM i community's structured response to the agentic transition. Adopted by COMMON as its community readiness standard in 2026, HOT is the lens the COMMON AI Readiness Index uses to measure where IBM i organizations stand: Human capability, Organizational design, and Technology readiness.
When you see H · O · T attached to a domain or a signal, it tells you which layer of the transition that signal is primarily testing.
Individual capability. What people know, how they reason, and the tacit knowledge that can't be automated because it was never fully articulated.
Governance, structure, accountability. The layer between individual capability and production technology. Where oversight lives — or doesn't.
Tools, infrastructure, protocols, platforms. The most visible layer of the transition — and the one organizations invest in before the first two are ready.
The Human dimension is about individual capability: what people know, how they reason, what judgment they bring to the work. In the agentic economy, the relevant human questions are about knowledge — specifically, the tacit knowledge that can't be automated away because it was never fully articulated in the first place.
For IBM i practitioners, H signals often look like this: the 30-year developer who knows why a particular program works the way it does, even though the documentation doesn't say. The analyst who can describe a business rule in the terms the platform actually uses. The operator who recognizes when an automated process is producing outputs that are technically correct but operationally wrong.
The Knowledge Distance Problem — the gap between what an individual knows and what an organization can actually deploy — is fundamentally an H problem. When AI moves faster than human capability can adapt, H is where organizations break first.
What do your people know? How is that knowledge distributed? What happens when the person who holds it leaves — or when an agent that doesn't hold it starts making decisions in their domain?
The Organizational dimension is about governance, structure, process, and accountability. It's the layer between individual human capability and the technology that runs in production. Organizations fail at the agentic transition not because the technology doesn't work, but because no one decided who is accountable when it does something unexpected.
The IBM Institute for Business Value put a number on it in May 2026: 82% of C-suite executives say functional silos are blocking the value AI delivers. Fragmentation — not talent, not AI maturity, not platform readiness — is the primary constraint. It is the dimension where the gap between IBM i organizations' technology readiness and their organizational readiness is most consistently visible.
O signals surface in governance questions: Who authorized this agent to take this action? What does the audit trail look like when an agent makes a decision that affects a customer? How does your change management process handle a deployment that updates itself? These aren't technology questions. They're organizational design questions.
IBM i environments have historically strong O foundations — object-level access controls, journal-based audit trails, formal change management. The challenge in the agentic transition is extending those structures to cover agent identity and agent actions, not rebuilding them from scratch.
Who governs the agentic layer? Who is accountable for what agents do? What does oversight look like when the system is designed to operate without continuous human intervention?
The Technology dimension is about tools, infrastructure, protocols, and platforms. It's the most visible layer of the agentic transition and the one that gets the most attention — which is part of why organizations underinvest in H and O until something breaks.
T signals in the IBM i context include the arrival of MCP as the connectivity protocol, IBM Bob as the agentic coding tool, PowerVS as the cloud infrastructure path, and LangGraph as the orchestration framework. These are real and important signals. The error is treating them as the only signals, or treating T readiness as a proxy for overall readiness.
The HAI 2026 finding that 88% of agent pilots fail to reach production is a T signal with an O cause. The technology worked. The governance architecture didn't.
What's the right tool for this problem? What protocol does this system use? What does the infrastructure need to look like for this agent to operate reliably at scale?
HOT is not a ranking — all three dimensions matter. But the order of the letters is intentional.
In the agentic transition, the Human question comes first: what knowledge does your organization hold, and where is it at risk of becoming distance rather than decision? The Organizational question runs alongside: who governs the agentic layer, who is accountable for what agents do, and what does the audit trail look like? The Technology question is third — not because it matters less, but because it serves the first two.
Organizations that lead with T — that buy the tooling before answering the H and O questions — are the 88% in the failure dataset.
When you see a domain or signal classified as T · H, it's primarily a technology problem with meaningful human implications. When you see O · T · H, the organizational design question is load-bearing — technology and human factors follow from it. The classification tells you where to start, and where most organizations are making the mistake of starting somewhere else.
Every domain in the Agentic Tech Map carries a HOT classification. Every signal in the Signal Stack is tagged by dimension. The classification isn't taxonomy for its own sake — it's a sequencing tool. Know which dimension a challenge primarily lives in, and you know where to start.
Signal4i publishes at the intersection of the IBM i platform and the agentic economy. HOT is the framework that keeps that coverage from becoming a vendor catalog. The technology is visible. The human and organizational dimensions are where the real work is.