Research & community

THE CLIMB: Earning AI the Right to Act

AI agents act: they send messages, change records, and commit decisions. Before an agent earns that right, the layers underneath must earn trust in order. Know what data you have and who answers for it. Turn it into numbers you can defend. Agree on one meaning per term. Let the agent reason only with context it may see. THE CLIMB is that order, five layers with governance as the mortar in every seam. Skip a layer and the agent above it acts on guesses.

Governance runs through every layer, not just the base.

In brief

The key idea

AI agents act: they send messages, change records, and commit decisions. Before an agent earns that right, the layers underneath must earn trust in order. Know what data you have and who answers for it. Turn it into numbers you can defend. Agree on one meaning per term. Let the agent reason only with context it may see. THE CLIMB is that order, five layers with governance as the mortar in every seam. Skip a layer and the agent above it acts on guesses.

TL;DR

AI agents act: they send messages, change records, and commit decisions. Before an agent earns that right, the layers underneath must earn trust in order. Know what data you have and who answers for it. Turn it into numbers you can defend. Agree on one meaning per term. Let the agent reason only with context it may see. THE CLIMB is that order, five layers with governance as the mortar in every seam. Skip a layer and the agent above it acts on guesses.

The climb: why AI's right to act is earned, not granted

A demo shows the top of the pyramid, an agent answering a question, filing a ticket, or placing an order on its own. It hides the climb underneath. Every action rests on data, definitions, and permissions built layer by layer. Solid layers make the action trustworthy. Missing layers make it a gamble with a confident tone.

THE CLIMB makes the order explicit: Foundation, Transformation, Semantic, Intelligence, then AI, each layer earning the next. Governance does not sit at the bottom or get bolted on at the end. It runs through every layer, like mortar between bricks.

The problem: agents on top of a broken foundation

An agent reasons over whatever data it can reach. If that data is unclassified, unowned, and untraced, the agent's confident answer is a guess dressed up as a fact. It fills gaps with whatever looks plausible.

This is not rare. A 2023 survey by Monte Carlo and Wakefield Research of 200 data professionals found organizations averaged 67 data incidents per month, taking 15 hours on average to resolve each one. Each incident is data underneath a decision that was wrong, late, or unexplained. Put an agent on top of that foundation and it will act on the same bad data, faster and at greater scale.

Foundation: know what you have, and who answers for it

The first layer is an inventory. Know every dataset you hold, classify it, name an owner, and trace where it came from and what changed it.

Classification means knowing what a dataset contains and how sensitive it is. Ownership means a named person answers for it, not a team inbox nobody reads. Lineage means following a number back to its source. None of this is glamorous. All of it makes the layers above possible. That is the Data tier: raw facts, recorded and accounted for first.

Transformation: numbers you can defend

Raw facts become information in pipelines that add structure, context, and checks.

A data contract is an agreement about what a dataset promises: its shape, freshness, and quality. The Open Data Contract Standard from the Linux Foundation gives teams a shared way to write these promises down.

A quality gate is a check that stops bad data before it flows downstream. If the data fails the check, it does not reach the dashboard, the report, or the agent.

A number you can defend is one you can trace: show the pipeline it came through, the contract it met, and the checks it passed. That is the Information tier: data organized and given context, so it means something.

Semantic: one answer per question, everywhere

The goal is simple to state and hard to achieve: one definition per business term, used everywhere. Ask for revenue, churn, or headcount, and every tool, report, and agent gives the same answer.

Forrester research, cited by Atlan, found 61 percent of organizations run four or more business intelligence platforms. Each can carry its own definition of the same term, so the same question gets different answers depending on where it is asked. That drift is what the Semantic layer exists to end.

A glossary alone does not do it. What turns shared definitions into knowledge is shared understanding, the experience and interpretation baked into the definitions, so the whole organization means the same thing by the same word. The mechanism is a semantic layer, one place where definitions live, implemented in tools such as the dbt Semantic Layer, Looker, and the Power BI model layer.

Intelligence: reasoning with your context

This is where reasoning happens. The agent works with your context, your definitions, your history, your rules. It reasons about your business, inside the boundaries the lower layers set.

The layer spans two stages of understanding. Reasoning with context is knowledge: patterns, interpretation, and what things mean. Deciding which knowledge applies when is wisdom: judgment about the right response in a specific situation. Intelligence sits across both.

Access is the control that matters here. The agent reasons only with the data and context it is allowed to see. Who may reason, and with what, is decided here, not at the top.

AI: the capstone, and why it sits last

AI is the capstone because it acts: it sends, changes, commits, and orders. Everything below it exists to make those actions safe.

Autonomy is earned in stages: recommendations first, approved actions next, wider only on evidence the narrower actions were right. That is the standard in the NIST AI Risk Management Framework and OWASP guidance on excessive agency, where an agent given more power than its task needs becomes a risk in itself.

Gartner forecasts that 40 percent of enterprises will demote or decommission autonomous agents by 2027 over governance gaps. That is a forecast, not a fact, but the direction is plain: agents without governance underneath them do not survive contact with real operations.

Governance: the mortar in every seam

Governance is the mortar, not the base and not the bolt-on. Other models put governance at the bottom, as the base layer of the pyramid. THE CLIMB runs it through every layer instead.

At the Foundation, classification, ownership, and lineage. At Transformation, contracts and quality gates. At Semantic, agreed definitions with no drift. At Intelligence, access: who and what may reason. At AI, the list of actions the agent may take, and the approvals required for the rest.

A stack without mortar looks fine until something pushes on it, then it falls apart layer by layer. Governance in every seam keeps the climb standing when the pressure comes.

The ITIL DIKW map: what lines up, and where the climb goes further

The climb maps onto a much older idea, DIKW, the progression from Data to Information to Knowledge to Wisdom. The idea is commonly traced to Russell Ackoff's 1989 paper "From Data to Wisdom." Ackoff's original had five tiers, with understanding between knowledge and wisdom. ITIL 4 references DIKW in its Knowledge Management practice, but ITIL did not invent it.

The mapping:

  • Foundation is Data: raw facts, inventoried and owned.
  • Transformation is Information: data with structure, context, and validation.
  • Semantic is Knowledge: shared definitions carrying shared understanding.
  • Intelligence spans Knowledge and Wisdom: reasoning with context, and deciding which knowledge applies when.
  • AI is Wisdom, applied: judgment turned into action.

The honest caveat: classic DIKW ends at wisdom, which is human judgment. It never had an execution tier. THE CLIMB adds one. AI as Wisdom (Applied) is an extension, not a textbook mapping, and that extension is the point. The climb takes a model about knowing and adds a model about doing.

Governance is not a DIKW concept at all. DIKW is a hierarchy, not a governance model. The mortar is THE CLIMB's own idea, and it turns a ladder of understanding into something an organization can run.

This post follows an earlier one on WISB and WIRI, What It Should Be and What It Really Is, on how comparing the two exposes drift between intention and reality. Where that post used a Configuration Management Database to detect drift, this one climbs from data to action.

What this means for your next agent project

Work the checklist in climb order. Do not start at the top.

Foundation:

  • Inventory complete: you know every dataset the agent will touch.
  • Every dataset classified, with a named owner who answers for it.
  • Lineage traced from source to use.

Transformation:

  • Data contracts written for the key datasets the agent depends on.
  • Quality gates in place that stop bad data before it reaches the agent.
  • Any number the agent reports can be traced and defended.

Semantic:

  • One definition per business term, agreed and written down.
  • The same question returns the same answer in every tool.
  • Definitions live in one place, not scattered across platforms.

Intelligence:

  • The agent reasons only with data and context it is allowed to see.
  • Access rules are enforced, not assumed.
  • The agent's reasoning can be inspected, not just trusted.

AI:

  • The list of actions the agent may take is written down.
  • Autonomy is staged: recommendations first, approved actions next, wider only on evidence.
  • A human approves where the stakes demand it.

Governance:

  • A control exists in every layer, not a review at the end.
  • When something goes wrong, you can point to the seam where it failed.

Connect with SJULTRA

Follow SJULTRA for more on cybersecurity observability, CAASM, and AI governance.

Share this article

Sources and further reading

Publication context

Originally published November 17, 2026. Product capabilities, platform names, and technical steps may have changed. Confirm current details before making an implementation decision.

Put the idea to work

Turn insight into a practical next step.

Explore how SJULTRA can help with managed security operations, or talk through your specific environment with the team.

Research & community

eBPF community newsletter and updates

A look at eBPF community developments and the people sharing practical security and observability work. Use the original publication date when evaluating event and project updates.

Read insight

Let’s see a clearer tomorrow.

Talk with a team that turns complex security challenges into a practical next step.

Talk to SJULTRA