The Mechanism Axis

Definition

The Mechanism Axis is the “how” dimension of Greg Kihlström‘s AI Capability Framework, from the book Stop Saying “AI”. The Four Pillars name what AI does. They’re silent on how, and the “how” carries most of the cost and most of the accuracy risk. The mechanism axis names that “how.”

A capability can be delivered by a hand-written rule, a trained predictive model, a generative model, or a generative model running agentically in a loop with tools. These order into a spectrum:

rules / if-this-then-that → predictive → generative → agentic

As you move rightward, determinism, consistency, auditability, and cost-efficiency fall, while flexibility, reach, and failure surface rise. Agentic sits at the far end because it’s a composite — generative-in-a-loop-with-tools — which is why it inherits every generative failure mode and compounds them across steps.

The crucial structural claim is that mechanism is orthogonal to the pillars — an axis that crosses them, not a fifth tier in the stack. It has to be an axis because the mapping is many-to-many: a generative model powers Generation and Augmentation; an agentic loop serves Orchestration, but Orchestration also runs on pure if-this-then-that; a predictive model feeds Insights and triggers Orchestration. One mechanism spans several pillars, and one pillar is reachable by several mechanisms — the signature of two things that vary independently.

The two things that make a mechanism choice matter route into tiers the framework already has: cost and token usage are a Force (compute economics), and accuracy, consistency, and re-derivation are the Trust layer (stochasticity and silent confident-wrongness). The mechanism choice is the upstream decision variable that produces both and reduces to neither, which is why it earns a name of its own rather than being dissolved into those two tiers.

How It Relates to Marketing

In a marketing stack, the mechanism is where the money hides. Two features can serve the identical pillar — say, routing an inbound message — while one runs a five-line rule and the other runs an agentic loop that costs orders of magnitude more per interaction. The pillar conversation can’t see that difference. The mechanism conversation can.

Naming the mechanism under each capability does three things for a marketing leader:

• Exposes cost. It ties a capability to its real compute and token bill, which lands in the Forces tier.
• Exposes risk. It surfaces how stochastic the capability is and how hard its output is to verify, which lands in the Trust layer.
• Exposes over-provisioning. It reveals where a heavy, expensive mechanism is doing a job a lighter one would clear — the pattern the framework calls the forklift carrying a coffee cup.

The Four Mechanisms at a Glance

Mechanism	What it is	Strengths	Costs and risks
Rules / if-this-then-that	Deterministic logic	Cheap, consistent, fully auditable	Brittle; can’t handle novelty
Predictive	Trained model scoring or classifying	Efficient at scale; well-understood	Needs data; drifts; bounded to what it was trained on
Generative	Model synthesizing new output	Flexible; handles open-ended input	Stochastic; can be confidently wrong; higher cost
Agentic	Generative-in-a-loop with tools	Broad reach; multi-step autonomy	Compounds generative failure; hardest to audit; costliest

How to Apply the Concept

1. Name the pillar first. Decide what the capability does before touching how it’s built.
2. Identify the current mechanism. Is the capability running on a rule, a predictive model, a generative model, or an agentic loop?
3. Route the two consequences. Send its cost to the Forces reading and its accuracy and verifiability to the Trust reading.
4. Check for a lighter option. Ask whether a mechanism to the left would still clear the task’s accuracy bar. This is the lightest-mechanism discipline.
5. Hold the collisions apart. A generative mechanism isn’t the Generation pillar, and an agentic mechanism isn’t the Orchestration pillar. See the two collisions.

Comparison to Similar Concepts

Concept	Describes	Relationship
The Mechanism Axis	How a capability is implemented	The framework’s “how” dimension
AI maturity ladders	Organizational sophistication	Often conflate capability with technique; the axis separates them
Machine Learning vs. rules	Two implementation styles	Two points on the axis
Robotic Process Automation	Deterministic task automation	A rules-end mechanism

Most AI taxonomies stack technique and capability together, which is what produces the “we need generative AI” reflex before anyone has said what the capability is. The mechanism axis pulls the two apart on purpose, so the “what” and the “how” get decided in the right order.

Best Practices

• Keep it an axis, not a tier. The moment mechanism is stacked as a band, the many-to-many mapping breaks and the model starts implying a diagonal that doesn’t exist.
• Decide the “what” before the “how.” Pillar first, mechanism second. Reversing the order is how impressive techniques get bought for modest jobs.
• Expect to pay twice for moving right. Every step rightward costs more in compute and more in verification. Budget both.
• Treat agentic as a composite. Because it’s generative-in-a-loop, it inherits generative failure modes and compounds them, so its Trust burden is the heaviest on the axis.

Future Trends

• Mechanism churns while pillars hold. The pillars are built to stay stable as the mechanisms serving them re-version and reprice, so the axis is where most of the framework’s ongoing movement will concentrate.
• The center of gravity drifts right. As generative and agentic mechanisms get cheaper, the temptation to default to them grows, which makes the lightest-mechanism discipline more valuable, not less.
• Verification tooling becomes the gate. How far right a team can safely reach will track how good its Trust-layer tooling is.

FAQs

1. What is the mechanism axis? The “how” dimension of the AI Capability Framework: the spectrum of implementation techniques — rules, predictive, generative, agentic — along which any pillar can be built.

2. Why is it an axis instead of a tier? Because the mapping between mechanisms and pillars is many-to-many. One mechanism spans several pillars and one pillar is reachable by several mechanisms, which is the signature of an orthogonal dimension, not a stacked band.

3. Is agentic just the best mechanism? No. The spectrum is a menu of trade-offs. Agentic offers the most reach but also the highest cost and the hardest-to-audit failure surface, because it’s generative running in a loop.

4. Where does a mechanism’s cost show up in the framework? In the Forces tier, as compute economics and token usage.

5. Where does its accuracy risk show up? In the Trust/Verification layer, as stochasticity and the risk of silent confident-wrongness.

6. What’s the one rule it produces? Use the lightest mechanism that clears the task’s accuracy bar.

Related Terms

1. The AI Capability Framework (Master Stack)
2. The Lightest-Mechanism Discipline
3. The Forklift and the Coffee Cup
4. The Two Collisions
5. The Pillar × Mechanism Grid
6. The Four Pillars
7. Generative AI
8. Agentic AI
9. Predictive Analytics
10. Robotic Process Automation (RPA)

Sources

• Kihlström, Greg. Stop Saying “AI”. https://amzn.to/4wilWcA
• Greg Kihlström — official site. https://www.gregkihlstrom.com