AIToday
Large Language ModelsAI Safety & AlignmentAI Business & IndustrySiliconANGLE AIPublished: Oct 16, 2026, 04:00 JST

IBM's Lynch: Start AI from outcomes, not roles

IBM's Lynch: Start AI from outcomes, not roles

3 Key Points

  1. What happened

    IBM outbound CTO Tyler Lynch said teams should start from customer outcomes, not roles. He wants agent telemetry for token usage to trigger policies that can revoke an API key. HashiCorp's Infragraph is now available to eligible Terraform customers on a limited basis.

  2. Why it matters

    Lynch said no one has yet nailed how to handle authorization, logging and telemetry for different agent types. He also said shared infrastructure context could help teams catch dependency impacts their own changes might miss.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

IBM's approach, as described by outbound CTO Tyler Lynch, frames intelligent operations around a business question: what should AI help an enterprise accomplish? That framing extends beyond isolated projects to an operating model linking agent actions to customer outcomes, infrastructure dependencies and financial accountability.

On agent safety, Lynch points to a gap: agents deployed like applications, autonomous agents, delegated agents and local co-work agents have very different needs for authorization, logging and telemetry, and he says no one has nailed it yet. IBM supports Nvidia's Open Agent Safety Platform, contributing enterprise capabilities for agent identity, credentials and hybrid infrastructure, and Lynch's talks with Apptio have raised the idea of extending agent safety into financial oversight. His proposal is to emit token-usage telemetry from agents and let policies evaluate it, potentially revoking an API key to stop an agent until a human reviews it.

For operations, HashiCorp's Infragraph is now available to eligible Terraform customers on a limited basis. Lynch describes it as a graph-based representation of infrastructure that IBM is extending into a knowledge graph, enriched by FinOps and observability tools. That shared context may help teams catch dependency impacts beyond the resources a particular configuration directly manages, an area Lynch calls a scientific interest. On value, he argues spending alone cannot show whether AI delivers, and that financial practices are moving from retrospective cloud bills toward shorter optimization cycles and forecasting based on actual spending, with operational information reaching FinOps teams, controllers and CFOs. Ahead of IBM TechXchange 2026, his advice is to start from customer outcomes and expand from there.

FAQ
What is Infragraph and who can use it?
HashiCorp's Infragraph is a graph-based representation of infrastructure that IBM is extending into a knowledge graph. It is now available to eligible Terraform customers on a limited basis.
How does IBM suggest controlling agent spending?
Lynch said telemetry can be emitted directly from agents for token usage in and out. Policies could evaluate that and revoke an agent's API key to stop it until a human reviews it.
What does Lynch say about measuring AI value?
He said spending alone cannot show whether AI delivers value, and enterprises need to connect investment to outcomes like getting something to market faster or doing a process better.
SiliconANGLE AIRead Original Article

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleJapan Mobility Show Bizweek 2026 puts Physical AI in focus