<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[Prosaic Times]]></title><description><![CDATA[Thinking, not thought leadership, about enterprise technology. Prosaic Times explores the wonder and frustration of enterprise tech through the lens of history, economics, political science, psychology, epistemology and sardonic humor. ]]></description><link>https://www.prosaictimes.com</link><image><url>https://substackcdn.com/image/fetch/$s_!aBhv!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F64635cf2-2a93-40b6-829e-183019d5b8aa_336x336.png</url><title>Prosaic Times</title><link>https://www.prosaictimes.com</link></image><generator>Substack</generator><lastBuildDate>Thu, 19 Nov 2026 11:05:40 GMT</lastBuildDate><atom:link href="https://www.prosaictimes.com/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[James Kaplan]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[prosaictimes@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[prosaictimes@substack.com]]></itunes:email><itunes:name><![CDATA[James Kaplan]]></itunes:name></itunes:owner><itunes:author><![CDATA[James Kaplan]]></itunes:author><googleplay:owner><![CDATA[prosaictimes@substack.com]]></googleplay:owner><googleplay:email><![CDATA[prosaictimes@substack.com]]></googleplay:email><googleplay:author><![CDATA[James Kaplan]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[Strategy is everything]]></title><description><![CDATA[We just need to think rigorously about it]]></description><link>https://www.prosaictimes.com/p/strategy-is-everything</link><guid isPermaLink="false">https://www.prosaictimes.com/p/strategy-is-everything</guid><dc:creator><![CDATA[James Kaplan]]></dc:creator><pubDate>Sun, 15 Nov 2026 21:51:20 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/225051436/c640b8eb08ebb60b5d4ebc282e4de619.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>Strategy has a bad reputation. How many senior executives do you know who use &#8220;strategic&#8221; as a pejorative? I get it.</p><p>Everything is a strategy these days. Corporate strategies, business unit strategies, technology strategies, procurement strategies, purchasing strategies. Forget about the consumer price index, we live in an era of strategy inflation.</p><p>We have strategies for everything, but can barely define the word. What makes a strategy a strategy: breadth, height, impact or something else? Is the distinction between strategy and tactics qualitative or quantitative? How can we employ a concept we can&#8217;t define?</p><p>And, oh, the strategists. Anyone who has read the first chapter of <em><a href="https://www.hbs.edu/faculty/Pages/item.aspx?num=195">Competitive Strategy</a></em> and has walked past a copy of <em><a href="https://classics.mit.edu/Tzu/artwar.html">The Art of War</a></em> in an airport bookstore claims the moniker of strategist &#8212; despite innocence of the ideas of <a href="https://www.hup.harvard.edu/books/9780674007031">Luttwak</a>, <a href="https://www.mca-marines.org/gazette/ooda-loop-for-strategy/">Boyd</a>, <a href="https://classicsofstrategy.com/2016/01/19/liddell-hart-strategy-1954/">Liddell Hart</a>, <a href="https://www.napoleon.org/en/history-of-the-two-empires/biographies/jomini-antoine-henri-baron-de/">Jomini</a> and <a href="https://press.armywarcollege.edu/cgi/viewcontent.cgi?article=1974&amp;context=parameters">Mackinder</a>.</p><p>But Sir Lawrence Freedman implies strategy is everything, or at least underpins everything. In his <a href="https://global.oup.com/academic/product/strategy-9780199325153">history of the idea of strategy</a>, Freedman refuses to limit himself to statesmen and great captains. He locates the seeds of strategic thinking in the Torah and Greek epics and extends it all the way forward to nineteenth- and twentieth-century revolutionaries and political activists. Strategy involves humans exercising agency to achieve consequential objectives in the face of resistance and constraints. Maybe the use of strategy as an idea is okay, if we think rigorously about?</p><p>I worry my dear colleague <a href="https://www.mckinsey.com/our-people/whitney-zimmerman">Whitney Zimmerman</a> is too generous with Michael Porter. He counters that I conflate Porter with the Porterites. We enjoy debating Luttwak.</p><p>I also greatly enjoyed my discussion with Whitney about his new book, <em><a href="https://www.wiley.com/en-us/Strategy+and+Value%3A+The+Four+Foundations+That+Drive+Long+Term+Performance-p-9781394437672">Strategy and Value</a></em>, co-authored with our McKinsey colleagues Tim Koller and Andy West.</p><ol><li><p><strong>What makes a strategy a strategy?</strong> Is it a few bold, coherent choices about allocating resources, as Whitney argues, or a falsifiable wager on how the world works, as I maintain?</p></li><li><p><strong>Where does strategy end and doctrine begin?</strong> Is Jamie Dimon&#8217;s <a href="https://www.jpmorganchase.com/ir/annual-report/2025/ar-ceo-letters">fortress balance sheet</a> a strategy, or a governing conviction within which JPMorgan makes strategic choices?</p></li><li><p><strong>Can you have a technology strategy independent of a business strategy?</strong> And what good is a technology strategy that treats applications, infrastructure, cybersecurity and data as separate kingdoms? [1]</p></li><li><p><strong>Why are organizations so reluctant to argue?</strong> If there is zero tradeoff between vigorous debate and warm collaboration, why do so many executives behave as though disagreement is a character defect?</p></li><li><p><strong>Will AI make us better strategists or merely more confident idiots?</strong> If machines do the analytical work, where will the next generation of executives acquire the judgment to recognize when the machines are wrong?</p></li><li><p><strong>Are we confusing projection with momentum?</strong> How can a company deliver splendid financial results while quietly consuming its future? As Lampedusa observed in <em><a href="https://www.penguinrandomhouse.com/books/40905/the-leopard-by-giuseppe-di-lampedusa/">The Leopard</a></em>, everything must change for things to remain the same.</p></li></ol><h4><strong>Strategy Linked to Value</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p><em>Strategy and Value</em>, out November 17, distills more than 50 years of McKinsey thinking on strategy and valuation.</p></li><li><p>The premise is the connection between strategy and value, not either one alone.</p></li><li><p>The book pairs the concepts that drive decisions with practices that hold across approaches to strategy.</p></li></ul><div><hr></div><p><strong>James Kaplan:</strong> Hi there. This is James Kaplan with another Prosaic Times video podcast. I&#8217;m here with my colleague Whitney Zimmerman. Whitney, do you wanna introduce yourself?</p><p><strong>Whitney Zimmerman:</strong> Sure, James. It&#8217;s a pleasure to be on Prosaic Times. I&#8217;m a big fan, regular listener.</p><p>So I have the unfortunately fancy title of Distinguished Expert in Strategy, which means that I get to spend all of my time thinking and working with others on the future of strategy, and also, of course, talking with clients about it. I have been with a firm since twenty eighteen. Before that I spent about eight years in industry, in BMW and in semiconductor manufacturing.</p><p>I&#8217;m an engineer by training, but my big passion is two questions. What makes leaders good at strategy, good at leading the work of strategy?</p><p>And what makes institutions institutionally good at strategy as well? So, excited to be here.</p><p><strong>James:</strong> Okay, and I will note you&#8217;re one of the relatively few people I know who&#8217;s read more books about strategy than I have, which I respect. And now&#8212;</p><p><strong>Whitney:</strong> I like the competition.</p><p><strong>James:</strong> Yes, now we&#8217;ll have a strategy book club. You&#8217;ve written a book, so tell us a little bit about that.</p><p><strong>Whitney:</strong> Yeah, so we are coming out on November 17th with <em><a href="https://www.wiley.com/en-us/Strategy+and+Value%3A+The+Four+Foundations+That+Drive+Long+Term+Performance-p-9781394437672">Strategy and Value: The Four Foundations That Drive Long-Term Performance</a></em>. It is a distillation, a grounding of over 50 years of McKinsey thinking on both strategy and valuation. And importantly, it&#8217;s that intersection.</p><p>It is the connection between strategy and value. And it talks about the fundamental things that you need to understand in order to ensure that strategy creates value, both from concepts that drive the decisions you make and also some of the practices that apply across all kinds of approaches to strategy.</p><h4><strong>Strategy as Choices, Not Theory</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>Strategy is a few big, coherent choices that guide resource allocation; it is not an obligation or a plan for tomorrow.</p></li><li><p>A thesis, like the fortress balance sheet, is the theory behind the choices; keeping the two apart sets a higher bar for what counts as strategy.</p></li><li><p>Strategic choices concern where to play, how to play and future customer value; tactical choices are the reversible, day-to-day ones.</p></li></ul><div><hr></div><p><strong>James:</strong> Okay. So let me ask a little bit of an almost conceptual question. Strategy is one of those words, I don&#8217;t know, governance, that can mean almost anything to anyone. What is strategy to you, and how is it different from management, and how is it different from tactics?</p><p><strong>Whitney:</strong> This question of what is strategy, there&#8217;s a reason why it isn&#8217;t clear. It&#8217;s because there are legitimately many schools of thought on what strategy is.</p><p>And that&#8217;s both important, because there are many important reasons and ways of thinking about strategy, but it&#8217;s also a challenge. And it&#8217;s why I always start every conversation I have with a new executive talking about what I think strategy means.</p><p>We like to think about strategy as choices. It&#8217;s a very classic way of thinking about it. A coherent set of, usually, few big choices, or bold choices, that are designed to work together with some kind of underlying logic in order to change a business by guiding capital allocation, resource allocation, et cetera.</p><p>I like to say that a strategy shouldn&#8217;t be an obligation. It&#8217;s not like you need a strategy in order to know what to do tomorrow.</p><p>Strategy is important as a tool for changing a business. You use these choices in order to guide resource allocation. You use it in order to communicate some sort of underlying logic.</p><p>I also like to differentiate it from theory or a thesis. There&#8217;s a great example of a theory or thesis, which is Jamie Dimon&#8217;s fortress balance sheet concept, which he&#8217;s talked about for 20 years in <a href="https://www.jpmorganchase.com/ir/annual-report/2025/ar-ceo-letters">his shareholder letters</a>. The idea is that he has a unique view of the future, which is that they work in a very volatile industry, and that stability matters.</p><p>And that in order to succeed, it is important to have a fortress balance sheet to be able to lead through volatility, to be there for your customers, and also to take advantage of uncertainty. That isn&#8217;t, in my view, their strategy. Their strategy is the choices they&#8217;re making in any given year to build new businesses, to acquire companies, to build new capabilities, to transform how they work.</p><p>Those choices are ultimately informed by the thesis or the theory. And holding those two separate is valuable because it allows you to hold a higher bar for what a strategy really is. It is getting to those clear choices.</p><p>It&#8217;s about saying no. It is about having that underlying theory. And so that&#8217;s how we think about strategy.</p><div><hr></div><p><em>Strategy is important as a tool for changing a business. You use these choices in order to guide resource allocation. You use it in order to communicate some sort of underlying logic.</em></p><div><hr></div><p><strong>James:</strong> So what if someone were to ask you which choices are strategic choices versus which choices are tactical choices? How do you draw that distinction?</p><p><strong>Whitney:</strong> On the tactical side, typically tactical choices are things that you&#8217;re doing day to day in order to advance your business, and they&#8217;re often reversible. They&#8217;re often doing things that are sensible in pursuit of goals.</p><p>For strategic choices, I like to think about a classic framework from McKinsey, from Kenichi Ohmae in the 1980s, called the <a href="https://ideas.repec.org/a/eee/eurman/v1y1982i1p38-48.html">Strategy Triangle</a>, where he organized strategies into a triangle, saying there are competitor strategies, there are customer strategies, and there are corporate strategies. We are doing things in order to pursue customer opportunity, we are doing things in service of competing with competitors, and we are doing things to change or leverage how we work as a business. I map that to how we think about it in the book.</p><p>Strategic choices should be about either changing where you are playing, because you believe a market is becoming fundamentally more or less attractive; changing how you are playing, in pursuit of competitive advantage; and doing things that are in service of pursuing or creating future customer value. And those three things are deeply interlinked, which I think is easy to miss.</p><p>People think, I just need to pick where I play and then pick how I&#8217;m gonna win. And in reality, those two questions of where do I play and how do I win in service of creating value are deeply interlinked, both with each other and also with where future customer value is going.</p><h4><strong>Keeping a Market Leader Honest</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>A market leader can look strong while its underlying momentum declines.</p></li><li><p>A shared reality about markets, advantage and value creation keeps strategic choices honest.</p></li><li><p>Staying unique is a lens on market leadership that gets too little attention in stable times.</p></li></ul><div><hr></div><p><strong>James:</strong> Well, first up, let me ask two questions here. First, you talk about strategy in the context of change. Can a strategy be&#8212;maybe reactionary is the wrong word&#8212;but say you&#8217;re the market leader. Could you have a strategy around keeping things the same?</p><p><strong>Whitney:</strong> One of the good ways of thinking about this is momentum. You always want to have an understanding, not just what you&#8217;re <a href="https://www.prosaictimes.com/p/every-decision-you-make-rests-on">projecting</a>, but what the true underlying momentum of the business is. And when you see it that way, you can say, yes, we&#8217;re a market leader today, yes, things have been going well, but if you look at the underlying momentum of the business, it might be declining, due to various headwinds, due to various short-term decisions you might be making, bad optimization of how you&#8217;re thinking about market share versus capability.</p><p>When you&#8217;re doing strategy, it&#8217;s important to have a sort of shared reality amongst your team about the fundamental attractiveness of your markets, about the nature of advantage, and about how and why you create value, and to look at that momentum to keep you honest about the strategic choices you might need to make in order to sustain your market leadership.</p><p><strong>James:</strong> Yeah, I think there&#8217;s a famous novel called <em><a href="https://www.penguinrandomhouse.com/books/40905/the-leopard-by-giuseppe-di-lampedusa/">The Leopard</a></em> where one of the characters says, everything will need to change if we want things to remain the same.</p><p><strong>Whitney:</strong> Yes, and it&#8217;s all about perspective. It&#8217;s also one of those things where strategy is often talked about as being about uniqueness. It&#8217;s not always the case. But trying to understand how we continue to be unique, how we stay unique, is a lens on market leadership that is often one that doesn&#8217;t get enough focus, and is important, especially in times of stability.</p><h4><strong>Systems Thinking and Doctrine</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>A strategy and the theory behind it work as a system only when people share common language and mental models.</p></li><li><p>McKinsey&#8217;s 7S framework, now evolved into Organize to Value, treats an organization as a system, though a team of systems thinkers does not guarantee a system that works.</p></li><li><p>Doctrine adds values and productive constraints; with ideas now abundant, constraint separates good strategy from a surplus of ideas.</p></li></ul><div><hr></div><p><strong>James:</strong> So I was very taken by your point about the fact that where to play and how to win are so interconnected. And sometimes I worry that in many businesses people think in a very siloed way. We&#8217;ve got our manufacturing strategy over here, we have our customer strategy over there, we&#8217;ve got our technology strategy hidden in a corner and never&#8212;nobody&#8217;s allowed to&#8212;that&#8217;s not allowed to be connected to anything.</p><p>What you&#8217;re saying evokes systems thinking to me. And I wonder, the fascinating thing about systems is that it&#8217;s so nonlinear that four pieces together are worthless, but five pieces together are incredibly valuable. I was wondering if you could talk a little bit about the interplay of <a href="https://www.prosaictimes.com/p/prosaic-times-elevating-ai-from-tactics">systems thinking</a> and strategy.</p><p><strong>Whitney:</strong> Yes. There are so many angles on systems thinking going through my head at the moment. So, some of the things that come to mind.</p><p>Number one, this is why I think it&#8217;s valuable to separate a strategy, the coherent choices you&#8217;re making in any given part of the organization, and the underlying theory or thesis. And this comes from the <a href="https://whitneydzimmerman.substack.com/p/the-strategy-leader-as-scientist">theory-based view of strategy</a> from Zenger and Felin and others, and the idea that in order for a system, an organization, to effectively change, you benefit from having that sort of theory or thesis, a unique view of the future, your place and the advantages you can have in it, how you capture value, et cetera. Because it allows the broader system, the people around an organization, to have the same sort of underlying causal logic, the underlying theory that allows them to sense opportunities coherently and make choices.</p><p>And when you just focus on strategy, meaning the choices you&#8217;re making, oftentimes the broader system can&#8217;t always connect to those choices. Leaders across an organization may be able to connect their jobs to one or two of them, sometimes not.</p><p>And so for a system to work well, I think that&#8217;s where it&#8217;s important to have that sort of underlying corporate theory or thesis. That&#8217;s number one.</p><p>I think number two: systems work well when there&#8217;s common language, common mental models. There&#8217;s a lot of discussion today about clarity of ontologies. Our research finds that top teams that have a clear understanding of what strategy is and what quality strategy looks like outperform.</p><p>They&#8217;re more likely to reach the top of our <a href="https://www.mckinsey.com/capabilities/strategy-and-corporate-finance/our-insights/strategy-to-beat-the-odds">economic profit power curve</a>. [2] And so having a sort of shared standard, and we have a standard in the book, a standard for strategy, ensures that across an organization there&#8217;s a sort of strategic culture, a level of coherence about how we think, which is very, very important.</p><p>I think it&#8217;s also important not to become overfocused on one dimension. A classic McKinsey framework from the 1980s that&#8217;s a systems-thinking framework, the 7S, has now evolved into&#8212;</p><p><strong>James:</strong> Yes, I would agree. I would very much agree. Seven S is a systems thinking framework.</p><p><strong>Whitney:</strong> It&#8217;s fundamentally a systems orientation to how you view an organization. And that&#8217;s why the paper that introduced it, &#8220;<a href="https://doi.org/10.1016/0007-6813(80)90027-0">Structure Is Not Organization</a>,&#8221; started by talking about how you can&#8217;t just understand an organization by looking at its structure. And it equipped people with the ability to see the broader system and pull together, much like our book is trying to do, literature from across different fields into the essentials.</p><p>And that, of course, has now been evolved and modernized in our <a href="https://www.mckinsey.com/capabilities/people-and-organization/our-insights/the-key-to-ai-value-is-hiding-in-plain-sight-your-operating-model">Organize to Value</a> framework, which is very powerful. There is a benefit to people having a systems view, and as an electrical engineer I really value that. But it&#8217;s also worth recognizing that just because everyone in an organization is a systems thinker doesn&#8217;t necessarily mean that the system will work well at the end of the day, if that makes sense.</p><p><strong>James:</strong> Fair. What you&#8217;re thinking is the difference between <a href="https://www.prosaictimes.com/p/you-need-both-business-technology">strategy and doctrine</a>? And doctrine I sometimes mean to be, yeah, we do things this way. This is how we build a car, right?</p><p><strong>Whitney:</strong> Yeah, so the way I think about doctrine personally is very consistent with the idea of what an organization&#8217;s corporate theory or value creation thesis is. I think, though, that doctrine, the way I think about it, can go a little further than that. It also can have values that matter to an organization, and it&#8217;s something that fundamentally is designed to focus, to constrain.</p><p>Productive constraints, to equip people with a way of understanding how and why they feel they can create value. And it&#8217;s central to people being able to be part of an organization and not just a good leader.</p><p><strong>James:</strong> Yeah. If you think about <a href="https://www.prosaictimes.com/p/context-is-the-new-code">military doctrine</a>, say in the US military, NCOs have a lot of responsibility, which is different from other militaries. And you might say that&#8217;s part of the doctrine of how the US runs its armed forces. That&#8217;s applicable probably in a whole bunch of different strategic contexts, but the effectiveness of a relatively small unit, or the assumptions you can make about the effectiveness of a relatively small unit, creates, I presume, strategic options in deploying forces.</p><div><hr></div><p><em>Just because we are awash with ideas, we have a surplus of ideas, doesn&#8217;t mean that translates to strategy, to good strategy. Constraint, productive tension, is an important way of getting to value.</em></p><div><hr></div><p><strong>Whitney:</strong> Yeah, and we are awash with strategic options today. No one is lacking for strategic ideas and options. And AI, of course, is only making that&#8212; there&#8217;s a lot of discussion about how AI can give you just the average option, but in reality, I think in practice, there are a lot of situations where you&#8217;re seeing the idea not come from the AI but from the edge of the organization, where a leader sees something, has an idea, or has always had one and now has AI as a little team to be able to bring it to life.</p><p>And so we are awash with ideas. But just because we are awash with ideas, we have a surplus of ideas, doesn&#8217;t mean that translates to strategy, to good strategy. Constraint, productive tension, is an important way of getting to value.</p><p>And doctrine, or corporate theory, or value creation thesis, et cetera, is an important way of ensuring that the ideas being identified by a small team, et cetera, are more likely than not going to be coherent and complementary to how the overall organization is working, the capabilities it&#8217;s building, its ability to change, its momentum, and where it&#8217;s moving. And so that&#8217;s why I think it&#8217;s important to have that. It&#8217;s also why, in our penultimate chapter, which has recently been published in McKinsey Quarterly as <a href="https://www.mckinsey.com/capabilities/strategy-and-corporate-finance/our-insights/the-six-strategy-roles-a-ceo-must-not-delegate">the undelegatable roles of the CEO</a>, we don&#8217;t say that the CEO owns strategy.</p><p>Only the CEO can own strategy: I think that&#8217;s an unhelpful frame. I think many, many people across an organization can own this practice of getting to big, clear, coherent choices and saying what&#8217;s going to stop and what is not going to happen.</p><p>But ultimately, the second role, for us, is the view that only the CEO can change the company&#8217;s value creation thesis, which you might also frame as doctrine. It&#8217;s that thing that gives everyone a sense of who we are and where we&#8217;re going into the future.</p><h4><strong>Functional and Integrative Strategy</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>Strategy as a tool of few big choices applies at any level, including a function or one person.</p></li><li><p>At every level strategy integrates the pieces beneath it, and capabilities move across the business.</p></li><li><p>Debate is how an organization integrates; each strategic initiative needs one owner, which themes cannot supply.</p></li></ul><div><hr></div><p><strong>James:</strong> Is the idea of functional strategy a meaningful idea? We often talk about marketing strategy or manufacturing strategy or procurement strategy. Is that meaningful, or is that just wrapping planning in higher level terms, or what have you? What does a functional strategy mean to you?</p><p><strong>Whitney:</strong> Yeah. So it&#8217;s important to, I think, expose my biases within this. So&#8212;</p><p><strong>James:</strong> Please. That&#8217;s what we&#8217;re here for.</p><p><strong>Whitney:</strong> So, as I&#8217;ve mentioned, I see strategy as a tool. It is a set of few big choices you are making in order to guide how resources are allocated in pursuit of some greater value. And it is used to change a business.</p><p>And when you take that as the definition, it is something that you can do anywhere in the organization, including for yourself personally. I am making a few big choices. I&#8217;m making clear about what I&#8217;m not gonna do.</p><p>I have some sort of underlying theory for what those choices are. And I&#8217;m comfortable with the extent to which those choices are either betting on certainty or trying to shape the landscape, either by adapting to uncertainty or by trying to create it.</p><p>And when you take that as a way of viewing strategy, then it makes complete sense to say, yes, of course we should think about functional strategy. We should think about using this tool of a few big choices, or coherent choices, that make clear how we should change our part of the business, coherent with and in support of a broader strategy and a broader thesis in the organization. Now, that isn&#8217;t the only way of thinking about it.</p><p><strong>James:</strong> Right. You know, I&#8217;m not a&#8212;we&#8217;ve discussed that I&#8217;m not a Porter fan. I may throw you off the video conference set.</p><p><strong>Whitney:</strong> Yeah, and I am a Porter fan. But I think that&#8217;s why it&#8217;s important to define terms in an organization, of what do we mean by strategy and what does it do for us. And there can be different views, and very legitimate ones, but what matters in an organization is clarity of what we mean, especially in an age of AI, where it&#8217;s important to ground ourselves and our AIs in that sort of epistemology, not just ontology.</p><p><strong>James:</strong> Yeah. Sometimes I think of strategy at any given level as <a href="https://prosaictimes.substack.com/p/things-i-was-too-stupid-to-know-when-1bf">integrative</a>, which is the way you bring together marketing plus sales plus operations plus technology plus procurement plus half a dozen other things. And at the enterprise level, it&#8217;s often strategy across business units plus functions.</p><p>In a business unit, it&#8217;s across functions. In a function, it&#8217;s across subdomains. Let&#8217;s take technology strategy.</p><p>We can break down an enterprise technology organization into a bunch of different parts: application development, infrastructure, cybersecurity, data, what have you. And a lot of what I see as interesting enterprise technology strategy is the integration of the strategies across the different components of the technology organization.</p><p>You see the same for marketing or operations or any other function. Does that resonate at all?</p><p><strong>Whitney:</strong> Completely. And I think that it&#8217;s particularly important today. There&#8217;s a great school of thought called <a href="https://www.cambridge.org/core/books/dynamic-capabilities-and-related-paradigms/50501CF71C6118316FC74C28A1B61DEE">dynamic capabilities</a>, from David Teece and others, where they talk about advantage coming from the ability to take capabilities in one part of an organization and bring them to another, in order to ensure that what you&#8217;re doing, and what you&#8217;re bringing from your business or building, is meeting the moment, wherever you are.</p><p>That, of course, is a fundamentally integrative task, of how you are thinking about moving things across a business, bridging capabilities from one context into the other. That&#8217;s my first thought.</p><p>The second is that one of the points we make in the book is that we don&#8217;t say there&#8217;s one approach to strategy, because there are many. We say there are some universally important practices, like having that shared reality, holding strategy to a high bar, but also debate. We say, listen, productively disagreeing or debating is how we bring our different perspectives from different parts of a business or our humanity into a problem.</p><p>And it is important to equip teams with the tools, the language, the permission to debate the right things for strategy, at the right times. And if you don&#8217;t do that, if you don&#8217;t focus on the quality of debate, the quality of productive disagreement, in an organization, it can be very, very difficult to be institutionally integrative, as opposed to there being someone that is the integrator.</p><p>And the third thing I would say about that is one of the failure modes I see in organizations is that they see a real need for a strategic choice, a strategic initiative that is cross-functional, but they don&#8217;t&#8212; Part of our standard for strategy is to say any given strategic choice should be codifiable as one or very few strategic initiatives, each of which should be owned by one person. And oftentimes strategy comes out as themes, which is a way out of getting to enough clarity about how we are going, as an organization, to ensure one person can own, for example, a cross-functional strategic choice.</p><div><hr></div><p><em>We say, listen, productively disagreeing or debating is how we bring our different perspectives from different parts of a business or our humanity into a problem. And it is important to equip teams with the tools, the language, the permission to debate the right things for strategy, at the right times.</em></p><div><hr></div><p><strong>James:</strong> I don&#8217;t know how you execute on a theme.</p><p><strong>Whitney:</strong> Indeed. And our research finds that mobilization of strategy matters a lot, and that companies exceptional at mobilization are also exceptional at getting strategy to a high standard with clear choices. [3] And so this idea of an integrative approach to strategy is also, I think, very intertwined with holding a high standard for how clear a choice is, in order to push the debate long enough to the trade-offs required for one person to own something that is truly integrative.</p><h4><strong>Debate and Productive Disagreement</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>Corporations may have grown less comfortable with conflict, though no one has longitudinal data to say so.</p></li><li><p>Teams able to debate in service of the best answer show a marker of success, especially under uncertainty.</p></li><li><p>Organizations treat debate as something to make comfortable instead of a capability to build; tools like Amazon&#8217;s six-page memo prepare people for it.</p></li></ul><div><hr></div><p><strong>James:</strong> Let me ask this question; it&#8217;s a bit of a cultural question. I sense, and I can&#8217;t prove this, that corporations are less comfortable with conflict than might have been the case twenty years ago. They conflate intellectual tension with personal conflict, making, in some cases, it harder to have the sort of debates you&#8217;re describing around strategy.</p><p>Do you agree with that hypothesis? And do you think that institutions that are willing to have the real debates, that the willingness to have real debates about tough choices, becomes an indicator of success or a marker of potential success?</p><p><strong>Whitney:</strong> I don&#8217;t&#8212; I don&#8217;t have data longitudinally on whether organizations&#8212;</p><p><strong>James:</strong> None of us do. I certainly don&#8217;t either.</p><p><strong>Whitney:</strong> &#8212;have gotten worse over time. I do know it has always been an issue. I think it&#8217;s part of human nature to be consensus oriented. That&#8217;s why Peter Drucker used to talk about the importance of productive disagreement.</p><p>I would also hypothesize that it has gotten worse over time, organizations having consensus-oriented cultures that don&#8217;t lend themselves to productive disagreement, to debate. I also would agree, from my client work, that organizations where top teams or any teams have an ability to have productive debate in service of the best answer, where we&#8217;re trying to have sympathy for others&#8217; perspectives to bring it to the best answer, I think is a very important marker of success. And it&#8217;s something particularly important in uncertainty.</p><p>There is lots of research on the cognitive biases and social dynamics that can hold teams back from grappling with their strategy. And you don&#8217;t have to necessarily be comfortable with debate and productive disagreement to understand it matters. There are lots of things that we do in organizations that we don&#8217;t want to do because we know it&#8217;s important.</p><p>And I don&#8217;t think enough organizations place that priority on debate. They look for it to be comfortable, as opposed to understanding it is important and a capability to have.</p><div><hr></div><p><em>There are lots of things that we do in organizations that we don&#8217;t want to do because we know it&#8217;s important. And I don&#8217;t think enough organizations place that priority on debate. They look for it to be comfortable, as opposed to understanding it is important and a capability to have.</em></p><div><hr></div><p><strong>James:</strong> Well, if you believe a company or a corporation is, at least in part, an information processing entity, then the debate&#8217;s incredibly important, right? Because that&#8217;s part of processing information.</p><p><strong>Whitney:</strong> Yeah, absolutely. And we also see that&#8212;this is where I&#8217;m a little bit out of my depth, potentially&#8212;but what I see is that there&#8217;s a lot of focus on ensuring that AI agents are debating each other, because we know it gets to better answers, at least when done well. And so I think we all know that this is important, but it doesn&#8217;t make it easy. The question is whether or not it&#8217;s considered to be valuable.</p><p>And I think that&#8217;s also why you have seen, over time, many, many organizations putting in place tools like <a href="https://www.sec.gov/Archives/edgar/data/1018724/000119312518121161/d456916dex991.htm">Amazon&#8217;s six-page memo</a>, which is fundamentally about preparing for a debate and equipping people to have a shared reality, including shared mental models and language, to be able to have a high-quality debate. And I think that then lends itself to the value of it.</p><h4><strong>AI and Shared Understanding</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>AI can reinforce a user&#8217;s biases or, set up as adversarial agents, sharpen thinking.</p></li><li><p>Earlier computing revolutions degraded shared reality in some organizations; the same risk returns as analysis is automated.</p></li><li><p>Understanding how things work, like driving a manual transmission, is worth renewing through strategy work.</p></li></ul><div><hr></div><p><strong>James:</strong> I wonder if the advent of AI will sharpen&#8212;will widen the disparity. Because I would suggest to you, if you&#8217;re using a large language model via a chat window, often the result is sycophantic and will reinforce your biases. In contrast, if you&#8217;re very thoughtful and careful, you can set up an agent to engage in adversarial review, or to give a range of perspectives, or to debate each other. And I wonder if it makes it both easier to reinforce your biases and also easier to challenge them, and you perform an acid test on your thinking.</p><p><strong>Whitney:</strong> It&#8217;s a good question. One of the things I&#8217;m hyper tuned to with myself is trying to manage extrapolation bias, trying to avoid thinking, okay, how have things worked recently, and that means that they&#8217;re gonna work that way going forward. I think you and I are kindred spirits in caring about history as a way of debiasing.</p><p>One of the things that&#8217;s interesting from history is that there have been other massive computing revolutions, like, for example, the rollout of mainframe computers in the 1950s and 60s, and the rollout of personal spreadsheets and ERP databases and relational databases, et cetera. And what we have found in going back into our own archives and in doing research is that after these computing revolutions that have increased the ability to automate analysis, there has been, with some organizations, a degrading of the shared reality. [4] Meaning where people aren&#8217;t really&#8212;I don&#8217;t want to misuse this term&#8212;but are in the loop.</p><p>They don&#8217;t have that shared mental model, shared language. They don&#8217;t share a view&#8212;it doesn&#8217;t mean they have to agree about the outside&#8212;but it&#8217;s important to share the ability to talk about what&#8217;s going on outside the business. And&#8212;</p><p><strong>James:</strong> I always worry about those science fiction novels where a group of people is in some generation ship and there&#8217;s some computer that controls the ship, and at the beginning they understand how to work the computer, and then five generations in they&#8217;ve lost any understanding and the computer has become God, right?</p><p><strong>Whitney:</strong> Yeah, that relates to this idea.</p><p><strong>James:</strong> They see it as a deity that issues pronouncements, right, rather than a tool.</p><p><strong>Whitney:</strong> Yeah, and what I was going to say is that there are natural reasons why that shared reality might degrade, because of the volume of analysis. My colleagues have just done a good piece on <a href="https://www.mckinsey.com/capabilities/strategy-and-corporate-finance/our-insights/the-judgment-bottleneck-balancing-ai-and-human-speeds-in-strategy">the judgment bottleneck</a>.</p><p>But it&#8217;s not universal. There are plenty of organizations that also stayed in the loop, in the sense of ensuring analyses were in service of a so-what, that they were grounded in what really creates value, and things being in pursuit of decisions. And your point just now about generations later, that is a very natural progression in any technology regime.</p><p>It happened in the medieval period as well, where painters would, generation to generation, learn from their masters by copying, and stop understanding why certain things mattered, and things got flattened out. And the Renaissance was in part about regaining an understanding of the fundamentals and breaking with them.</p><p>And the same thing happens in strategy, where you do strategy review year after year, and you&#8217;re doing these templates and you&#8217;re starting to forget why you&#8217;re doing it. And so what I also want to say is that I don&#8217;t think it is a foregone conclusion that it will happen, that it&#8217;ll increase the disparity, because it is a general-purpose technology.</p><p>One of the things that is powerful about AI is that it can make it easier to learn things. And what I have found, and this is also research from <a href="https://whitneydzimmerman.substack.com/p/holding-on-to-the-why-in-strategy">Frank Keil at Yale</a>, who&#8217;s a cognitive scientist who looks at how people understand how things work, is that it is very, very important for people to understand how things work. It applies for children being able to take apart toys.</p><p>It applies also for organizations, in understanding how our organization works and whether we are exposed to the inner workings of it. And that, of course, relates&#8212;</p><div><hr></div><p><em>It is very, very important for people to understand how things work. It applies for children being able to take apart toys. It applies also for organizations, in understanding how our organization works and whether we are exposed to the inner workings of it.</em></p><div><hr></div><p><strong>James:</strong> This is why I&#8217;m so opposed to automatic transmissions.</p><p><strong>Whitney:</strong> Well, automatic transmissions are really cool, as an ex-automotive engineer.</p><p><strong>James:</strong> No, no, no. But you understand, using a manual transmission, you intuitively understand the dynamics of the car, right? You can feel it.</p><p><strong>Whitney:</strong> You understand how things work. Exactly. And so that&#8217;s why I also say strategy processes, strategy work should be in service of renewing and reinvesting in how we understand how things work: the why behind where to play, how to win, and how we make money.</p><p>And when there are incentives towards people understanding the why of their organization, it is more likely that tools like AI will also be used in service of sustaining that understanding of the why. And so that&#8217;s why I think it&#8217;s important, with this book as well, to reground people in some few fundamental concepts that are ultimately about the why, that sit beneath every way of doing strategy, and will unlock the kind of focus and priority that leads to better value creation with strategy.</p><h4><strong>Strategy Books Worth Reading</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>Drucker&#8217;s <em>The Practice of Management</em> and <em>The Effective Executive</em> reground strategy in focusing on the right few things.</p></li><li><p>Todd Zenger&#8217;s <em>Beyond Competitive Advantage</em> makes the case for corporate theory, and his forthcoming <em>Theory First</em>, with Teppo Felin, extends it.</p></li><li><p>Three business memoirs show strategy in practice: Gerstner at IBM, Lafley and Martin on P&amp;G, Cote at Honeywell.</p></li></ul><div><hr></div><p><strong>James:</strong> Okay, in the service of time, we&#8217;re probably gonna have to cut it there. This has been fantastic. You&#8217;re gonna have to come back, and we&#8217;ll have probably&#8212;let&#8217;s dive deeper into the implications of AI on strategy. But before we go, three books other than your own on strategy that you would recommend, or that you find especially insightful. Either business strategy or geopolitical strategy.</p><p><strong>Whitney:</strong> Yeah. So, number one, I think that a lot of things we need, we already know. And it&#8217;s valuable to reground yourself in the past.</p><p>I think a book like <em>The Practice of Management</em> from Drucker or <em>The Effective Executive</em> are really, really important to strategy, focusing on the right few things. Secondly, I&#8217;m a big fan of Todd Zenger&#8217;s <em><a href="https://store.hbr.org/product/beyond-competitive-advantage-how-to-solve-the-puzzle-of-sustaining-growth-while-creating-value/15030">Beyond Competitive Advantage</a></em>, which talks about corporate theory. He also has a book coming out with Teppo Felin called <em>Theory First</em>, which is really relevant there.</p><p>And then I would say, I always like business memoirs that really get at strategy, how things happened. I&#8217;ll throw three in there. I think Lou Gerstner&#8217;s <em>Who Says Elephants Can&#8217;t Dance</em>, in terms of turning around IBM, is really powerful.</p><p><em><a href="https://store.hbr.org/product/playing-to-win-expanded-with-bonus-hbr-articles-how-strategy-really-works/10852">Playing to Win</a></em> by Roger Martin and A. G. Lafley is fundamentally a story of a business, in addition to being a great guide to how you do strategy and how you understand things, that&#8217;s consistent with how we think in many ways. And then as well, David Cote&#8217;s <em><a href="https://www.harpercollinsleadership.com/9781599510217/winning-now-winning-later/">Winning Now, Winning Later</a></em>, about his time at Honeywell and trying to really maintain focus on the long term and ground people in a shared view of how to talk about strategy, I think is really powerful.</p><p><strong>James:</strong> Fantastic.</p><p>Bonus, bonus two books. Thank you so much, Whitney.</p><p><strong>Whitney:</strong> Pleasure. Thanks for having me.</p><h4><strong>Score Your Own Strategy</strong></h4><p><em>*{Six questions to take back to your own team, one for each I raised at the top. Score a point for each yes. Fewer than four, and you may have a plan with a better name.</em></p><ol><li><p><em><strong>Choices.</strong> Can you name the few big choices that make up your strategy, including what you have decided to stop?</em></p></li><li><p><em><strong>Thesis.</strong> Can you state in two sentences the conviction behind those choices, and does your CEO own it?</em></p></li><li><p><em><strong>Integration.</strong> Do applications, infrastructure, cybersecurity and data answer to one technology strategy, and does that strategy answer to the business?</em></p></li><li><p><em><strong>Debate.</strong> When did an argument over a strategic choice last cost someone comfort?</em></p></li><li><p><em><strong>Judgment.</strong> If machines do the analysis, where will your next executives learn to tell when the machines are wrong?</em></p></li><li><p><em><strong>Momentum</strong>. Is your underlying momentum rising or falling, whatever your projections say, and who would tell you?</em></p></li></ol><p><em>-- Ed.}</em></p><h4><strong>Footnotes</strong></h4><p>[1] The December 14, 2025 issue, <a href="https://www.prosaictimes.com/p/you-need-both-business-technology">The tyranny of the use case and the need for enterprise tech doctrine</a>, takes up this question at length.</p><p>[2] Economic profit is operating profit after deducting the cost of capital. In McKinsey&#8217;s analysis of the 2,393 largest companies from 2010 to 2014, the top quintile captured nearly 90 percent of the economic profit created (<a href="https://www.mckinsey.com/capabilities/strategy-and-corporate-finance/our-insights/strategy-to-beat-the-odds">Bradley, Hirt and Smit, &#8220;Strategy to beat the odds,&#8221; McKinsey Quarterly, February 2018</a>). The research behind the claim is <a href="https://www.mckinsey.com/capabilities/strategy-and-corporate-finance/our-insights/how-strategy-champions-win">&#8220;How Strategy Champions win&#8221;</a> (McKinsey Quarterly, July 2025), which finds that stragglers are nearly twice as likely as Strategy Champions to have little or no agreement on what makes strategy high quality.</p><p>[3] The same research, <a href="https://www.mckinsey.com/capabilities/strategy-and-corporate-finance/our-insights/how-strategy-champions-win">&#8220;How Strategy Champions win&#8221;</a>, finds that the biggest gap between Strategy Champions and stragglers is in mobilization, the phase of translating strategic choices into organizational readiness.</p><p>[4] In <a href="https://whitneydzimmerman.substack.com/p/holding-on-to-the-why-in-strategy">his conversation with Yale cognitive scientist Frank Keil</a>, Whitney points to Lou Gerstner&#8217;s IBM in 1993 as a firm that had mastered analysis but whose leaders no longer shared an actionable view of the world. He writes about the case in <a href="https://www.linkedin.com/pulse/sustaining-shared-reality-how-past-technology-waves-have-zimmerman-zqmde">his LinkedIn article on sustaining shared reality</a>.</p>]]></content:encoded></item><item><title><![CDATA[Does AI help us think more, or less?]]></title><description><![CDATA[Where will the next generate of wizards come from?]]></description><link>https://www.prosaictimes.com/p/does-ai-help-us-think-more-or-less</link><guid isPermaLink="false">https://www.prosaictimes.com/p/does-ai-help-us-think-more-or-less</guid><dc:creator><![CDATA[James Kaplan]]></dc:creator><pubDate>Sun, 08 Nov 2026 18:29:05 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/224029691/0472244fe0a3414331de6f3ab665e911.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<pre><code>type: issue
id: &#8220;component-00018&#8221;
display_name: &#8220;ProsaicTimes &#8212; 2026-11-08&#8221;
headline: &#8220;Will AI help us think more &#8212; or less?&#8221;
</code></pre><p>The PE fund CEO thought for a second and then asked &#8220;But where will the next set of wizards come from?&#8221;</p><p>We were discussing the impact of AI on knowledge work. I had observed that professionals would spend more time building <a href="https://www.prosaictimes.com/p/prosaic-times-elevating-ai-from-tactics">ontologies</a> and <a href="https://www.prosaictimes.com/p/everything-is-a-graph">tending graphs</a> than pushing boxes around a slide or copying numbers from one sheet to another.</p><p>The CEO reminisced that he developed his instincts about the financial mechanics of a deal by building hundreds of LBO models himself in the 1990s &#8212; so he could now sit in the investment committee and say &#8220;Wait a second. Something seems off with your capex projections in the out years. Explain that to me.&#8221;</p><p>I reminded him that not too long before that bankers built models with graph paper and calculators rather than spreadsheet software. He countered that moving from spreadsheets to GenAI-built models represented a bigger disruption than moving from graph paper to desktop software. He had a point, and it is stronger than my analogy allowed. Spreadsheets removed the arithmetic but left the model building, and the model building is where his instincts formed. AI may eliminate that work. This is a genuine difference from the move from graph paper to spreadsheets.</p><p>I said that we&#8217;ve been wrestling with the cognitive impact of new information technologies for millennia. The Iliad and the Odyssey pre-dated the re-introduction of written communication to the Greek world by centuries. You imagine crusty bards complaining the youngsters would never really learn Homer if they could just refer to a passage in a scroll.</p><p>The CEO liked the example. I suspect we were both right. AI will eliminate some of the work through which professionals traditionally developed expertise. Whether it creates better ways to develop that expertise remains to be seen. Each individual will need to decide whether he or she will use AI to think more or think less. Each institution will need to decide whether it will use AI to produce more work or to develop more capable professionals. The first path accepts AI slop. The second builds the tools and incentives that enable and encourage employees to achieve things not before possible, and it is the more interesting strategic choice. It is also where the next set of wizards will come from.</p><p>My colleague Ryan Davies and I discuss this topic and many others in this week&#8217;s Prosaic Times podcast.</p><h4><strong>Gen X, Vic 20s and Pac-Man</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>Early computing memories: a Vic 20 word processor, Pac-Man ghosts evolved by genetic algorithms.</p></li><li><p>Twenty-one years at McKinsey on top of an applied math and computer science background.</p></li><li><p>The conversation is set up around finance and the economics of technology.</p></li></ul><div><hr></div><p><strong>James Kaplan:</strong> Hello, it&#8217;s James Kaplan with Ryan Davies and another Prosaic Times podcast. Welcome, Ryan.</p><p><strong>Ryan Davies:</strong> Thank you, James. I am so excited to be here with you.</p><p><strong>James:</strong> And I&#8217;m excited we surmounted our minor audiovisual difficulties in getting this set up.</p><p><strong>Ryan:</strong> In the age of AI, sometimes it&#8217;s the little stuff that trips us up.</p><p><strong>James:</strong> Exactly so. So Ryan, we start out with why don&#8217;t you give people just a brief introduction or a brief background?</p><p><strong>Ryan:</strong> Okay, my name&#8217;s Ryan. I&#8217;ve been 21 years now at McKinsey. Before McKinsey, I studied applied math and computer science. And probably the closest I&#8217;ve ever been to the frontier of AI was in high school. I grew up in New Mexico, and there was something called the supercomputer challenge, where kids got to code something for the supercomputers at Los Alamos to run. And my sophomore year, we used genetic algorithms to evolve Pac-Man ghosts, and we competed against some more deterministic heuristics that we also coded and the genetic algorithms just beat all the other ones and we won. And that was a really awesome experience and again probably the closest I&#8217;ve ever been to the AI frontier in the mid to late 90s, quite a while ago now.</p><p><strong>James:</strong> That is terrific. Well my first computing experience was programming a Commodore Vic 20, which is not so glamorous as a supercomputer.</p><p><strong>Ryan:</strong> Yeah, but you&#8217;re very credible.</p><p>Old school cred.</p><p><strong>James:</strong> That&#8217;s a function of being Gen X. I will say I was talking with a senior executive and we realized we were the same age and we&#8217;re talking how we first started with technology. I mentioned I wrote a word processor in nineteen eighty-two on my VIC twenty so I wouldn&#8217;t get bad grades in my papers for my lousy handwriting.</p><p><strong>Ryan:</strong> Ha ha.</p><p><strong>James:</strong> And this guy ran outside into the file cabinet outside of his office and came back in with the Vic twenty he used or the Commodore 64 he used as a teenager back in the nineteen eighties. So that is how emotional an attachment to those of us who are Gen X can have to our early computers. I do not still have either of the physical Commodore machines.</p><p><strong>Ryan:</strong> Excellent. Yeah.</p><p>If I interpret Twitter correctly, I am a quote geriatric millennial.</p><p><strong>James:</strong> Our mutual colleague Charlie Lewis describes himself as a Xennial, I believe. We Gen Xers are always skeptical because we don&#8217;t think the Xennials or the geriatric millennials are sardonic enough to hang with Gen X.</p><p><strong>Ryan:</strong> Mm. I am very earnest.</p><h4><strong>Tokenomics and who burns tokens</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>In the three-to-five-year window, building AI may cost more than running it.</p></li><li><p>An enthusiastic engineer with an unlimited budget can consume far more tokens than anyone has modeled.</p></li><li><p>Mapping a code base into a graph spares the tokens spent searching it again every turn.</p></li></ul><div><hr></div><p><strong>James:</strong> So one of the reasons I&#8217;d asked you to come on was to I know you do a lot of work in corporate finance and spend a lot of time with CFOs, so we should talk a little bit about that and you know how to think about it&#8217;s a particular passion of mine to think about technology w from a rigorously economic standpoint. So we&#8217;d love to hear a little bit about your perspective on that and we can range more broadly because I know there&#8217;s a whole bunch of things related to AI and technology far beyond the CFO function that I know you&#8217;re all also interested in. So tell us a little bit about how you think about that.</p><p><strong>Ryan:</strong> Yeah, happy to. And I think by the way, personally very interested in AI and longtime personal and professional interest in capital markets and finance. There&#8217;s many ways in which those two come together, all of which are really interesting. One of the pet projects that I haven&#8217;t really gotten off the ground, but I think there&#8217;s actually a lot more research we could potentially do in a bunch of different areas of this. We also, by the way, have a fantastic team digging into tokenomics and exactly this question. So Tanguy and Wasim.</p><p>And a bunch of other folks. We have a tech ROI effort that has done some good work on this. And frankly, we&#8217;re still much nearer the beginning than the end, I think, of having settled all the theory. And then there&#8217;s more work to get from great theory to great practice.</p><p><strong>James:</strong> Yeah, I admit to being a bit of a tokenomic skeptic.</p><p><strong>Ryan:</strong> Say more about what you mean by that.</p><p><strong>James:</strong> Okay, so there&#8217;s a couple of ways companies might consume tokens. They can consume it via chat interface, but that&#8217;s not that many tokens. Very few people can type that quickly. They can consume it via applications that engineers have built. they can consume it via the process of building those applications, and they can consume it via citizen development. Now, in the three to five year time frame, if you think of those middle two things the number of software engineers you have is a natural barrier on the number of tokens you can consume. So I&#8217;m hypothesizing, I haven&#8217;t modeled this out entirely, that in the short term, <a href="https://www.prosaictimes.com/p/the-rise-of-the-stupid-model">the cost of building AI for many enterprises will exceed the cost of running AI</a>.</p><p>And finally the big unknown is to what extent companies will succeed with citizen development. Then you widen the number of people who are both using coding tools and therefore consuming tokens and building things that might consume tokens. Does that make sense at all?</p><p><strong>Ryan:</strong> I get the framework, and the driver in the driver tree that my instinct is to pressure test first is the maximum tokens that a software engineer could consume. Because with cursor and</p><p><strong>James:</strong> That is the X factor, I agree.</p><p><strong>Ryan:</strong> cursor and Claude Code and more and more loops and layers of abstraction, it wouldn&#8217;t surprise me if we have orders of magnitude to go before. And I do think there&#8217;s a ceiling on just cognitive capacity.</p><p>And I think there&#8217;s less of a ceiling than there should be right now on the quality of the code and software that&#8217;s being developed. And hopefully for the sake of everyone, that starts to bind a little more as well. But I think an enthusiastic software engineer with an unlimited budget can probably spend a lot of money with access to the right models and harnesses.</p><div><hr></div><p><em>And I do think there&#8217;s a ceiling on just cognitive capacity. And I think there&#8217;s less of a ceiling than there should be right now on the quality of the code and software that&#8217;s being developed.</em></p><div><hr></div><p><strong>James:</strong> Yeah, and just as a note, I found out of the forty four thousand people in McKinsey last month I hit the top ten. Not the top ten percent, but the top ten in terms of token consumption.</p><p><strong>Ryan:</strong> Good for you.</p><p>I thought that was mostly BAs in the top ten, so you&#8217;ve really earned some cred to get up there.</p><p><strong>James:</strong> Well that&#8217;s a thing. Even though I&#8217;m old, I try and hang with the young.</p><p><strong>Ryan:</strong> Yeah. I don&#8217;t have to watch my McKinsey token consumption that much because I&#8217;m not so much of a big user, but I have a personal, Claude Pro or Claude Max or whatever subscription. And so it is interesting to me when I&#8217;m, vibe coding something, a personal agent or I was recently using Fable for some personal legal advice, which may or may not be advisable. That&#8217;s not legal advice or life advice, but I wasn&#8217;t getting into big numbers.</p><p><strong>James:</strong> Yeah, it&#8217;s interesting to me, and I think there&#8217;s gonna be a lot of discussion about architectural choices you make that will impact token consumption. For example, one thing I did with one of my repos is I mapped my entire code base into a graph. So each function is a node,</p><p><strong>Ryan:</strong> Mm-hmm. Cool.</p><p><strong>James:</strong> each function call is an edge.</p><p>And I think I haven&#8217;t instrumented this yet, but from what I read, that mitigates token consumption. Because you&#8217;re not doing this investigation of the code base with every turn.</p><p><strong>Ryan:</strong> You&#8217;re not like searching every time.</p><h4><strong>Deterministic code, open weights and JEV</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>Agentic software engineering that produces deterministic code can draw on thirty years of quality assurance. Agentic software at runtime cannot.</p></li><li><p>Open-weight models may be good enough for most deployed applications, but frontier-lab optimization could erase the cost edge.</p></li><li><p>Turning free text into structured data is the killer use case for a cheap classifier like JEV.</p></li></ul><div><hr></div><p><strong>James:</strong> Exactly, exactly. Now that said it is hilarious to think that it&#8217;s sometimes hard to get your code base to act the way you want. You watch and you see it start grepping half the world, you&#8217;re like, no, don&#8217;t grep. Walk the graph, walk the edges. But the other thing I&#8217;m thinking about a little bit is where do we want to use agentic applications where you&#8217;re in effect consuming tokens at runtime. And when do we want to use agentic software engineering to <a href="https://www.prosaictimes.com/p/a-system-is-just-a-very-fast-legal">build deterministic applications</a>? Which has two advantages. One of which is if you&#8217;re consuming tokens once, that&#8217;s more token efficient. And then perhaps more importantly, once you write the code, we can use thirty years of software quality assurance practice to make sure we&#8217;re comfortable that the code does what we want it to do. Quality assurance for a non deterministic application is a little bit hairier a thing.</p><p><strong>Ryan:</strong> Yeah. I totally agree with that point. I think one, I agree, there&#8217;s a lot of the idea of building deterministic or largely deterministic software with very very contained, non-deterministic, LLM calling pieces is the way to think about things. That&#8217;s putting aside, for example, I expect we&#8217;ll find, again, orders of magnitude efficiencies, one through using open weight models where useful. By the way, one of my pet theses that is difficult for me to fully express financially is that secure end-to-end <a href="https://www.prosaictimes.com/p/cybersecurity-is-entropic-too">American sovereign provision of great open weight models</a> is gonna be a massive business. I also think sorry, you say something on that.</p><p><strong>James:</strong> Yeah, well let&#8217;s strike that department our colleague Sven Blumberg, who I have a lot of regard for, his hypothesis, and he&#8217;s still getting his head around this a little bit also, is that the Frontier Labs are doing some massive optimization that we don&#8217;t see. So it&#8217;s not clear to him that open weight, when you consider the TCO, is less expensive than a proprietary model. [1]</p><p>Now, I haven&#8217;t seen the analysis on that. I don&#8217;t think he&#8217;s done it yet, but it&#8217;s an interesting hypothesis for me to examine. Because originally even a few weeks ago I was hypothesizing, yeah, I was thinking, gee, we all have this massive, nobody&#8217;s using their laptop capacity. Why aren&#8217;t we putting local open weight models on every software engineer&#8217;s laptops and just sopping up spare capacity.</p><p><strong>Ryan:</strong> Yeah. It&#8217;s an interesting hypothesis. It&#8217;s counterintuitive to me, which doesn&#8217;t mean that it&#8217;s wrong.</p><p>My intuition is that there&#8217;s, for a significant majority of tasks, actually, when it comes to inferencing in an established application, a great open weight model will be good enough. By the way, I&#8217;m not even going to pretend that I fully understand <a href="https://typesafe.ai/blog/introducing-system-one-models-and-jev">JEV</a>, but there&#8217;s probably some other things around routing to different models and model types to further create efficiency.</p><p><strong>James:</strong> JEV is fascinating to me.</p><p><strong>Ryan:</strong> And so I want to hear your thoughts on JEV, but just the closing thoughts.</p><p>It feels to me like, for the vast majority of deployed applications and deployed agents, the number of times you&#8217;re calling Fable or Astra or Argo or something like that in the running of that application should be very small or zero.</p><p><strong>James:</strong> Yeah, I think that&#8217;s a really good point. That the frontier models matter more in software engineering than software execution. The other thing, I haven&#8217;t had a chance to play with JEV yet, but here&#8217;s why I&#8217;m so intrigued. One of the killer use cases to me for Gen AI is the conversion of free text to structured data.</p><p>And I would argue, for example, since the beginning of time, McKinsey associates have created scads of value by sitting down with hundreds of pages of free text and coding that in such a way that they could turn into structured data and we could do some sort of analysis with it. Something so simple as was an insurance claim paid in adherence to policy or not?</p><p>Right. And then we come back and say, hey, we sat down with a sample of a thousand insurance claims, and guess what? Twenty of them are paid inappropriately. You in your career, I&#8217;m sure, have seen a thousand analyses like that. Here&#8217;s a hundred transactions that went sideways, here&#8217;s a thousand transactions that where you had some sort of breakage and here&#8217;s why they went sideways. And so the ability to use something like JEV to quickly and cheaply act as a classifier to me is incredibly exciting.</p><p><strong>Ryan:</strong> Yeah, I have the same intuition without any of the technical understanding to underpin it properly.</p><p><strong>James:</strong> Well remember you have a background in computer science. You&#8217;re well ahead of many people. And you were building genetic algorithms in the nineteen nineties.</p><p><strong>Ryan:</strong> I was at MIT, our partner university two weeks ago, and one of the things that I took comfort from was that the MIT professors were excellent, by the way, really, really good. And it gave me some comfort that even they, who are able to spend much more time than I do trying to keep up with the frontier, struggle to keep up with the frontier.</p><h4><strong>Leaders cannot delegate AI fluency</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>Fluency comes only from building with the tools.</p></li><li><p>Senior technology executives who gave up the keyboard can build again.</p></li><li><p>A family-calendar agent shows the payoff comes as much from clearing bottlenecks as from writing code.</p></li></ul><div><hr></div><p><strong>James:</strong> Yeah, the only way and it sounds like you&#8217;re doing one of the most important things, unless you&#8217;re spending real time with one of the coding agents, I don&#8217;t even know how you stay conversant.</p><p><strong>Ryan:</strong> I don&#8217;t think it&#8217;s possible. One of the points that one of the MIT professors made, which completely resonates with me, is that AI leaders cannot delegate AI fluency today if you want to be an effective leader in domains for which AI is relevant, which arguably is becoming pretty much all of the domains that exist. And the only way to develop fluency is to be messing around with this stuff. And so yeah, I&#8217;ve found I try to do a lot of different things with it professionally. Frankly, the coding I&#8217;m doing almost entirely it&#8217;s for my own, like on my own personal account. So I made a home agent called Claudine who helps maintain our family calendar. And I set up, Claudine&#8217;s got a WhatsApp account and it&#8217;s set up on Twilio and it&#8217;s running on Railway and we can text Claudine if we wanna update, the calendar or something like that. By the way, the LLM for that, I think I built it with Opus 4.8, extremely helpful not only for the code generation, but for the debottlenecking: hey, the Twilio verification is hung up somewhere, what should I do? It would have taken me five times as long.</p><div><hr></div><p><em>One of the points that one of the MIT professors made, which completely resonates with me, is that AI leaders cannot delegate AI fluency today if you want to be an effective leader in domains for which AI is relevant, which arguably is becoming pretty much all of the domains that exist. And the only way to develop fluency is to be messing around with this stuff.</em></p><div><hr></div><p><strong>James:</strong> You never would have gotten there. You don&#8217;t say it would have taken you five times as long, you would have given up.</p><p><strong>Ryan:</strong> It would have taken me five times long to write the code, but I would have stopped on some of these administrative bottlenecks that the AI was very helpful to solve.</p><p><strong>James:</strong> Yeah, this is an interesting dynamic I sometimes see with senior technology executive CIOs, CTOs, and what have you, which is folks with these roles in big companies, they gave up the keyboard a long time ago. Partially because if you&#8217;re the CTO of a big bank, there&#8217;s hundreds of different technologies. You can&#8217;t stay current on all of them.</p><p>Right, and you&#8217;re necessarily managing via a level of abstraction. Things are changing very quickly. And I can&#8217;t tell you the number of senior technology executives said, well gee, now I can build again. Because it allows them to move more quickly and it allows them to debug things and figure things out even if they haven&#8217;t been reading sort of staying current on all the forums and newsgroups and what have you so not only, I would suggest, can senior leaders, to your point, not outsource AI fluency, but now have much more capability to be fluent in AI than would have been the case or anything else even a couple of years ago. Does that make sense?</p><p><strong>Ryan:</strong> Yeah. I agree with that. And I think there are some prominent counterexamples. It&#8217;s like Tobi L&#252;tke from Shopify is posting all the time about all this stuff he&#8217;s building, and it&#8217;s awesome, and I think highly, highly credentializing. And my encouragement to all the folks out there with computer science backgrounds, or even not, is, build with this stuff, one, because it&#8217;s gonna make you better, and two, it&#8217;s outrageously fun. It is outrageously fun to bring things to life in this way.</p><p><strong>James:</strong> It&#8217;s the world&#8217;s best Lego set. Let me test the hypothesis.</p><p><strong>Ryan:</strong> Yeah. So just the next frontier for Claudine, my wife spends real time every Sunday night transcribing from a list of recipes for a week to the grocery list for the week. And that&#8217;s</p><p><strong>James:</strong> Yeah. Oh God.</p><p><strong>Ryan:</strong> obviously something AI could do quickly. So when I find the chunk of time, and it&#8217;s not gonna be this weekend because I&#8217;m away at an AI conference, but it&#8217;s when I find a chunk of time, that&#8217;s my next thing to build is the use case for Claudine to do that grocery list transcription.</p><p><strong>James:</strong> Yeah, I have to admit, I&#8217;m fanatical I&#8217;ve put everything about my professional life into <a href="https://www.prosaictimes.com/p/turning-relationships-into-files">a knowledge graph which I built myself</a>. Our home life is still very pad and paper. And there&#8217;s some degree of which it&#8217;s I enjoy the paper tangibility of it. Also with the kids in college things are much simpler than they were ten years ago.</p><p><strong>Ryan:</strong> Yeah, my extracurricular and driving schedule on the home front sounds like it&#8217;s probably more complicated than yours is at the moment.</p><h4><strong>Will knowledge workers become engineers?</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>Knowledge work may look like DevOps and capital-markets strats: people who build the tools and know the domain.</p></li><li><p>Some people will use AI to think more and some to think less, and the second group loses.</p></li><li><p>Cognitive time under tension and refusing to delegate understanding keep the mind sharp.</p></li></ul><div><hr></div><p><strong>James:</strong> Yeah, yeah, now it&#8217;s like, oh gee, yeah, Thanksgiving&#8217;s coming. They&#8217;ll be home.. It&#8217;s much less logistically challenging than had been the case in the past. Let me test a hypothesis with you. I wonder if knowledge workers, business analysts, finance analysts, what have you, are going to become <a href="https://www.prosaictimes.com/p/you-cant-learn-much-without-wasting">more like software engineers</a>.</p><p>And the two metaphors I sometimes use are it&#8217;s like DevOps for knowledge work. It used to be when people provisioned a server, they would sit down and do the configuration directly. Now they&#8217;ll write a script, or use a script to do the configuration. The other is like strats in capital markets where you the people who are both very good software engineers and also understand capital markets or understand various trading strategies and what have you. And so do you think we&#8217;re at the edge of a transformation in knowledge work and what knowledge work looks like and feels like. Taking finance as an example.</p><p><strong>Ryan:</strong> Yeah. It&#8217;s a really interesting question.</p><p>It brings me back, by the way, to when I was interviewing out of undergrad for McKinsey. I was also interviewing with Goldman Sachs. And to Goldman&#8217;s credit, they spent a lot of time trying to figure out what role to put me in. And they ended up giving me a couple of offers to be what&#8217;s called a sales strat, which is I guess what you are at Goldman if you can code and do math at a high level, but also are good at talking to clients or something like that.</p><p><strong>James:</strong> Yeah. The forward deployed engineer is a new name, it&#8217;s not a new thing.</p><p><strong>Ryan:</strong> Yeah, maybe sales strats were the forward deployed engineers of the Goldman FICC division of the day. I like what you described. And I think the best knowledge workers probably will go in that direction. They&#8217;re capable of building, deploying, tweaking these tools like at the edge, at the coal face, if you will. On the other hand, I&#8217;m not sure everyone&#8217;s gonna do the work &#8212; the personal work &#8212; to develop the capability to get there. And there was an article I read, I can&#8217;t remember where, but my synthesis of the article is that there are some people who will use AI to think more, and some people who will use AI to think less. And people using AI to</p><p><strong>James:</strong> I think that&#8217;s exactly right.</p><p><strong>Ryan:</strong> think less is a problem and will not work out well for them professionally.</p><p><strong>James:</strong> I think that is precisely correct. Because you do have people say, gee, AI can write the executive summary for me. No, no, no, you write the executive summary. AI helps you structure the appendix. Or AI helps you gather the information.</p><p><strong>Ryan:</strong> Yeah. One other concept I liked a lot, there was a podcast, <a href="https://www.theringer.com/podcasts/plain-english-with-derek-thompson/2026/09/11/whats-the-point-of-college">Derek Thompson interviewed a guy named David Deming</a>, who&#8217;s now the dean of Harvard College. Interestingly, Ohio State undergrad has become dean of Harvard College, which is impressive. Good for him.</p><p>And there were a couple things I really liked about the interview, but one of the concepts that really stuck with me, which was actually from Derek, was this idea of <a href="https://www.derekthompson.org/p/the-end-of-thinking">cognitive time under tension</a>. In the same way that physically we build muscle by time under tension, cognitively we build cognitive ability by thinking and thinking hard and pushing our brains. And so I think that concept is really useful because if we&#8217;re, using AI to explain.</p><p>And think and pressure test, which is certainly how I feel. I think it&#8217;s gonna, our brains will stay strong and we&#8217;ll be magnified by it in a way that&#8217;s really impactful. If we use it to offload too much, we risk, cognitive atrophy. And again, I don&#8217;t think that ends well for people who go down that path.</p><p><strong>James:</strong> I think that&#8217;s a really interesting point. And one of the dirty little secrets of knowledge work, whether it&#8217;s software engineering or anybody anything else, there has traditionally been a lot of <a href="https://www.prosaictimes.com/p/friction-wont-disappear-from-corporate">mindless scut work</a> where you could turn your brain off. It&#8217;s like copying and pasting and I always hated back in the 90s sort of coding UIs I always felt was sort of brain dead but necessary, or what have you. I&#8217;m sure many will disagree with me. And it&#8217;s interesting to me the degree to which by abstracting away some of the scut work.</p><p>Working with AI forces you to be on your game for a higher percentage of the day.</p><p><strong>Ryan:</strong> Yeah, you hear stories of burnout in software engineers, for example, where it&#8217;s like, they&#8217;re doing so much more. But again, there&#8217;s real cognitive load to it, and our energy, our physical energy and cognitive energy is finite. So yeah, and I certainly relate to that. I feel like I go to bed tired as often as I ever had. And it reminds me, our colleague and CFO Yuval Atsmon published something in his newsletter on LinkedIn a week or a couple weeks ago and the title was Don&#8217;t Delegate Understanding. And it was a really thoughtful piece about you know how to use AI and not use AI. And I think this idea of by all means use it, but don&#8217;t delegate understanding. By the way, it&#8217;s a good policy in knowledge work in general and has been for long before Gen AI was a thing. But it&#8217;s a really good framing and it takes real effort and energy to do it well all the time.</p><div><hr></div><p><em>And I think this idea of by all means use it, but don&#8217;t delegate understanding. By the way, it&#8217;s a good policy in knowledge work in general and has been for long before Gen AI was a thing.</em></p><div><hr></div><p><strong>James:</strong> Yeah, one thing I want to do some research on is the distinction between, system one, intuitive versus intentional system two, intentionally analytical thinking when you&#8217;re using AI. Because I often find myself using a lot of system one thinking, a lot of instinct, which is not that different from what you do when you&#8217;re working with early tenure associates, you develop some instinctive pattern recognition about the stuff they tend to get wrong in the spreadsheet. And you don&#8217;t quite know exactly why you&#8217;re saying, go tell me about this cell. But you do, and it turns out that that&#8217;s something that&#8217;s messy. And I find myself using a lot of that, which does also require a lot of concentration.</p><p><strong>Ryan:</strong> Yeah. I had a system two example last night where we had a we&#8217;re preparing for an important workshop for a client next week. We have a draft deck, we have a draft draft agenda and all that kind of stuff. And the client helpfully like wrote us what they had in mind for the agenda.</p><p>Same spirit, but different in some ways.</p><p>And we spent ten or fifteen minutes on the team problem solving talking about it. And then I said, you know what? I actually just need some quiet time with this. Let&#8217;s end the problem solving. I need to sit and really think about how we incorporate the other input while staying true to what we think is really important in this session and make that one fused thing. And that was an offline old school manual. System 2.</p><h4><strong>Redlines, contracts and legal work</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>An automated redline between a client email and a revised draft catches what a tired reviewer misses.</p></li><li><p>Comparing contracts conceptually, not just word for word, makes legal work the canary for knowledge work.</p></li><li><p>A formal contract language would expose vendor terms and open second-order economic effects.</p></li></ul><div><hr></div><p><strong>James:</strong> Yeah.</p><p>I love that example. The one thing I&#8217;ll add is one of the things I love about incorporating Gen AI into a workflow is the ability to take two things and sort of compare them. For example, there was a document that I sent over to a client. Client said, gee, this is great. I circulated with the people. Here&#8217;s these 12 pieces of feedback. Could you incorporate this? Had a associate partner update it. And I looked through it and like, yeah, this looks pretty good. But the ability to do a virtual red line or an automated red line between the email I had gotten from the client and the updated draft to do the punch list of whether everything had been addressed.</p><p>Yeah, I would have done that by hand, but I&#8217;m sure that the machine would have been more conscientious than I would have been by myself.</p><p><strong>Ryan:</strong> Yeah. I had a funny personal example of that recently. Does Chrome want to relaunch now? No. Dismiss.</p><p><strong>James:</strong> Chrome might want you, but you don&#8217;t want Chrome to.</p><p><strong>Ryan:</strong> Yes. This is in the context of a prospective real estate transaction in my personal capacity, but we&#8217;re going back, there&#8217;s some stuff that&#8217;s a little complicated. So we had drafted a contract and the other party had had their lawyers draft a different contract sort of from scratch from a different template. And I was using Fable on this and its ability to almost instantly pick apart the comparison, not just at a word for word level, but a conceptual level was amazing. And for example, it identified something about the template that the counterparty was using that was actually favorable to us, not them, which I wouldn&#8217;t have caught, maybe, even if I had stared at it for 24 hours, but it just picked it up like that. By the way, I think legal work is gonna be a fascinating canary in the coal mine for knowledge work in general because these models are amazing at some of that stuff</p><p><strong>James:</strong> Well, and a contract is a form of code. Although I will admit, it astonishes me that nobody came up fifty years ago with like formal language for certain types of legal contracts, but I suppose what&#8217;s that?</p><p><strong>Ryan:</strong> Like lean for legal contracts? That&#8217;s a great idea.</p><p><strong>James:</strong> Yeah, XML, XML, yeah, exactly. Yeah. We have formal language for mortgage contracts. That&#8217;s why banks can trade mortgages because there&#8217;s a standardized, parameterized way of describing mortgages. Now I&#8217;m sure there&#8217;s a were a million in stakeholders that did not want formal language for various types of contracts, but yeah. One of the second order things that I think nobody&#8217;s thought through you think about it, contracting is incredibly intransparent. Most companies, even if they sign a contract, it goes in a virtual file cabinet, they never look at it ever again. Because it&#8217;s just not worth it.</p><p>But now you can interrogate your contracts with your ten thousand vendors to figure out what the discrepancies in payment terms are or whether you&#8217;re fully taking advantage of the payment terms you have access to. There&#8217;s going to be, I think, some interesting second order microeconomic effects to the fact that we will now have much more transparency into and transparency over time.</p><p>Does that make sense?</p><p><strong>Ryan:</strong> Yeah.</p><p>It&#8217;s super interesting. From the math angle, it&#8217;s been really interesting what folks have done in recent years with Lean and <a href="https://techcrunch.com/2026/11/05/axiom-math-wants-to-keep-ai-slop-out-of-mathematics/">Axiom Math</a> and Frontier Labs are getting in the mix. I hadn&#8217;t thought about this idea of an analogous, truly formalized language for the law, but it&#8217;s a really appealing idea. And for any entrepreneurial-minded folks out there, I&#8217;m not convinced</p><p><strong>James:</strong> Except to lawyers.</p><p><strong>Ryan:</strong> that Harvey and Legora are gonna, survive in the end of day if the core intelligence is coming from the frontier models, but maybe there&#8217;s a different legal entrepreneurial angle there.</p><h4><strong>CFOs and the ROI hand wave</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>CFO fluency on AI varies widely, and perhaps half of CFOs admit they can&#8217;t see the return.</p></li><li><p>Tesla, SpaceX and Amazon show that option value, not current operations, can justify an investment.</p></li><li><p>Treating an AI case like a venture bet may be more honest than scrubbing it like a tactical purchase.</p></li></ul><div><hr></div><p><strong>James:</strong> Exactly. I wanna talk to you about the AI conference you&#8217;re going to in a couple of minutes, but before we do that, where are most CFOs on AI investments, on how they&#8217;re thinking about <a href="https://www.prosaictimes.com/p/cios-the-boardroom-is-grading-a-business">how to measure value from AI</a> and, you know what? Less about how AI is gonna change the finance function, because everyone knows that&#8217;ll get more automated, but how will it change the economics of large institutions? Does that make any sense?</p><p><strong>Ryan:</strong> It&#8217;s a great question. A couple things. First of all, I recorded a little video snippet in February where I said that I thought ROI on AI is gonna be the most important question in business in twenty six, and I feel pretty good about that standing the test of time. Second is you see in CFOs like other executives.</p><p>A very wide, perhaps shockingly wide dispersion of AI fluency. And from people who are doing impressive things to people who, and I certainly won&#8217;t name you, feel like it&#8217;s like, have you been living under a rock for the last three years? Like, I don&#8217;t want to be dispersed. Yeah.</p><p><strong>James:</strong> There&#8217;s a lot of rocks in corporate America for people to live under.</p><p><strong>Ryan:</strong> Third an experience that speaks to this that really stuck with me. So we have a global CFO forum every year in London in June. It&#8217;s a fantastic event. Everyone out there should nominate your CFOs. It&#8217;s really, really world-class only McKinsey event. One of the things that surprised me most there, because this question is top of mind for everyone, how are you thinking about ROI on AI?</p><p>I was expecting all of the CFOs, or substantially all of the CFOs, to be really hard edged, yeah, we&#8217;re looking really hard at this and really scrubbing the numbers and sweating the business cases and all this kind of stuff.</p><p>And what I heard instead was actually, maybe half the CFOs were in that camp, but many, many CFOs, maybe half, were much more in the hand wave. We actually don&#8217;t know exactly where the return is gonna come from. We kind of know it&#8217;s the right thing. We had the CFO of an almost hundred billion dollar enterprise, super rigorous guy, former banker, getting interviewed on stage, and he was like.</p><p>Yeah, I don&#8217;t actually have line of sight to the ROI. I just intuitively, know it&#8217;s the right thing to do. And that that surprised me. But it&#8217;s interesting. I don&#8217;t actually know that it&#8217;s wrong. Yeah. More honest and not necessarily</p><p><strong>James:</strong> Is it possible that&#8217;s the more honest answer? Is it possible that given</p><p><strong>Ryan:</strong> wrong.</p><p><strong>James:</strong> the degree of uncertainty that trying to scrub the AI business case the way you would scrub the business case for sort of a more tactical technology investment. Maybe that&#8217;s the wrong thing. Maybe you have to think about this a little bit like a venture capitalist.</p><p><strong>Ryan:</strong> Yeah, a capital markets analogy that comes to my mind is if you try and explain, I&#8217;ll pick an extreme example or two. If you try and explain the value of Tesla or the value of SpaceX through the current operating businesses, you just can&#8217;t get there. Those companies are valued the way they are because they have these real businesses. And Elon might do other awesome stuff on that platform.</p><div><hr></div><p><em>If you try and explain the value of Tesla or the value of SpaceX through the current operating businesses, you just can&#8217;t get there. Those companies are valued the way they are because they have these real businesses. And Elon might do other awesome stuff on that platform.</em></p><div><hr></div><p><strong>James:</strong> When, in one institution, you have, what, seventy percent of the world&#8217;s space launch. I&#8217;m sure it&#8217;ll be in the percentage.</p><p><strong>Ryan:</strong> But the thing is you can&#8217;t get to one and a half, two trillion dollar just on the space launch business. You just can&#8217;t get there. And so yeah,</p><p><strong>James:</strong> Of course, I understand that, but I&#8217;m saying who the hell knows what might happen.</p><p><strong>Ryan:</strong> yeah, but so the point is a financially rigorous take on it could be there&#8217;s some near-term ROI, but there&#8217;s, the value of us being at the cutting edge of this will create new frontier opportunities that we don&#8217;t even understand yet, but we have conviction it&#8217;s important for us to be on that frontier. I frankly feel that way about us as a firm as well.</p><p><strong>James:</strong> Yeah. think about it from an Amazon standpoint, from my understanding outside in, a large percentage of Amazon&#8217;s cash comes from <a href="https://www.sec.gov/Archives/edgar/data/0001018724/000101872426000038/amzn-20260930xex991.htm">AWS</a>, another big chunk comes from advertising. In 2003, who would have predicted AWS or Amazon&#8217;s advertising business. Nobody had foresight into that. They leveraged the platform, they used the option value of the platform and leveraged it in different ways.</p><p><strong>Ryan:</strong> Yep, the platform, the talent, the leadership.</p><h4><strong>The Curve, P doom and growth</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>The Curve gathers a multidisciplinary group around positive outcomes from transformational AI.</p></li><li><p>P doom tracks geopolitics, and the larger worry is P degradation: thinking less, and sycophantic models.</p></li><li><p>Growth could add a hundred basis points a year, and recursive self-improvement is doubtful.</p></li></ul><div><hr></div><p><strong>James:</strong> Exactly. so tell me about this conference you&#8217;re going to. That sounds super interesting.</p><p><strong>Ryan:</strong> Yeah, I&#8217;m very excited and intrigued. The conference is called <a href="https://thecurve.goldengateinstitute.org/">The Curve</a>.</p><p>It&#8217;s in Berkeley, California this weekend. [2] It&#8217;s put on by a nonprofit called the Golden Gate Institute. And the intent of the conference is to bring together a diverse multidisciplinary group of thinkers to discuss how we can, as humanity, achieve positive outcomes from transformational AI. And this is the hosts have conviction that no discipline has all of the answers, and so it&#8217;s important to bring people from across many different disciplines to discuss, which is a mindset that I like. A good friend of mine who runs a nonprofit related to career skilling called Career Village went last year and said it was amazing. He highly, highly recommended. He nominated me to apply, which I appreciated, and the organizers felt like I would be a net addition to the conference which I also appreciate and so I&#8217;m gonna go and there&#8217;s a bunch of formal sessions and a bunch of just mingling around with different people and there&#8217;s some there are some reasonably big names there and I&#8217;m sure a bunch of other interesting people who I haven&#8217;t heard of but look forward to meeting.</p><p><strong>James:</strong> Terrific. We&#8217;re coming to the top of the hour. Anything else we should talk about? I feel like we go for another hour.</p><p><strong>Ryan:</strong> Yeah. Let me think of some hard questions for you that you can play back to me. Let&#8217;s start at the foundation. One, what&#8217;s your P doom and why? Two, what do you think AI does to economic growth and why? And three, how real do you think this sort of RSI recursive self-improvement is gonna play out to be in the coming years?</p><p><strong>James:</strong> I think P Doom is very low.</p><p>P Doom to me is correlated entirely with your beliefs around geopolitics. Which is if you have major nation states using AI to attack each other, that gets really scary. If you don&#8217;t that feels a lot better to me. And even some of the scenario like the <a href="https://openai.com/index/hugging-face-incident-and-the-road-ahead/">hugging face attack</a>, people got scared about that, but yeah, sure, the agents went rogue only after they removed all the controls as an experiment. Okay, maybe you shouldn&#8217;t do that. I think there was a little bit of a kerfluffle based on <a href="https://www.noahpinion.blog/p/heres-how-were-all-going-to-die">Noah Smith&#8217;s blog</a> about using AI to engineer bioweapons, then <a href="https://blog.genesmindsmachines.com/p/im-sorry-youre-not-going-to-die-from">another group of people who actually understood the virus supply chain</a> pointed out how unlikely that should be. So I&#8217;m not incredibly concerned about P doom. I&#8217;m more concerned about P degradation, which was a little bit what you were saying about, it&#8217;s easier to think less with AI.</p><p>Also, I&#8217;m very worried that large language models can be very sycophantic. So I worry that people will be more comfortable, especially children and adolescents, more comfortable speaking to large language models than will be speaking to other human beings who have their own agendas and are not seeking to placate you. So that&#8217;s a bigger worry for me. What was the second question? Oh, economic growth?</p><p><strong>Ryan:</strong> Economic growth.</p><p><strong>James:</strong> I&#8217;m broadly speaking bullish. The way I think about it is we have organized factories and <a href="https://www.prosaictimes.com/p/agent-serena-stopped-the-yak-shaving">chaotic offices</a>.</p><p>So over the past 50 years, as a result of <a href="https://www.prosaictimes.com/p/ai-enabled-software-engineering-is">things like lean</a>, there&#8217;s been a massive productivity improvement in factories. A car of today is infinitely better than a car of the 1960s. And we still have a lot of chaos in office offices, driven, I think, <a href="https://www.prosaictimes.com/p/the-world-is-entropic-and-deterministic">by entropy</a>. And I think Gen AI because it&#8217;s less rigid than other forms of automation, gives us the opportunity to Apply some of the efficiency improvements we&#8217;ve seen in more production type processes to more knowledge type processes, which is a bigger and bigger part of the economy. And I am a bit skeptical of recursive self-improvement. I wouldn&#8217;t claim to be an expert on this, but I tend to make the case that large language models, for example, are structured very differently from the human brain or are infinitely more simple architecturally and therefore we are talking about an incredibly good model that predicts output in a way that&#8217;s incredibly useful and is an incredibly valuable tool, but not in any way, shape or form approaching sentience.</p><p>Does that make sense at all?</p><p>But who knows whether I&#8217;m right or wrong, or any closer to right than anyone else.</p><p><strong>Ryan:</strong> Yeah. I share your view on P Doom, and I don&#8217;t know if you&#8217;ve seen the <a href="https://www.dallasfed.org/research/economics/2025/0624">FT chart</a>, the title of which is something like, AI could end scarcity or end humanity or increase GDP growth by zero point two percent per year.</p><p><strong>James:</strong> Yeah. It&#8217;s like it&#8217;s all it&#8217;s a little bit like we could either win or lose this football game or there might be a tie.</p><p><strong>Ryan:</strong> Yeah, it&#8217;s a fantastic chart and I&#8217;m firmly in the middle case myself. Maybe point seven percent, not point two percent, but there&#8217;s a lot of bottlenecks other than intelligence.</p><div><hr></div><p><em>Yeah, it&#8217;s a fantastic chart and I&#8217;m firmly in the middle case myself. Maybe point seven percent, not point two percent, but there&#8217;s a lot of bottlenecks other than intelligence.</em></p><div><hr></div><p><strong>James:</strong> Yeah, I worry about political resistance to AI, but if we surmount that, I think it could be a hundred basis points. Which I suppose is not that far from your seventy. And let me tell you something, a hundred basis points compounded over twenty years, that&#8217;s a lot of benefit to a lot of people.</p><p><strong>Ryan:</strong> could underpin part of our getting to the next century of plenty.</p><p><strong>James:</strong> Exactly so and could solve a lot of problems. for example, I love that you can sometimes see in the same publication, in succeeding issues, one issue saying, Oh my god, AI will take all the jobs and nobody will have a job anymore, and the next issue we have an aging population and who will do all the work. So maybe these things will balance each other out.</p><p><strong>Ryan:</strong> Yeah, and my personal view is I think AGI is basically here. I think the current models are sort of effectively, as smart as humans on a bunch of stuff. And yet we have unemployment the US where this is most prevalent is still <a href="https://www.bls.gov/news.release/empsit.nr0.htm">under five percent</a>. So there&#8217;s a long time for diffusion. I think by the way, the recent I think it was an <a href="https://www.mckinsey.com/mgi/our-research/workforce-in-motion-skills-and-pathways-to-future-jobs-in-the-united-states">MGI piece</a> around, the question is the pace at which workers can reskill.</p><p><strong>James:</strong> Yeah. Okay. Thank you so much. This was great. You&#8217;re gonna have to come back. We&#8217;re gonna have to have a another discussion after you go to the conference. And there&#8217;s a whole bunch of things we touched on.</p><p><strong>Ryan:</strong> I would be honored and delighted to. Thank you so much, James.</p><p><strong>James:</strong> All right.</p><p>[1] McKinsey CTO Sven Blumberg has been evaluating the relative merits of hosted versus open-weight models. Naturally open-weight models will be important in some circumstances for data sovereignty reasons. But the cost per token may be much smaller than initially appears when you take all the engineering and support costs into account.</p><p>[2] We recorded this shortly before <a href="https://thecurve.goldengateinstitute.org/">The Curve</a>, which ran October 2&#8211;4, 2026. &#8220;This weekend,&#8221; and &#8220;after you go to the conference,&#8221; refer to that event.</p>]]></content:encoded></item><item><title><![CDATA[A system is just a very fast legal pad]]></title><description><![CDATA[Reducing the minimum viable scale for digitization and giving the cobbler&#8217;s children feet]]></description><link>https://www.prosaictimes.com/p/a-system-is-just-a-very-fast-legal</link><guid isPermaLink="false">https://www.prosaictimes.com/p/a-system-is-just-a-very-fast-legal</guid><dc:creator><![CDATA[James Kaplan]]></dc:creator><pubDate>Sun, 18 Oct 2026 21:01:49 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/221021247/34cbb58b405753ebaba1859c707116fe.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>&#8220;It&#8217;s a legal pad, a very fast legal pad.&#8221;</p><p>The project manager was older (must have been in his thirties!), upper class and British. [1] He had worked at Coba-MID [2] before coming to <a href="https://accountancyage.com/1997/07/02/profile-enterprise-transformation/">Deloitte &amp; Touche Consulting Group</a>. [3]</p><p>As we sat in a conference room in Denver, preparing to embark on one of the sillier CRM adventures of the 1990s, he had asked me &#8220;What can a computer do?&#8221; [4]</p><p>What form of information technology did the project manager trust? The yellow legal pad. He brought one to every meeting and carefully worked through every issue on its pages.</p><p>So I explained: &#8220;Think of a software program on a computer as a very fast legal pad. If you can do something on a legal pad, you can do it much more quickly via a software program. If you can&#8217;t do it on a legal pad, you can&#8217;t do it with a software program.&#8221;</p><p>He nodded. The products of the British public school system and Northern Valley Regional High School [5] had achieved shared context. [6]</p><p>Agentic ideologues will demand I retire my metaphor. They will argue that probabilistic reasoning allows us to build systems that we can&#8217;t reduce to a set of instructions on a legal pad. [7] And if you&#8217;ve never sat in a conference room, with worried professionals asking each other why the release can&#8217;t pass the bloody test cases, you might believe that.</p><p>Yes, generative AI allows us to do things we couldn&#8217;t do before. But we don&#8217;t have to put probabilistic reasoning in the core transaction flow.</p><ul><li><p>Have a mess of unstructured data? You don&#8217;t have to interpret it afresh every time someone needs an answer. Use agents to extract and structure the information, validate the results, and load them into a database (possibly a graph). Then use fast, reliable Cypher or SQL queries at run-time.</p></li><li><p>Have thousands of pages of standard operating procedures outlining untold numbers of paths through and exceptions to a process? Use agents to derive explicit business rules, then test and validate those rules using decades&#8217; worth of software quality assurance practice.</p></li><li><p>Users frustrated by having to tab through dozens of fields on several screens for data entry? Let them enter data as free text. Use an agent to map that input to the required fields, present the proposed transaction for approval, and let conventional software execute it. [8]</p></li></ul><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!IT5K!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76e0eb5-4492-4d00-a1ce-2fa94dfca6d1_1784x882.jpeg" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!IT5K!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76e0eb5-4492-4d00-a1ce-2fa94dfca6d1_1784x882.jpeg 424w, https://substackcdn.com/image/fetch/$s_!IT5K!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76e0eb5-4492-4d00-a1ce-2fa94dfca6d1_1784x882.jpeg 848w, https://substackcdn.com/image/fetch/$s_!IT5K!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76e0eb5-4492-4d00-a1ce-2fa94dfca6d1_1784x882.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!IT5K!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76e0eb5-4492-4d00-a1ce-2fa94dfca6d1_1784x882.jpeg 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!IT5K!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76e0eb5-4492-4d00-a1ce-2fa94dfca6d1_1784x882.jpeg" width="1456" height="720" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/a76e0eb5-4492-4d00-a1ce-2fa94dfca6d1_1784x882.jpeg&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:720,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:317484,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/jpeg&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.prosaictimes.com/i/221021247?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76e0eb5-4492-4d00-a1ce-2fa94dfca6d1_1784x882.jpeg&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!IT5K!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76e0eb5-4492-4d00-a1ce-2fa94dfca6d1_1784x882.jpeg 424w, https://substackcdn.com/image/fetch/$s_!IT5K!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76e0eb5-4492-4d00-a1ce-2fa94dfca6d1_1784x882.jpeg 848w, https://substackcdn.com/image/fetch/$s_!IT5K!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76e0eb5-4492-4d00-a1ce-2fa94dfca6d1_1784x882.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!IT5K!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa76e0eb5-4492-4d00-a1ce-2fa94dfca6d1_1784x882.jpeg 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Now consider enterprise technology. Executives in other business functions marvel at how manual IT remains, despite employing armies of people whose business is automation. [9] Technology environments are incredibly intricate machines that (for most business processes) must work even in the face of a terrifying array of edge cases.</p><p>That&#8217;s why we have a whole discipline -- change control -- that traditionally involves people sitting on a videoconference asking each other &#8220;Well, what might this break?&#8221; It&#8217;s fun, even if it might breed a little neuroticism. [10]</p><p>If you&#8217;re prioritizing alerts, kinda-sorta may be good enough. If you&#8217;re automating server management, it isn&#8217;t. You have to demonstrate that the automation will work. It is a hell of a lot harder to do that if you don&#8217;t understand the internals.</p><p>I think Serval rests on this proposition. The company helps operational users &#8212; citizen developers &#8212; turn their knowledge of business processes into executable code. It also seeks to provide the testing, deployment, version control, permissions, and other infrastructure required to operate that code reliably. [11]</p><p>Many of Serval&#8217;s early implementations have been in IT, [12] itself an enormous business domain populated by thousands of operators and managers who aren&#8217;t necessarily software engineers. [13]</p><p>In today&#8217;s Prosaic Times, I discuss all this with Serval CTO Alex McLeod. We don&#8217;t endorse companies or technologies. But I like hearing directly from builders about the world they intend to create.</p><h4><strong>Why IT stayed manual</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>Automating a task takes far longer than doing it by hand once, and time-pressed teams default to manual work</p></li><li><p>Handling exceptions can consume more effort than automating the core process</p></li><li><p>IT&#8217;s thousands of applications and configurations turn operating leverage against it</p></li></ul><div><hr></div><p><strong>James Kaplan:</strong> Good afternoon. This is James Kaplan with another Prosaic Times podcast. I&#8217;m here with Alex McLeod, from &#8212; and I&#8217;m gonna try and pronounce this correctly &#8212; Serval.</p><p>And he&#8217;s the CTO there. And we look forward to having a whole bunch of discussions about technology automation of IT operations and of security. How&#8217;s that sound, Alex?</p><p><strong>Alex McLeod:</strong> That sounds great. Looking forward to it.</p><p><strong>James:</strong> All right, terrific. You wanna tell us a little bit about yourself and a little bit about the company?</p><p><strong>Alex:</strong> Yeah, sure thing. So yeah, my name&#8217;s Alex McLeod. I am the CTO and co-founder of Serval.</p><p>My background is very much in startups and building companies from the ground up. And I spent a number of years at Verkada previously helping them build new product lines, until starting Serval about two and a half years ago. And Serval itself is an automation platform that helps anyone at a company automate away kind of repetitive work and toil so they can get back to meaningful work.</p><p>We do often enter and start with IT teams at businesses and help them automate employee support. It&#8217;s a big part of what we do. And then we will often move from there into other departments like HR, legal, finance, security, engineering, and so on.</p><p>And it&#8217;s been a fun journey and excited to chat about it.</p><p><strong>James:</strong> So sometimes I joke that, with regards to IT, it&#8217;s not that the cobbler&#8217;s children don&#8217;t have shoes. They barely have feet. I think most people who have not worked in large enterprise technology organizations would be astonished by how much manual activity there has been historically.</p><p>That&#8217;s gotten better over the years. But talk to us a little bit about that. Why is there so little automation in IT historically?</p><p><strong>Alex:</strong> Yeah. That&#8217;s a great question. The reason for that is it takes very significantly longer to automate something than to just do it manually one time.</p><p>And when people are pressed for time, they will then go and kind of choose to do the manual version of that task. So, as an example, you might have a task like resetting an MFA factor for a device. This is often a problem when new iPhones come out or new phones come out, and that may take 10 minutes, 20 minutes per case to handle manually. The automation of that historically could take a long time.</p><p>It could take days, weeks. It really depends on the organization. I&#8217;ve seen cases where the internal process, although it sounds simple on the surface, just reset the MFA factor, can be very nuanced, and there can be lots of different situations that you have to deal with and account for, and exception cases that you can&#8217;t really, maybe, require kind of thinking through up front. And so historically building those automations and deploying that can just take orders of magnitude longer than actually just manually resolving it.</p><div><hr></div><p><em>The reason for that is it takes very significantly longer to automate something than to just do it manually one time. And when people are pressed for time, they will then go and kind of choose to do the manual version of that task.</em></p><div><hr></div><p><strong>James:</strong> The way I sometimes think about it is that operating leverage has been sometimes hard to come by in IT, which is maybe one way to say it. Let&#8217;s take a credit card.</p><p>In many cases, at least in consumer credit cards, one credit card provisioning action looks like the last ten thousand. But in an IT environment where you have thousands of applications and God knows how many configurations, the operating leverage dynamics can work against you. Is that a fair way of thinking about it?</p><p><strong>Alex:</strong> I think that&#8217;s a fair way of thinking about it. I also think that when it comes to automation, the exception cases are what really kind of just take up all the time.</p><p><strong>James:</strong> Well, exceptions are the enemy of operating leverage, right? And when it&#8217;s version four point two of the OS, we have to configure something differently than when it&#8217;s version four point one of something or other, right? Or when it&#8217;s in this location &#8212; or this country &#8212; we have to deal with the firewall rules or something, right?</p><p><strong>Alex:</strong> Right, exactly. A hundred percent. That&#8217;s a good way to think about it.</p><h4><strong>DevOps and the operator problem</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>DevOps made operational procedures repeatable but did not remove the effort of automating them</p></li><li><p>Automating takes a different mindset and skill set than operating</p></li><li><p>Agents may allow operators to encode their own process knowledge without becoming professional software engineers</p></li></ul><div><hr></div><p><strong>James:</strong> So how did DevOps change some of that? How much did DevOps change the dynamics, right? Because in DevOps we started to push sysadmins, instead of doing things, to write scripts to do things. Now that was imperfect, but how did DevOps change that?</p><p><strong>Alex:</strong> I think, broadly, it helps a lot to have this kind of like engineering or automation mindset to solving a lot of problems. And I think the kind of like DevOps mentality of how do we make these operational procedures repeatable and consistent and minimize kind of like one-off cases, I think that is 100% the right mentality. And it certainly helps.</p><p>It doesn&#8217;t perfectly resolve the situation of the &#8212; it takes time to kind of think through how do I automate something. And I think it takes a different kind of mindset as well, and it takes a bit of a different skill set. And so it&#8217;s directionally correct, but still there&#8217;s a lot of energy and effort required to go from more of a manual world into an automated world.</p><p><strong>James:</strong> You imply something really interesting there. Okay, we always have debates. Who&#8217;s best positioned to think through automation?</p><p>Is it the business owner who&#8217;s close to the business process? Or is it someone who understands the discipline of automation? And you&#8217;re saying we still have that same tension inside the four walls of IT, because there may be a quote-unquote operator who is close to an operational process, but that person may not have an engineering mindset required to automate that process.</p><p><strong>Alex:</strong> Yeah, I think that the engineering mindset can certainly be adopted and learned. I mean, one thing that we are very much doing and seeing with our platform Serval is that we&#8217;re enabling people at companies to be builders, to be engineers and to operate with that kind of mindset. And our goal is really to give the operators &#8212; the people that are closest to a business process and have the context of all the kind of like messy business rules and complexity &#8212; have that in mind.</p><p>And also understand the user as well, or the end customer, whether that&#8217;s an internal customer or otherwise. Have that deep understanding. And then we want to give them the tools to encode that into a system like ours, so that they can automate and get themselves more leverage, basically. We think that&#8217;s the ultimate best situation and direction.</p><p>And then the mindset of, well, how do you engineer this? How do you take this messy process and convert that into something repeatable or into a workflow of some kind? That is where we&#8217;re leaning on LLMs and agents to help give people that skill set and that capability. And so our view is that&#8217;s the direction.</p><p><strong>James:</strong> Yeah, I joke that I want a large language model pre-trained on the principles of lean operations. Or a small language model pre-trained on the principles of lean operations. I also joke that I want a large language model that has only ingested good code from the internet as opposed to bad code, but that may be a little bit of an idealistic hope, if an impractical one.</p><p><strong>Alex:</strong> I think that&#8217;s a great idea. It&#8217;s also &#8212; I think what my learning over time is that so much of this stuff is subjective, and there&#8217;s so much like taste that is still important. And that&#8217;s why it&#8217;s always a better-together situation with large language models and the human experts.</p><h4><strong>User experience beyond the chrome</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>At a forum of about sixty-seven CTOs, nobody raised a hand for a beautiful IT experience and nearly everyone raised one for frustrated users</p></li><li><p>Teams can reinvest the toil automation removes in experience, not only in output</p></li><li><p>Good experience means fewer fields to tab through, and the next step is preventing the request altogether</p></li></ul><div><hr></div><p><strong>James:</strong> Yeah. It&#8217;s funny.</p><p>We had our enterprise CTO forum yesterday; we had about sixty-seven CTOs together. [14] We were talking about various things, including user experience, and in one of the plenary sessions I asked the assembled group, how many of you think your users believe they get a beautiful experience from IT? And nobody raised their hands.</p><p>And then I said, how many people feel their users are frustrated with the experience they get from IT? Pretty much everyone raised his or her hand. And I think you make a really interesting point.</p><p>Listen, an architect can design a building that is either soul deadening or inspiring, and we can either define software that is not only productivity enhancing or productivity detracting, but also is soul deadening or, if not inspiring, at least pleasant.</p><p><strong>Alex:</strong> Yeah, a hundred percent. And the teams that we work with, they really care.</p><p>They want to create that pleasant experience. They deeply care about that. It&#8217;s just about giving them the tools to make that possible, and giving them the time back effectively by making it as easy as possible to get to a great user experience, because that&#8217;s what&#8217;s hard.</p><p><strong>James:</strong> Yeah, that was some of the discussion we got into, which is if you can reduce the toil associated with automation, some of that you may drop to the bottom line, some of that may be used to do more automation and automate more things, but some of that you might be able to reinvest in &#8212; let&#8217;s actually think about the user experience rather than just slamming it home in order to meet a production deadline.</p><p><strong>Alex:</strong> Yeah, a hundred percent correct. And as I say, we&#8217;re seeing that across a lot of our customers at the moment, in many cases customers who have kind of existing automations built out in other platforms, and they&#8217;re looking at it and they&#8217;re like, &#8220;This is not it. This is not a great experience.&#8221; And they care.</p><p><strong>James:</strong> Yeah, and so much of what we talk about great experience, I fear, sometimes focuses on the chrome. What&#8217;s the fonts, what&#8217;s the colors, as opposed to, gee, are we really asking people to tab through forty fields to automate one thing? I don&#8217;t care what the fonts look like. That&#8217;s gonna be painful, right?</p><p><strong>Alex:</strong> Exactly. I think some of the organizations we&#8217;re working with kind of go a step further. And I think this is where it&#8217;s really going: you can make the experience of requesting something or getting help very, very easy and super simple.</p><p>And that is important. But you can also be thinking about how do I proactively prevent something or automate something away so that the user doesn&#8217;t even have to ask for it in the first place. And we&#8217;re really excited about that. We&#8217;ve built a lot of functionality around that, and we&#8217;re seeing that is a great direction.</p><div><hr></div><p><em>You can make the experience of requesting something or getting help very, very easy and super simple. And that is important. But you can also be thinking about how do I proactively prevent something or automate something away so that the user doesn&#8217;t even have to ask for it in the first place.</em></p><div><hr></div><h4><strong>From drag-and-drop to code</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>Agentic coding is the capability that made this possible, and it arrived only a couple of years ago</p></li><li><p>Drag-and-drop builders constrain logic, while code is compact, reusable, and handles conditionals and errors</p></li><li><p>An agent abstracts the syntax and preserves the semantics</p></li></ul><div><hr></div><p><strong>James:</strong> So would it be fair to say that what you&#8217;re trying to do would have been impossible two years ago or three years ago?</p><p><strong>Alex:</strong> Without question. I think it just became possible. We were at a good time where it just started becoming possible.</p><p><strong>James:</strong> And obviously we talked about the maturity of large language models, but what specifically is the capability from a large language model that allows you to do what you do that would have been impossible three years ago? What&#8217;s the specific unlock?</p><p><strong>Alex:</strong> Agentic coding ability is basically what it comes down to. I mean, when we started Serval, the status quo for automation was &#8212; and I think largely still is &#8212; that if you want to automate something, you are building kind of like drag-and-drop workflows or automations, and you&#8217;re kind of piecing together logic visually. And maybe you&#8217;re scripting to some extent.</p><p><strong>James:</strong> Which I will say &#8212; and I&#8217;m a little bit older than you &#8212; I hated that in the nineteen nineties. I recall in the mid nineteen nineties trying to explain to people, I can type code more quickly than I can drag and drop things onto it. And I can achieve a degree of reusability with textual code that is probably all but impossible once I&#8217;m dragging things around. Well, maybe if the drag and drop is just a front end to textual code, but stuff like Macromedia Director, there was no reusability, there was no ability for abstraction.</p><p>Everyone&#8217;s like, gee, we have a GUI. No, no, no. That doesn&#8217;t help that much. Sorry for the rant.</p><p><strong>Alex:</strong> A hundred percent. No, I totally agree. It&#8217;s like &#8212; programming is incredibly flexible, and UI is actually kind of constraining, but maybe more approachable.</p><p>And so we had this idea early on of, well, why can&#8217;t I just chat with an agent that goes and writes code that represents my logic? Code is super flexible, it&#8217;s very compact representation of logic. I get all these great built-in primitives from the programming language, like conditionals and loops and error handling and all that good stuff. And that ability to do that &#8212; so you didn&#8217;t have to drag and drop and build a workflow visually, but you could actually just chat within something, write out a few sentences, and it would go and build it for you &#8212; became possible a couple years ago.</p><div><hr></div><p><em>Code is super flexible, it&#8217;s very compact representation of logic. I get all these great built-in primitives from the programming language, like conditionals and loops and error handling and all that good stuff.</em></p><div><hr></div><p><strong>James:</strong> What I&#8217;d say is you&#8217;re preserving semantics but abstracting syntax. I don&#8217;t know about you, but I can never &#8212; it&#8217;s like, what the hell, what order do they want the parameters in? Let me go look that up, which is a giant pain in the neck, but the ability to abstract away that syntax but still retain the flexibility the code allows is quite an important thing.</p><p><strong>Alex:</strong> 100%. I think the other thing as well that is very important is, as I mentioned up front, exception cases are where a lot of the problems come in with automation. And that&#8217;s where large language models are just incredibly valuable: you want to use code and determinism for certain parts of automation.</p><p>But you also want to have the ability for there to be kind of like reasoning and judgment for other aspects of automation. And so I&#8217;ll give you an example. If I am coming into my IT help desk and I&#8217;m like, &#8220;I need to reset my Okta password,&#8221; and I send a screenshot, and actually the screenshot is of maybe a Google Workspace login.</p><p>And the user maybe has gotten confused. You want to have a system that can have some amount of judgment to be like, &#8220;That looks like Google Workspace. I&#8217;ll trigger the Google Workspace automation instead.&#8221;</p><h4><strong>Judgment at the edges, determinism at the core</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>Has the field overindexed on non-deterministic processing?</p></li><li><p>No one can predict every failure in a chaotic environment. Edge cases get judgment, and execution stays deterministic</p></li><li><p>Deterministic tools enforce authorization and rate limits, and can reject an invalid request or escalate it to a human</p></li></ul><div><hr></div><p><strong>James:</strong> This is fascinating to me. This to me is a very fundamental question. And one of the reasons I want to interview you guys, interview you, excuse me, is I worry that we&#8217;ve overindexed on non-deterministic processing.</p><p>And what&#8217;s interesting to me, as I understand it, is that what you guys do a lot of is, in effect, okay, let&#8217;s have non-deterministic interaction between the analyst or the engineer or operator and the tool, which is constructing code. But then we construct deterministic code, and we can apply 30 years of software quality assurance practice to make sure it works. And I don&#8217;t know about you, but I sort of like that idea, especially if you&#8217;re touching systems in production.</p><p>And that to me is super exciting, but you raised something else. So I want to test the hypothesis now, because one of the joys of agentic coding is the automation of error handling. Because I don&#8217;t know about you &#8212; I mean, what&#8217;s worse than sitting down and thinking through every single error condition and trying to code those? That&#8217;s soul deadening, right?</p><p>Now, you challenged a hypothesis of mine in an interesting way, which is I would assume that at design time or at build time, you would provide an instruction to the agent to sort of say, okay, here&#8217;s the 50 possible edge cases. Go create code to trap each one of those edge cases.</p><p>Let&#8217;s say, I don&#8217;t know, browser version. Go research the zillion different outdated browser versions you might possibly have and create some error catch, error handling code for each browser condition. And that&#8217;s all deterministic, right?</p><p>But you&#8217;re saying you could even go one step further and even if the core of the script is deterministic, you might have some, I don&#8217;t know, ingestion, routing, what have you that is non-deterministic. Because even with the instruction, you may not be able to figure out all the potential errors. That&#8217;s a really interesting point.</p><p><strong>Alex:</strong> I think that when a system becomes complex enough or chaotic enough, it becomes entropic enough.</p><p><strong>James:</strong> Entropic enough is the term I use. Actually, the system isn&#8217;t entropic.</p><p>The environment around it is entropic. We build system complexity to deal with environmental entropy. That&#8217;s maybe the right way to describe it, right?</p><p><strong>Alex:</strong> Exactly. And I think when a system becomes entropic enough, it becomes effectively impossible to predict every failure case and every situation that can go wrong. I remember Netflix had this popular idea of chaos engineering, maybe it was a decade ago, where they recognized that within their kind of software systems, where there&#8217;s enough services and enough interactions between services that you can no longer kind of upfront predict the different failure modes. So instead they would inject failure modes into the chaotic system and see how different parts of the system would react, right?</p><p><strong>James:</strong> Okay. Every banking CTO watching this is now screaming at the screen: that&#8217;s fine to do with video streaming, not with high dollar volume transactions. It&#8217;s like, there was a glitch in my video stream, let me hit play again.</p><p><strong>Alex:</strong> Totally. I totally agree. But I think that the core idea there is that as entropy increases, it becomes impossible to predict failure modes. So you do want to test resilience to failure.</p><p>It&#8217;s an interesting way of thinking about things. And I think that&#8217;s true in all kind of like IT operations and internal operations at businesses: the environment is just so chaotic and complex that you can never predict every single failure mode. And so you want to encode some of those, but you also want to give some amount of freedom or flexibility to an intelligent entity, which is an LLM, to deal with the edge cases that you&#8217;re comfortable with, right? So the example I gave you of, like, resetting a password.</p><p>You don&#8217;t want to connect the LLM directly into all of your business systems and say you can take any action you want. But if it&#8217;s got two tools, one for resetting Okta password, one for resetting a Google Workspace password, it&#8217;s okay if it picks one or the other and has some intelligence there. As long as when it executes that tool, the reset happens very deterministically.</p><p>One thing you might want to be deterministic about is, you might want to say, &#8220;A user is allowed to reset their password anytime they want &#8212; sorry, anytime as long as they haven&#8217;t reset it in the last three hours.&#8221; You want some kind of rate limiting, and you want that logic encoded into the tool. And that&#8217;s where you want code literally checking, when was the last time they did a reset? &#8220;Okay, it&#8217;s been less than three hours &#8212; fail.&#8221;</p><p>That&#8217;s kind of authorization logic or rate-limiting logic that you really want to bake into the tool. But the selection of which tool to use in which situation, it&#8217;s okay to allow some amount of reasoning and intelligence to make that selection. That&#8217;s how I think about it.</p><div><hr></div><p><em>You don&#8217;t want to connect the LLM directly into all of your business systems and say you can take any action you want. But if it&#8217;s got two tools, one for resetting Okta password, one for resetting a Google Workspace password, it&#8217;s okay if it picks one or the other and has some intelligence there. As long as when it executes that tool, the reset happens very deterministically.</em></p><div><hr></div><p><strong>James:</strong> What I&#8217;m hearing from you is &#8212; what you&#8217;re suggesting is the combination of non-deterministic routing and deterministic execution can feel okay from a risk and resiliency standpoint. Because if, worst case, you make a bad routing decision, the deterministic code says, &#8220;I can&#8217;t do anything about this,&#8221; and it gets kicked back to a human operator, right?</p><p><strong>Alex:</strong> Exactly. And you can be thoughtful about what are the boundaries around which I&#8217;m comfortable allowing a level of judgment and reasoning. And that, we see as like combining the best of all worlds together, to automate more processes kind of in a really safe manner.</p><p><strong>James:</strong> Yeah, I mean, the other thing I&#8217;m thinking about is a bit of a tangent. I wonder if we&#8217;re going to see more modeling of complex technology environments, which is &#8212; you can think about a technology environment as a graph, where every piece of technology, every system, every application is a node, and every network link and every system call is an edge. And then, in effect, you can have a non-deterministic chaos monkey that figures out the tests. A non-deterministic virtual chaos monkey to figure out where you might possibly break the system, to sort of figure out the edge cases you need to automate around.</p><p><strong>Alex:</strong> I think that&#8217;s a great idea. I think that, like, simulating the full environment and simulating, yeah, what goes wrong if we enable a user to have this level of flexibility, and where should we take that flexible decision and maybe make that non-flexible and kind of encode that in a deterministic system? And where is something deterministic that really could be flexible and non-deterministic? I&#8217;m seeing a lot of that today.</p><p>We&#8217;re seeing, actually, and working with a number of companies that are trying to simulate business systems. So, like Workday, Okta, Slack. So you can actually iterate and test your work in a simulated environment. So you&#8217;re not testing it in a production environment, which is exciting.</p><p><strong>James:</strong> Yeah. I mean, I&#8217;d like to see more people even take that up a level from the operational level to the strategic level, so they can test business strategy. But now we&#8217;re really far afield.</p><p>It&#8217;s a fascinating time, right? So much less depressing than fifteen years ago, when there were like six vendors and it was a giant oligopoly, right? Or twenty years ago.</p><h4><strong>Why not just use a coding agent?</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>If frontier labs absorb enterprise software, who needs a platform?</p></li><li><p>Agent-written scripts still need deployment, version control, system access, permissions, approvals, and someone on call</p></li><li><p>Writing code is a small share of running software at scale, thirty years of discipline for managing code has to evolve for agents, and Serval aims to package that discipline for people who are not engineers</p></li></ul><div><hr></div><p><strong>James:</strong> One other thing we discuss as we talk about an oligopoly &#8212; what we discussed at the CTO forum &#8212; is how much of the world will wind up being controlled by the frontier model. So if you go back ten years or maybe eight years, there were a bunch of people saying the entire enterprise software market will disappear and will be entirely owned by the cloud service providers, and as of yesterday morning that had not happened.</p><p>Now there are other people saying, gee, the entirety of the enterprise software market will be consumed by the frontier labs. Now, this is actually maybe a little bit more plausible a hypothesis, because somebody, perhaps wrongly, might listen to this conversation and say, okay, I have my favorite coding agent.</p><p>Why do I need a third-party platform? I can take advantage of agentic software development all by myself. I could tell my coding agent to develop error trapping for 50 different browser versions and what have you. So how do you think about what will get done, in terms of, say, IT automation, via coding agents versus more specialized platforms or more targeted &#8212;</p><p><strong>Alex:</strong> Yeah. So I mean, the way that I think about it is you need a full platform like ours to effectively deploy those automations and maintain them over time. So in the example you&#8217;re talking about there, of like, well, can I just use a coding agent and build out some scripts or things like that to solve these different cases?</p><p><strong>James:</strong> And clearly people are doing that in various places. That is happening.</p><p><strong>Alex:</strong> Yeah, for sure. And it&#8217;s like, yeah, you can build out those scripts, but then what do you deploy them to? How do you version control those things?</p><p>And then when they&#8217;re deployed, how do they get access to your business systems? And then if someone wants to make a modification to that script, then how does that work? And what permissioning and role does that person need to make that modification?</p><p>And then what if you need an approval procedure through to execute a particular script? Well, how is that executed? And how does that get routed to the right person?</p><p>And then what happens if, through all those things, something goes wrong in the middle of the night, right? Like, the writing of software is &#8212; I think we are all relearning, maybe &#8212; a small percentage of the kind of effort required and kind of work required to deploy and run software and maintain it over time at scale. And so I do think you need coding agents. So coding agents are incredibly powerful, but then you need all of the different kind of systems and capabilities around them to leverage that capability effectively, which is certainly what we provide at Serval and what we focus on.</p><div><hr></div><p><em>You can build out those scripts, but then what do you deploy them to? How do you version control those things? And then when they&#8217;re deployed, how do they get access to your business systems?</em></p><div><hr></div><p><strong>James:</strong> Okay. That&#8217;s interesting.</p><p>That&#8217;s a little bit different from the answer I thought you were gonna give. I thought you were gonna give a more tactical answer, which is, hey, if you&#8217;re gonna automate IT stuff, you need to interrogate and control AWS, and you need to control ServiceNow and a million different things. And you guys had &#8212; and maybe you have done this &#8212; some degree of understanding of the object models and the API models, and whatever MCPs have been exposed that allow you to avoid a lot of trial and error in manipulating much of that stuff.</p><p><strong>Alex:</strong> Yes, which is also definitely true. But I think it&#8217;s more &#8212; no, for sure, without question, that is definitely true. It is just like there&#8217;s so many pieces around the deployment and execution of software that are critical. And so for a platform like &#8212; sorry, go on.</p><p><strong>James:</strong> And non-trivial, I would add. What you&#8217;re saying is really interesting.</p><p>It&#8217;s quite a big thing, because what you&#8217;re saying, and I would agree with this, is we&#8217;re starting to do software development differently, right? And much of the discipline that the world developed over the past 30 years is going to need to evolve. Not all of it.</p><p>We&#8217;re gonna build on top of it, it&#8217;s not all gonna get thrown out, but we&#8217;re gonna need to build on top of it, because contexts, skills &#8212; how do you version skills that can invoke scripts? I mean, a million things. And what you&#8217;re saying is you guys aspire to provide some of the discipline that the world has developed in managing code over the past 30 years to the process of managing agentic development and all the stuff that lives above code in this case. Okay.</p><p><strong>Alex:</strong> Yes. Exactly.</p><p>And we&#8217;re actually taking a lot of the &#8212; I guess the tools and techniques and capabilities that software engineers have relied on for a long time. We&#8217;re packaging that all up into our platform. And then we&#8217;re actually making that available to anyone at a company, in IT or beyond, so that they can make use of those different capabilities.</p><p>So we&#8217;re kind of packaging up all these capabilities that we have come to rely on as software engineers, and techniques we&#8217;ve come to rely on as software engineers, into a platform that lets people who are not traditionally software engineers automate things at their company, to reduce that toil and get back to meaningful work. And that&#8217;s very much how we think about the entire Serval platform: it&#8217;s a software development system. You can have an entire software development lifecycle on top of Serval that includes code, it includes skills, it includes all configuration. It&#8217;s just that we&#8217;re making that available to maybe people who wouldn&#8217;t traditionally go through that software development lifecycle.</p><h4><strong>Guardrails for citizen developers</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>Builders range from vibe coders to Wall Street strats. A personal automation is low risk, but a password reset can hurt people</p></li><li><p>The critical skill is architecting a system in natural language, and SQL is a precedent for declarative programming</p></li><li><p>Generated code gets a constrained SDK, deterministic type checking, and LLM review</p></li></ul><div><hr></div><p><strong>James:</strong> It&#8217;s interesting because there&#8217;s two flavors of what we&#8217;ve been discussing. One flavor is for software engineers who need something, because it&#8217;s not like they&#8217;re doing the same thing that they were doing two, even three years ago.</p><p>Then in addition you have what &#8212; I hate the term vibe coder, but let&#8217;s say citizen developer, right &#8212; who is going to try and build things with some degree of discipline, as opposed to just sitting down and saying, give me a report, and I don&#8217;t care how good or bad the underlying code is. And you guys are more focused on the second use case, the citizen developer? Is that a true statement?</p><p><strong>Alex:</strong> Yeah, we&#8217;re certainly enabling that, that kind of individual. Again, often those people maybe are in an IT department, but they may be in other departments as well. We&#8217;re enabling them to have automation capabilities so they can get to the outcome they want and kind of can encode the business rules and context that is important for their domain, without tapping a software engineer on the shoulder.</p><p><strong>James:</strong> So let me ask this question. How much do you think a citizen developer needs to understand in order to be competent? At one end of the spectrum is the vibe coder, right? At the other end of the spectrum &#8212; you know what a strat is?</p><p><strong>Alex:</strong> A strat.</p><p><strong>James:</strong> Yeah, they&#8217;re the folks in investment banks who sit on the trading floor and code trading algorithms. And they are people who deeply, deeply know capital markets and also in many cases are very good software engineers. Sometimes they have computer science backgrounds, sometimes they have finance backgrounds, and I think the history there is they put the capital markets person sitting next to the software engineer, and after all nobody could tell which was which. And that is often a fairly sophisticated person.</p><p>As you think about a citizen developer, where on the continuum do you think that person needs to be? How much does that person need to know to avoid hurting him or herself and people in the vicinity?</p><p><strong>Alex:</strong> Yeah. I think it depends on what you&#8217;re building and the scope of that.</p><p>If I&#8217;m building an automation for my personal use, I think anyone can do that, and you can iterate on it, and it&#8217;s just gonna use your credentials and your access that you have anyway. And there&#8217;s less of a long-term maintenance challenge. I think when you are &#8212;</p><p><strong>James:</strong> Fair. But if you&#8217;re building a password reset application, you could hurt people with that, right?</p><p><strong>Alex:</strong> Yeah, I think you need to have &#8212; again, I think it comes back to a bit of an automation mentality of how you think about what actions should be allowed, what shouldn&#8217;t be allowed, and less about, to your point, an ability to kind of take that mentality and the vision and convert that into syntax and code. That is less important now.</p><p>But you do need the mentality of being able to kind of architect a vision of how a system should work in your head and document it in natural language. I think that&#8217;s the critical skill.</p><div><hr></div><p><em>But you do need the mentality of being able to kind of architect a vision of how a system should work in your head and document it in natural language. I think that&#8217;s the critical skill.</em></p><div><hr></div><p><strong>James:</strong> Yes. Sometimes the metaphor I use is &#8212; and this is before even I remember &#8212; in the early nineteen eighties, when people started using SQL to build databases.</p><p>Before that, people actually hand coded the database, using procedural language, and then SQL, which I think we can describe as a declarative language, right? [15] You just describe the query you want. You&#8217;d still need to know SQL, but you ripped about, what, ninety percent of the effort out of constructing a database and what have you. [16] So I wonder if that&#8217;s the metaphor, that we&#8217;re moving more things to a declarative programming model, which is more democratic in certain respects.</p><p><strong>Alex:</strong> Absolutely. Exactly right.</p><p>And you declare in a language they&#8217;re all familiar with. And as, I guess, with declarative programming, you&#8217;re less concerned about how that gets executed under the hood, how it gets to that outcome. And so you need the system underneath to be robust, and that execution logic, I guess, to be very well thought through and tested internally.</p><p><strong>James:</strong> So let me ask this question. One thing I&#8217;ve noticed about coding agents &#8212; some of you may have a different experience &#8212; is they will hard code anything. They&#8217;re like the laziest software.</p><p>Unless you explicitly have instructions not to hard code things, they will hard code things. So how do you think about that enforcement of reasonable programming practice? Now obviously that&#8217;s a doable thing, and you can include checks for architectural smells and what have you, but is that something you do? How do you think about that?</p><p><strong>Alex:</strong> Yeah. The way that we approach that, in a lot of cases: for our system, we&#8217;ve built our own SDK. It&#8217;s a TypeScript SDK, and that is the library that basically the agent uses to write all of its code.</p><p>And as a result, the type of code that we&#8217;re expecting is relatively constrained. That enables us to do, one, a reasonable amount of sanity checking of the output, and that could be done by an LLM. But also, two, we can use fully deterministic checks, like just type checking, for example, which won&#8217;t necessarily catch hard coding, but it does catch misuse of an API, for example, where you pass a parameter that doesn&#8217;t actually exist, or a type for a value that is incorrect.</p><p><strong>James:</strong> Actually, large language models are pretty good at catching coding errors if you instruct them to look for the coding errors, which obviously many people neglect to do.</p><p><strong>Alex:</strong> Yes. And we can kind of encode those opinions into &#8212; and I wouldn&#8217;t say that&#8217;s necessarily opinion, but we can encode tastes and opinions into our system and our agent that runs on top of the Serval platform, which isn&#8217;t just a coding agent, because it&#8217;s writing code in a library that we have constructed, and we can see over time how best to write code that operates with our system. So that has a lot of advantages.</p><h4><strong>Adoption and the automation engineer</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>Customers range from &#8220;anyone can build anything&#8221; to tightly controlled, and the platform lets them set the level</p></li><li><p>A new role is emerging: the internal automation engineer who works as a forward deployed engineer for other departments</p></li><li><p>The role pairs platform expertise with business context</p></li></ul><div><hr></div><p><strong>James:</strong> One final question is, as you engage with people looking at your platform &#8212; and we&#8217;ve talked about a lot of complexity here, important stuff &#8212; to what extent do you think the people considering implementing your platform get that? And to what extent, at the other end of the continuum, is it like, hey, we&#8217;re gonna give users a platform and goodness will emerge? What&#8217;s the level of recognition that citizen development is good, but it&#8217;s not thoughtless, right?</p><p><strong>Alex:</strong> Yeah, for sure. And I think the idea of complete &#8212; anyone at a company can build anything &#8212; I think there are varying degrees of comfort with that or interest in that. In some businesses, that just is not going to make any sense.</p><p>And that&#8217;s not gonna be the direction they want. And for those companies, we are an incredible solution. We let you control the level of flexibility you have across an org.</p><p>I think that&#8217;s kind of a continuum, I guess, of comfort or interest in having automation being spread across the business. For a platform like ours, we give you all the controls and the capabilities and enable you to make the judgment calls of how those are kind of leveraged around the org. The thing we&#8217;re seeing as well, which I think is incredibly interesting, is the kind of rise of this automation engineer.</p><p>Which maybe that&#8217;s somebody who is in an IT department or otherwise at a business who becomes an expert in a platform like ours and uses it to automate password resets and the long tail of kind of IT issues, but then they become effectively like an internal forward deployed engineer for other parts of the business to go out and help them automate the capabilities or the issues in their environment. So they can then work with other people who have the deeper context that maybe aren&#8217;t as interested in being the automation engine themselves. They can work with those people to create tremendous amounts of value and give a lot of time back. And we&#8217;re very excited about that direction, and seeing that happen across our customer base.</p><div><hr></div><p><em>The thing we&#8217;re seeing as well, which I think is incredibly interesting, is the kind of rise of this automation engineer. Which maybe that&#8217;s somebody who is in an IT department or otherwise at a business who becomes an expert in a platform like ours and uses it to automate password resets and the long tail of kind of IT issues, but then they become effectively like an internal forward deployed engineer for other parts of the business to go out and help them automate the capabilities or the issues in their environment.</em></p><div><hr></div><p><strong>James:</strong> Terrific. Anything that I neglected to ask about?</p><p><strong>Alex:</strong> I think we covered a lot of the areas I thought might be interesting in this conversation. So nothing springs to mind.</p><p><strong>James:</strong> Right. Thank you so much for joining us. This was great.</p><p><strong>Alex:</strong> This is fantastic. Thank you, James. I really appreciate the time.</p><h4><strong>Not really a legal pad</strong></h4><p>Okay, you can&#8217;t really do everything you can do in software on a legal pad, at least not without an infinite amount of time and a capacious supply closet. But legal pads have had some terrific advantages over software. Using a legal pad to perform an analysis or keep track of a process has almost no fixed costs, is flexible and requires no ongoing technical support &#8212; even if it&#8217;s prone to error and impossible to scale efficiently.</p><p>Traditionally, CIOs have faced a brutal tradeoff in enterprise technology, especially in <a href="https://www.prosaictimes.com/p/the-world-is-entropic-and-deterministic">entropic business domains</a> with messy business rules and data. Every incremental unit of automation or analytics functionality has required substantial investment to build and maintain. Which is worse? The Scylla of users frustrated by incomplete automation with a narrow happy path? Or the Charybdis of a CFO appalled by spiraling technology costs?</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!JaqZ!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F29b3f98a-d2d3-4c5d-9191-212963da65ff_2128x1532.jpeg" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!JaqZ!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F29b3f98a-d2d3-4c5d-9191-212963da65ff_2128x1532.jpeg 424w, https://substackcdn.com/image/fetch/$s_!JaqZ!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F29b3f98a-d2d3-4c5d-9191-212963da65ff_2128x1532.jpeg 848w, https://substackcdn.com/image/fetch/$s_!JaqZ!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F29b3f98a-d2d3-4c5d-9191-212963da65ff_2128x1532.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!JaqZ!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F29b3f98a-d2d3-4c5d-9191-212963da65ff_2128x1532.jpeg 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!JaqZ!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F29b3f98a-d2d3-4c5d-9191-212963da65ff_2128x1532.jpeg" width="1456" height="1048" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/29b3f98a-d2d3-4c5d-9191-212963da65ff_2128x1532.jpeg&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1048,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:188077,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/jpeg&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.prosaictimes.com/i/221021247?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F29b3f98a-d2d3-4c5d-9191-212963da65ff_2128x1532.jpeg&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!JaqZ!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F29b3f98a-d2d3-4c5d-9191-212963da65ff_2128x1532.jpeg 424w, https://substackcdn.com/image/fetch/$s_!JaqZ!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F29b3f98a-d2d3-4c5d-9191-212963da65ff_2128x1532.jpeg 848w, https://substackcdn.com/image/fetch/$s_!JaqZ!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F29b3f98a-d2d3-4c5d-9191-212963da65ff_2128x1532.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!JaqZ!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F29b3f98a-d2d3-4c5d-9191-212963da65ff_2128x1532.jpeg 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Agentic technologies offer the possibility of shifting the efficient production frontier outward: more automation and analytics for the same expenditure, or the same functionality at lower cost. This changes the minimum efficient scale for any given requirement -- you can automate exceptions that you would have previously forced onto users for manual intervention.</p><p>Not a small thing for companies where the pace of digitization has been a rate-limiting factor for their business strategy.</p><p>CIOs and CTOs might ponder two questions.</p><p>Where in the digitization value chain and technology stack should they deploy agents? What combination of design time or run time? In the presentation layer, the application layer or the data layer?</p><p>Can they give the cobbler&#8217;s children feet? Can enterprise technology provide a proof point in using agentic technologies to achieve extreme automation? Could you aspire to:</p><ul><li><p><a href="https://www.prnewswire.com/news-releases/robin-by-atera-achieves-321-roi-according-to-new-forrester-study-302877580.html">Roughly 90%</a> of routine user IT requests fulfilled without human intervention.</p></li><li><p><a href="https://www.servicenow.com/products/itsm/what-is-it-change-management.html">95%+</a> of standard infrastructure changes executed automatically.</p></li></ul><p>What changes in governance, platforms, risk management and operating models would that require?</p><h4><strong>Footnotes</strong></h4><p>[1] One of the other associates reported the manager claimed descent from a buccaneering sea captain who danced on the line between commerce and privateering. Sadly, a common surname precludes confirmation of this detail.</p><p>[2] In the 1990s, we listened to the <a href="https://www.youtube.com/watch?v=ah5gAkna3jI">Gin Blossoms</a> on cassette in our cars and sought interviews at a million boutique consulting firms: <a href="https://managementconsulted.com/marakon/">Marakon</a>, <a href="https://startupintros.com/orgs/corporate-decisions-inc">CDI</a>, <a href="https://www.scribd.com/doc/18250617/The-Mitchell-Madison-Story-Part-II">Mitchell Madison</a>, none of which I could get hired at. Yes, the Marakon folks were smart, but given the firm&#8217;s <a href="https://www.govinfo.gov/content/pkg/USCOURTS-nysb-1_08-bk-12547/pdf/USCOURTS-nysb-1_08-bk-12547-0.pdf">subsequent history,</a> I&#8217;m lucky I blew the final-round case interview in 1996. Couldn&#8217;t figure out that holding too much cash depressed returns for a manufacturing company.</p><p>Very little available on Coba-MID, but there are enough references to it in CVs and the like to confirm I am not engaging in carbon-based hallucination here.</p><p>I&#8217;m (much) less cynical about consulting than the author of <a href="https://www.harpercollins.com/products/consulting-demons-lewis-pinault?variant=32129201766434">Consulting Demons</a>, but it&#8217;s an amusing memoir of a more buccaneering, less risk-averse and often worrisome era in the industry&#8217;s history.</p><p>[3] Later Deloitte Consulting. Then Braxton for a little bit. Then Deloitte Consulting again. Some of the consulting partners of the era just wanted to call it <a href="https://www.latimes.com/archives/la-xpm-1989-08-14-fi-453-story.html">Touche Ross.</a></p><p>[4] Historians call the Monroe presidency (1817&#8211;1825) the <a href="https://millercenter.org/president/monroe/domestic-affairs">Era of Good Feelings</a>. Their successors will refer to the 1990s as the era of <a href="https://www.cio.com/article/266792/customer-relationship-management-the-truth-about-crm.htm">silly CRM adventures</a>.</p><p>[5] Admittedly by way of Brown University and the Wharton School.</p><p>[6] Reuse is essential. You build a function that works, you keep invoking it. I have used the fast legal pad metaphor hundreds of times in the ensuing decades.</p><p>[7] You might respond that given enough time and enough legal pads you could replicate the operation of a GPT manually. You shouldn&#8217;t, but you could.</p><p>More interestingly, Goodfire researcher <a href="https://already-clean.goodfire.com/">Nick Cammarata</a> argues, as a working hypothesis, that most neurons in trained networks do one identifiable job, and that the apparent tangle was largely a misreading of the evidence.</p><p>If he is right, a model&#8217;s internals are more legible than I assumed. His results are preliminary, and he works at an interpretability company. Understanding individual neurons is not the same as demonstrating the reliability of an entire system.</p><p>[8] <a href="https://www.prosaictimes.com/p/prosaic-times-if-you-can-code-well">Prompt injection</a> is the risk this leaves. <a href="https://www.prosaictimes.com/p/cisos-help-business-leaders-take">Scoped permissions and least privilege</a> limit what a manipulated agent can reach, and a program can <a href="https://www.prosaictimes.com/p/prosaic-times-if-you-can-code-well">check the agent&#8217;s plan against security policy</a> before it acts. <a href="https://www.prosaictimes.com/p/cybersecurity-is-entropic-too">Assume eventual penetration</a>.</p><p>[9] They should have seen what it was like 20 years ago, before <a href="https://www.martinfowler.com/bliki/InfrastructureAsCode.html">infrastructure as code</a> became widespread.</p><p>[10] <a href="https://www.prosaictimes.com/p/is-mythos-the-sputnik-moment-for">Change control can be a test, not a meeting</a>: a change proves itself in a sandbox, against an adversary agent, before it rolls out in stages. Rich Isenberg: <a href="https://www.prosaictimes.com/p/cisos-help-business-leaders-take">&#8220;Autonomy without governance is not innovation; it&#8217;s negligence.&#8221;</a> <a href="https://www.prosaictimes.com/p/context-is-the-new-code">An agent can&#8217;t lose its job</a>. A named person stays on the hook.</p><p>[11] <a href="https://www.prosaictimes.com/p/you-need-both-business-technology">Business users want use cases quickly</a>, and <a href="https://www.prosaictimes.com/p/building-the-control-point-for-agentic">someone has to build the shared layer once</a>: <a href="https://www.prosaictimes.com/p/prosaic-times-how-enterprise-technology">enterprise technology provides the platform</a> and <a href="https://www.prosaictimes.com/p/does-vibe-coding-have-to-mean-technical">citizen developers build on top</a>. Some companies will build their own platform. Others will buy one.</p><p>[12] Here are some of the case examples Serval provides on its website: <a href="https://www.serval.com/customers/cribl">Cribl reports building in twenty minutes an automation that took consultants three weeks</a>. <a href="https://www.serval.com/customers/seatgeek">SeatGeek reports a 50% automation rate within sixty days</a>. <a href="https://www.serval.com/customers/abridge">Abridge reports clearing a two-month ticket backlog in two weeks</a>.</p><p>[13] <a href="https://www.prosaictimes.com/p/letter-to-a-vibe-coder">Skills have boundaries. Mindsets compound.</a> A good developer pairs curiosity with intellectual precision, and asks &#8220;What do I mean by X?&#8221; as well as &#8220;How do I do X?&#8221; Five habits for a citizen developer: automate what you understand, remember that models aren&#8217;t magic, make agents write things down, keep business logic deterministic and tested, and probe the agent as you would a new joiner.</p><p>[14] The <a href="https://www.prosaictimes.com/p/trading-bad-inefficiency-for-good">Technology Leadership Forum</a> convenes 50&#8211;70 CIOs, CTOs, CISOs and enterprise technology executives every spring and fall.</p><p>[15] I overstated this in the interview. SQL did not remove the work of designing databases. It separated what you want from how the system gets it: you write the query, and the database decides how to run it.</p><p>[16] <a href="https://wp.sigmod.org/?p=688">Thomas Haigh</a> on the tape era: &#8220;Every time a field was added or changed all the programs working with the file would need to be rewritten.&#8221; And on relational systems: &#8220;deleting all records more than a year old or adding 10% to the sales price of every item could be performed with a single command.&#8221; <a href="https://research.ibm.com/publications/relational-database-a-practical-foundation-for-productivity">Demand for applications was outrunning what programmers could build</a>, and <a href="https://www.ibm.com/history/relational-database">specialists often wrote whole programs to fetch one piece of data</a>. I have no source for ninety percent.</p>]]></content:encoded></item><item><title><![CDATA[Character and leadership in the executive suite: advice for CIOs and CTOs]]></title><description><![CDATA[A discussion with my partner-colleague Ramesh Srinivasan]]></description><link>https://www.prosaictimes.com/p/character-and-leadership-in-the-executive</link><guid isPermaLink="false">https://www.prosaictimes.com/p/character-and-leadership-in-the-executive</guid><dc:creator><![CDATA[James Kaplan]]></dc:creator><pubDate>Sun, 11 Oct 2026 20:00:27 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/219866093/5b738b2ea407fbf1ac4d1bddf1b670d4.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>Being a CIO or a CTO is a tough gig. You don&#8217;t control a full P&amp;L or even a revenue line. You only create economic value through other members of the executive team, who may not understand what you do and may have conflicting or competing objectives. You face a vendor community that primarily sees you through the lens of a sales target. Corporate functions in finance, HR and procurement that have their own agendas. In many sectors, you have stringent regulatory oversight and unforgiving regulators. And your team members worry that technological advances will render them irrelevant within a few years.</p><p>Political savvy grounded in <a href="https://www.prosaictimes.com/p/just-like-parents-cios-must-be-demon">game theory</a> is existential if you want to assemble the fragile coalitions that progress requires. But that&#8217;s not enough.</p><p>I&#8217;ve been wandering around large technology organizations for decades &#8212; I remember frame relay and installing software from CD-ROMs. CIOs and CTOs who sustainably make progress draw on enormous reserves of character.</p><p>Here&#8217;s my hypothesis on the markers of character in a high-stakes business environment &#8212; and why they matter for CIOs and CTOs.</p><ul><li><p><strong>Duty:</strong> recognizing what you owe and discharging it. Will the rest of the executive team see you as prosecuting the shareholders&#8217; agenda or your own?</p></li><li><p><strong>Integrity:</strong> committing to understanding the facts of the matter. Will your team see you as doing the work to understand the options they present to you?</p></li><li><p><strong>Judgment:</strong> choosing a course of action dispassionately based on the world as it is. Can you put anxieties and preconceptions aside when making &#8220;<a href="https://s2.q4cdn.com/299287126/files/doc_financials/annual/2015-Letter-to-Shareholders.PDF">one-way door</a>&#8221; decisions?</p></li><li><p><strong>Fairness:</strong> giving other people their due. Will your team see you as sharing credit for successes and accepting responsibility for disappointments?</p></li><li><p><strong>Courage:</strong> acting on your judgment despite personal cost. Will you fight for the resources required to reduce technical debt and protect the environment?</p></li><li><p><strong>Enterprise:</strong> taking responsibility for making something happen. Will you keep going, no matter the absurdities and frustrations of corporate life? [1]</p></li></ul><p>I&#8217;ve had the privilege of watching some senior technology executives handle reductions in force, reorganizations, brutal budgetary choices, strategic disagreements, tough vendor negotiations and stalled projects with class.</p><p>Character is not pleasantness or even conflict aversion, no matter what the zeitgeist believes or what they sell in airport <a href="https://www.penguinrandomhouse.com/books/177478/the-power-of-nice-by-linda-kaplan-thaler-and-robin-koval">bookstores</a>.</p><p>Early in my McKinsey career, I joined a team supporting a massive, stalled IT consolidation. Coincidentally, the company had just appointed a long-time senior executive to lead this program.</p><p>He called the dozens of people working on the program together in a big conference room. He stood and said, loudly:</p><blockquote><p>I have some homework for every employee of the bank in the room. Do some homework about me. Ask around. I&#8217;ve been around a long time. I&#8217;ve bought businesses. I&#8217;ve sold businesses. I&#8217;ve built technology organizations, and I have cut them in size as well.</p><p>When you ask around, people will tell you that I get done what I promise to do, and they will tell you that when people deliver I am very vocal in the bonus committee at the end of the year, and I get listened to.</p><p>We need to get this program on track. If you help me do that, I will speak up for you in the bonus committee. And if you don&#8217;t, I will speak up about that as well.</p></blockquote><p>This was not pleasant. It may not even have been nice, but it manifested character. This executive understood his responsibility &#8212; the financial health of the institution demanded the hundreds of millions of dollars we would all save. He quickly grasped the gravity of the situation and declined to console himself with happy platitudes. He acted to address the biggest problem, an uncommitted team, and he promised astringent fairness at year end.</p><p>And sadly, I have sometimes seen the opposite.</p><p>For all these reasons I was thrilled to talk with my partner-colleague <a href="https://www.mckinsey.com/our-people/ramesh-srinivasan">Ramesh Srinivasan</a> about leadership and character in the executive suite, how that intersects with the age of AI and what that might mean for CIOs.</p><h4>Leadership as a choice</h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>Leadership means accepting accountability for outcomes that others deliver, and exercising it is a choice</p></li><li><p>The Bower Forum has put 800-plus CEOs through a learning program over sixteen years, and the work became a book</p></li><li><p>The guest brings 32 years at McKinsey, mostly healthcare and life sciences, and has studied leadership at close quarters through the Bower Forum</p></li></ul><div><hr></div><p><strong>James Kaplan:</strong> All right, this is James Kaplan with another Prosaic Times video podcast. I&#8217;m on video today with one of my favorite colleagues, Ramesh Srinivasan, who I&#8217;ve worked with on a whole bunch of stuff, mostly for clients in the pharmaceutical industry, and we&#8217;re gonna have a conversation about leadership and AI and about CIOs and <a href="https://prosaictimes.substack.com/p/cios-the-boardroom-is-grading-a-business">how they engage with CEOs</a>.</p><p>And the rest of the executive team.</p><p><strong>Ramesh Srinivasan:</strong> I&#8217;m a senior partner with McKinsey, been with McKinsey for 32 years. The sector I know well is healthcare and life sciences within that, which is where James and I have done some work. But beyond that, I call myself a student of leadership. I play the role of the dean of the Bower Forum, which is McKinsey&#8217;s CEO learning program. We have had 800 plus CEOs who&#8217;ve gone through the program over the last 16 years. So it&#8217;s given me a chance to study leadership at close quarters. Based on that, we wrote a book called <a href="https://www.mckinsey.com/featured-insights/mckinsey-on-books/journey-of-leadership">The Journey of Leadership</a>, and I continue to study that topic.</p><p><strong>James:</strong> Always a pleasure and it&#8217;s always exciting to be talking with someone who&#8217;s been at the firm longer than I have, especially now with Vik Malhotra retiring.</p><p>Let&#8217;s start off. Let me offer a potential definition of leadership. I&#8217;d like you to beat it up and see if you agree with this or do disagree with it. So I would define leadership as accepting responsibility and enlisting others in discharging that responsibility. Is that a plausible definition? What&#8217;s missing? Are there other definitions we should consider?</p><p><strong>Ramesh:</strong> It&#8217;s actually a pretty good definition, James. When we wrote the book Journey of Leadership, Kurt Strovink and I, but also a couple of others, thought about this question about how do we define leadership? And we believe leadership is a choice and it&#8217;s not something that you exercise by default, but it&#8217;s good to be explicit and you assume the role of leadership when you actually have accountability and responsibility for the outcomes that others may be delivering on your behalf.</p><h4>Leadership in an always-on world</h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>The core principles of leadership have held for three decades while the pace of change has not</p></li><li><p>Geopolitics, AI, and social media have made the role more dynamic and always on</p></li><li><p>Shorter CEO tenures through 2025 point to a harder job</p></li></ul><div><hr></div><p><strong>James:</strong> Roughly speaking, our professional careers have spanned about the past three decades or so, a little bit more. We&#8217;re both getting older. Over that time you&#8217;ve been active in the professional world, how has the model for leadership changed? If at all?</p><p><strong>Ramesh:</strong> I do think the fundamental model and principles, I think the good news is there have been many constants over these three decades. And so some of those principles I feel haven&#8217;t changed as much. But the fact of the matter is that the rate of change in the world has increased tremendously. You and I have talked about it, the geopolitics have become more complex today than ever before. Technology broadly speaking, but AI and Gen AI have also disrupted the world in a tremendous way. And so these couple of factors I feel have really forced leaders to be even more dynamic in the way they operate. So I think leaders I feel need to have a sense of purpose, a purpose that typically comes from within. So we call it the inside out model of leadership. So why do I do what I do? What gives me meaning? What gives me energy? What is my identity? Those I think need work so that I start from within. And I&#8217;m always on with social media now. What I say as a senior leader can be shared anywhere in the world. So I have a greater responsibility. It&#8217;s an always-on 24 by 7 role, so especially as a senior leader in the business or social impact world, I need to be ready for that, which was not as intense three decades ago, I feel, James. That&#8217;s probably been the biggest shift.</p><div><hr></div><p><em>What I say as a senior leader can be shared anywhere in the world. So I have a greater responsibility.</em></p><div><hr></div><p><strong>James:</strong> What&#8217;s your view on the state of leadership today? If you look around at CEOs, you say most CEOs are pretty good leaders, most CEOs aren&#8217;t such great leaders.</p><p><strong>Ramesh:</strong> I think most CEOs are pretty good leaders. So, in that sense, that&#8217;s an easy question to answer. But the fact of the matter is that <a href="https://www.russellreynolds.com/en/insights/reports-surveys/global-ceo-turnover-index">CEO tenures</a> are going down. So, investors and boards, at least that metric tells you that it&#8217;s harder and harder for CEOs to be delivering value to their stakeholders for long periods of time that they were able to do three decades ago. And so in that sense, it is becoming harder.</p><p>And so as human beings and leaders, CEOs, but also all of us need to really keep asking ourselves, are we ready for this challenge? Are we ready for this next level of changes, for this even more rapid world?</p><h4>Inner-directed or other-directed?</h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>Riesman&#8217;s inner-directed and other-directed types frame the tension between purpose and popularity</p></li><li><p>One path starts by wanting to be liked and learns to speak truth to power; the other starts with a fixed aim and learns to hear competing ones</p></li><li><p>The answer is a balance that starts from a purpose that comes from within, then serves the stakeholders</p></li></ul><div><hr></div><p><strong>James:</strong> You said something very interesting a couple of minutes ago about internal purpose. Last time we chatted, did I mention David Riesman&#8217;s book <a href="https://yalebooks.co.uk/book/9780300174144/the-lonely-crowd/">The Lonely Crowd</a> from the nineteen fifties?</p><p><strong>Ramesh:</strong> No, you didn&#8217;t. Tell me more.</p><p><strong>James:</strong> Okay. It&#8217;s a fascinating book. It was written in, I think, nineteen fifty. And you would have thought it had been written last year. And it divides the world, or says that most people are other-directed. In effect, they want to be popular. They want to be liked. They seek harmony. And it&#8217;s said that some people are <a href="https://prosaictimes.substack.com/p/things-i-was-too-stupid-to-know-when-1bf">inner-directed</a>. They have an internal gyroscope that often was set at a younger age and they have a set of things they&#8217;re trying to accomplish.</p><p>And sometimes I worry over time we&#8217;ve defined leadership as being too other-directed rather than inner-directed, though inner-directed can have its pathologies also, right? You can be a little bit of a heat-seeking missile, as I&#8217;ve sometimes been. Are the best leaders a combination of other-directed and inner-directed?</p><p><strong>Ramesh:</strong> No, great question, James. Well, I&#8217;m the youngest of three kids and unfortunately my father passed away when I was twelve years old and I was a lonely kid and I really wanted people around me and so I did want everyone to like me. And I actually built skills to connect with people and connect with them quickly.</p><p><strong>James:</strong> I&#8217;m sorry to hear that.</p><p><strong>Ramesh:</strong> And it&#8217;s really as I grew more tenured as a leader, I realized that leadership is not a popularity contest. In my role as an advisor, sometimes I need to be able to tell people tough news. I need to be able to speak truth to power. And so to be an effective advisor is not to be liked by everybody. And it&#8217;s been a growth process for me. And as I&#8217;ve gone through that journey, inner journey myself, I&#8217;ve learned that I need to strike a balance.</p><p>And I need to go back to my own purpose. My own purpose is to bring hope, optimism, a sense of possibilities in an ever-changing world.</p><p>So the answer to your question and what we saw even with CEOs is it&#8217;s good to have a bit of balance, but it starts from within. It starts by being an inner-directed leader and having a clear why and being able to communicate that.</p><p>But then leaders and CEOs and CIOs and other leaders have an obligation to think about the different stakeholders, and making sure that the purpose, the vision is then serving the needs of different stakeholders. And when there&#8217;s a conflict, being able to do that in an effective way and making those trade-offs, that&#8217;s where I feel leadership is about, James.</p><div><hr></div><p><em>So the answer to your question and what we saw even with CEOs is it&#8217;s good to have a bit of balance, but it starts from within. It starts by being an inner-directed leader and having a clear why and being able to communicate that.</em></p><div><hr></div><p><strong>James:</strong> Yeah, and maybe the best leaders figure out how to manage that dialectic. And my journey, however imperfect, has been the opposite of yours. Even as a small kid, I was hyper-inner-directed. I was like, God damn it, I&#8217;m doing this. And anyone else is welcome to come along for the ride. And I had a bad habit of, okay, I&#8217;m trying to do X. I think X is the right thing. And I wouldn&#8217;t realize that someone else was trying to accomplish Y. And maybe Y was a legitimate objective also, right? Even if it wasn&#8217;t X.</p><p>And how do we mediate between I want to do X and you want to do Y? And maybe both those things are okay and we don&#8217;t have to work across purposes to each other. That took me probably into my 40s to sort of work out.</p><p><strong>Ramesh:</strong> No, that&#8217;s a beautiful journey. That&#8217;s what I feel, because if you keep listening to others, which was sometimes my challenge, then A, that&#8217;s not what the world expects of me. But also more importantly, that was not giving me joy and meaning. I define joy as things that I do every day, coming from the work of <a href="https://prosaictimes.substack.com/p/agent-serena-stopped-the-yak-shaving">Mihaly Csikszentmihalyi</a>, who wrote about flow. I&#8217;ve really reflected more on what keeps me in flow.</p><p><strong>James:</strong> <a href="https://books.google.com/books/about/Flow.html?id=QVjPsd1UukEC">Flow: The Psychology of Optimal Experience</a> is one of my favorite books. It&#8217;s like one of those books which I think everybody should read.</p><p><strong>Ramesh:</strong> Absolutely. And that&#8217;s what results in creativity and innovation in the world. And on the other side, the work of Viktor Frankl&#8217;s <a href="https://www.beacon.org/Mans-Search-for-Meaning-P602.aspx">Man&#8217;s Search for Meaning</a>. When you have a great why, the how matters less and less. And just reading about his story, his work, I have realized that, for me, when I&#8217;m 80 years old, I really want to feel like I&#8217;ve had some accomplishment, even as along the way I&#8217;ve had joy and been in flow throughout, James.</p><h4>Resilience and the choice of reaction</h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>Frankl&#8217;s Man&#8217;s Search for Meaning shows purpose sustaining a person in the worst circumstances</p></li><li><p>Resilience means reframing a problem into a challenge and a challenge into an opportunity</p></li><li><p>Frankl and Marcus Aurelius both place power in controlling one&#8217;s reaction, which no one can take away</p></li></ul><div><hr></div><p><strong>James:</strong> Yeah, and a couple of thoughts. One is I read Man&#8217;s Search for Meaning in high school, but it&#8217;s a pretty good exposition of an inner-directed mindset, right? Which he obviously developed or sustained himself with in the worst circumstances imaginable. Right? And obviously infinitely worse than any circumstance you could experience in an office type environment, but I think that&#8217;s an example of the strength that a sense of purpose and a sense of inner direction can provide to you.</p><p><strong>Ramesh:</strong> And maybe one theme there that was there in Viktor Frankl&#8217;s book, and also a theme we then borrowed and we expanded in the Journey of Leadership book is the notion of resilience. In today&#8217;s day and age, with all the changes, I think it&#8217;s critical for leaders to be resilient. And part of that is the ability to reframe. I often say how do you reframe a problem into a challenge and a challenge into an opportunity? Similarly, Viktor Frankl talks about when there is a stimulus, the biggest power that we as human beings and leaders have is we control our reaction to that stimulus. And nobody can take that away. That&#8217;s a choice that will stay with us till the day we die. And that&#8217;s been a very powerful notion I learned from him, James.</p><div><hr></div><p><em>When there is a stimulus, the biggest power that we as human beings and leaders have is we control our reaction to that stimulus. And nobody can take that away. That&#8217;s a choice that will stay with us till the day we die.</em></p><div><hr></div><p><strong>James:</strong> Yeah, I tell that to people all the time. Someone else cannot invite you to the meeting. They can criticize what you wrote, they can be unfair in some way. They can&#8217;t make you be upset about it. Right? Only you get to control how upset you are about something or how you react to something. That&#8217;s tremendous amount of power. I just finished reading Marcus Aurelius&#8217;s <a href="https://standardebooks.org/ebooks/marcus-aurelius/meditations/george-long">Meditations</a>.</p><p>It&#8217;s a fascinating book. And one of the things you take is this is written by possibly the most powerful man in the world, as he was writing, the Roman Emperor, right? And he is talking through the petty frustrations he has to deal with, and he&#8217;s like, there&#8217;s nothing you can do to escape the frustrations. You can be the Roman Emperor. And still be frustrated by this sycophancy or that flattery or that disingenuousness or what have you. All you can do, no matter who you are, is control your reaction to it, right? And that was an astonishing thing to me. But I suppose that&#8217;s why Marcus Aurelius was one of the five good emperors, and a much better emperor than, for example, his son Commodus was.</p><h4><strong>Do we talk enough about character?</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>Business talks about character far less than the military does</p></li><li><p>One working definition: what a leader does when nobody is watching</p></li><li><p>A second test: how a leader responds under stress, which Navy SEAL training simulates</p></li></ul><div><hr></div><p><strong>James:</strong> Let me ask you this question. Do we talk enough about character in the business world? Because there&#8217;s some part of me that thinks that everything boils down to character. And it sort of feels like an old-fashioned word. Are we embarrassed to speak about it? And should we be thinking and speaking about it more?</p><p><strong>Ramesh:</strong> I think we should be speaking about it more. <a href="https://irp.fas.org/doddir/army/adp6_22.pdf">The military world</a> actually understands it better. I&#8217;ve been learning about it from <a href="https://navyseals.com/ns-overview/notable-seals/eric-t-olson/">Admiral Eric Olson</a>, who spent nearly forty years with the US Navy, Navy SEAL himself. And I think it&#8217;s actually quite critical.</p><p><strong>James:</strong> Our mutual colleague, <a href="https://prosaictimes.substack.com/p/when-binaries-break-and-what-that">Charlie Lewis</a>, is a West Point grad, right? And he was upset about something. He called me about it, he says, I have a ring that says duty, honor, country. He says, I take those very seriously. And it was one of the most striking and inspiring statements I&#8217;ve ever heard a colleague say. Right? It&#8217;s like, for him, everything comes back to that, right?</p><p><strong>Ramesh:</strong> So I think character needs to be studied more. And one way to define character is what is it that leaders do when nobody&#8217;s watching?</p><div><hr></div><p><em>So I think character needs to be studied more. And one way to define character is what is it that leaders do when nobody&#8217;s watching?</em></p><div><hr></div><p><strong>James:</strong> Also, he&#8217;s been on <a href="https://prosaictimes.substack.com/p/when-binaries-break-and-what-that">Prosaic Times</a>, right? We had a great discussion.</p><p><strong>Ramesh:</strong> Another way is to see what do you do under stress. The Navy SEALs do this by simulating stress. And the fact of the matter is with all the changes happening in the world, business leaders have to very often deal with stressful situations and how I respond in those situations I feel is a good test and a good definition of my own character.</p><h4>Long on character: a working definition</h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>Executive teams may be long on character, but few have definitions, behaviors, measures, or experiences that build it</p></li><li><p>Six proposed components: duty, integrity, judgment, fairness, courage, and enterprise</p></li><li><p>Proposed additions: purpose, resilience, courage preferred over boldness, and curiosity</p></li></ul><div><hr></div><p><strong>James:</strong> Right. So if you look at executive teams, are they often long character or short character?</p><p><strong>Ramesh:</strong> What do you mean by a long character or short character?</p><p><strong>James:</strong> A long character means we have a lot of character. Yeah, I&#8217;m talking &#8212; you remember I&#8217;ve served banks &#8212; you can be long or short a commodity, right? You may or may not think of character as a commodity, but your average executive team, do they have lots of character or do they have a shortage of character?</p><p><strong>Ramesh:</strong> I&#8217;ve never heard this frame long character and short character. I think many of the leaders, especially the CEOs who come to the Bower Forum, I actually feel they&#8217;re long on character, if I were to use your definition.</p><p><strong>James:</strong> Maybe a self-selecting sample.</p><p><strong>Ramesh:</strong> It&#8217;s probably a self-selecting sample. They want to reflect more and they wanna explore more. But I often feel they don&#8217;t have definition around it, they don&#8217;t have specific behaviors that define it. They don&#8217;t have ways of testing and measuring, they don&#8217;t have ways of building character, creating experiences that build character. So that&#8217;s the struggle that I&#8217;ve seen.</p><p>How do you help them explain what they&#8217;ve been through and put some definition and terminology around it?</p><p><strong>James:</strong> Yeah, that&#8217;s a fascinating idea. Okay, let&#8217;s assume you have a CEO who is taking character seriously, is willing to do the right things when nobody is watching. Then there&#8217;s a whole nother thing around how does that CEO foster character in his or her executive team and two and three and four levels down in the organization.</p><p>In my internal newsletter, I suggested six components of character. Let me run you through those. Tell me if you think this is missing anything. Duty. Integrity. Judgment. Fairness, giving other people their due. I was really bad at that when I was younger. Courage. And enterprise. How does that work for you as a definition of character? Does that resonate or not resonate? Or are things missing?</p><p><strong>Ramesh:</strong> It resonates. The risk with some of these, like duty, for example, is that it comes with such heaviness that in a world that is changing so fast you need to figure out how you can be light and flexible, take initiative, take risk, back to your point about enterprise, so that&#8217;s a reaction that&#8217;s going through my mind. I&#8217;m a big believer on purpose. What is my why? And often that purpose is tied to my own crucible moments and my inner work and inner journey. So there&#8217;s something about that inner purpose and my why deserves some attention.</p><p><strong>James:</strong> Yeah, as I define duty, I think I define it very similarly to the way you define purpose. I define it a little bit as what you owe, but I think you&#8217;re someone who sees his purpose as doing something for those outside of you. Right? You have a purpose that is not entirely endogenous, right? That it is service to others.</p><p><strong>Ramesh:</strong> Correct. It&#8217;s a service to others but comes from within. I went to a public school in India where I paid five rupees a month and got an excellent, fantastic, almost I would say, world class education, and I felt like therefore I owed it to the system. And in part that&#8217;s what has driven my passion for education equity, later on, right? So to me the purpose, yeah, I could live with the sense of duty. Yes, it has a service to others and it has to come from within. I think the other is this concept of resilience that you and I have already started talking about. It goes back to my notion that character really gets tested when you&#8217;re under stress.</p><div><hr></div><p><em>So to me the purpose, yeah, I could live with the sense of duty. Yes, it has a service to others and it has to come from within.</em></p><div><hr></div><p><strong>James:</strong> No, this is fantastic. Yeah, my takeaway here is even if you have senior executives who have character, I offer the hypothesis that institutions should be thinking more systematically about character.</p><p><strong>Ramesh:</strong> I agree with you. And by the way, I love the notion of courage. Our colleagues published this book called CEO Excellence and one of the big ideas they talk about is being bold. I actually prefer the word courage to the word boldness. My sense is courage has a better, more robust and more rigorous definition. And then I love to use the word curiosity as well within the character, which goes back to your notion of evidence and really asking deep questions. We often talk about the <a href="https://prosaictimes.substack.com/p/things-i-was-too-stupid-to-know-when-1bf">five whys</a>, and I feel like that&#8217;s so critical. Yes, we want to move fast, and yes, we want to react to changes in the world, but I think leaders need to ask the second order questions about implications of both the root causes and implications of their actions. And I feel like that&#8217;s a test of character as well.</p><h4><strong>Curiosity as a test of character</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>Curious people make the best colleagues, and incuriosity makes intellectual integrity hard</p></li><li><p>Observation and orientation come before decision and action in Boyd&#8217;s OODA loop</p></li><li><p>Observing with limited judgment is a discipline, and asking questions can itself intervene in what is observed</p></li></ul><div><hr></div><p><strong>James:</strong> Perhaps the biggest single discriminant for me about whether I enjoy working with someone is their curiosity. I love working with curious people. I love working with people who say, Yeah, gee, why is that? Explain that to me, right? And I would tie, and I thought about this, I would tie curiosity to integrity because I would argue it&#8217;s very hard for people who are incurious to have intellectual integrity.</p><p><strong>Ramesh:</strong> I love that linkage. I love the intellectual integrity that I am really testing my own beliefs, my own frameworks against what&#8217;s happening in the world and I&#8217;m open to that debate and challenge as a component of character. I like that a lot, James.</p><p><strong>James:</strong> Yeah, because if you think about strategy setting, right? John Boyd&#8217;s <a href="https://www.prosaictimes.com/p/every-decision-you-make-rests-on">OODA loop</a>, observe, orient, decide, act, which is, if you&#8217;re not observing and you&#8217;re not orienting, how the bloody hell are you gonna decide and act effectively, right?</p><p><strong>Ramesh:</strong> In fact, my wife who is an educationalist, she often talks about low inference observations. When she goes into a classroom and she sees a teacher with forty students, her first instinct is just to observe. And observe, she might pick some great behaviors and some bad behaviors by teachers or students. Her instinct is to just pause the inference and the judgment or any decision making or comments, but really observe and observe with as limited judgment as possible for a period of time before then forming hypothesis and figuring out how to coach the relevant teacher or whoever is in the mix.</p><div><hr></div><p><em>In fact, my wife who is an educationalist, she often talks about low inference observations. When she goes into a classroom and she sees a teacher with forty students, her first instinct is just to observe.</em></p><div><hr></div><p><strong>James:</strong> I&#8217;m really bad at that, not because I jump to the hypothesis. I&#8217;m like, why&#8217;d you do that? Why did someone say that? I always wanna ask the questions. I wanna understand why. So it&#8217;s hard for me to sort of sit back and not ask the twelve questions about why someone did something or why something happened, right? Which one of the things that fascinates me about the work we do and the work our clients do, which is say large enterprises are these incredibly complicated, interconnected machines, right? Machines with this, obviously tremendous human components. And just the ability to just like, okay, why did this happen? Right? Explain that, explain that to me. It&#8217;s sort of the part of me that was passionate about history, where you say, okay, gee, why did this set of events in the French Revolution happen, right? It&#8217;s like, why did this set of events in a merger or a business strategy happen or a technology strategy?</p><p><strong>Ramesh:</strong> No, I love that curiosity about you, James. I think what I&#8217;ve learned from my wife is just the balance between getting those set of facts to just describe a system and then absolutely the asking the why you really dig into it.</p><p><strong>James:</strong> Well, yeah. I&#8217;m not disputing her point because the challenge with asking so many questions, it&#8217;s like Heisenberg&#8217;s uncertainty principle. [2] Right, by asking the question you&#8217;re disrupting the experiment. So I&#8217;m not saying I&#8217;m right to ask all those questions. I&#8217;m just saying it&#8217;s hard for me not to.</p><p>Right. You&#8217;re observing the classroom. If you start asking questions, the classroom will go in a different direction. The act of asking the questions becomes an intervention.</p><p><strong>Ramesh:</strong> Exactly. The first question becomes an intervention, even if it is asked from a place of curiosity and learning.</p><h4><strong>The CEO&#8217;s role in AI strategy</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>The CEO need not be the AI expert but does need to understand the pace of disruption in the business</p></li><li><p>Three roles proposed: aspiration setter, systems thinker, and disruptor of governance functions that slow AI value</p></li><li><p>A fourth role: culture carrier; AI adoption moves at the speed of trust, and the CEO sets that tone</p></li></ul><div><hr></div><p><strong>James:</strong> So let me bring this back around to AI for a second. What do you think the role of the CEO is in the age of AI, in pursuing AI strategy?</p><p><strong>Ramesh:</strong> So the first thing is the role of the CEO is not to be the expert on what&#8217;s happening with AI, but I think the CEO needs to start with just an awareness of their business and what they&#8217;re trying to accomplish, their vision, their purpose. What is the level of disruption? And what is the pace of disruption?</p><p>As they then craft their strategy, how are they going to embed AI into what they are planning to do? And where is it that they want to experiment, where is it that they want to place some big bets? These are some of the critical choices. That&#8217;s what a CEO needs to be able to do effectively, James.</p><p><strong>James:</strong> Yeah, I wonder if it&#8217;s three things. Tell me if you agree with this. First of which is the aspiration setter. Like people come and say, RPA is gonna change everything. Really?</p><p>I really think it&#8217;s easy to underestimate the transformative potential of Gen AI, largely because it allows us to process new types of data economically, process messier data and messier business rules economically than we could in the past. So one part of the CEO role is to set higher aspirations. And then a second thing I think is to be the systems thinker.</p><p>Right, particularly in bigger organizations, it&#8217;s easy to do local optimization. But the real value comes when you can connect across multiple businesses or multiple functions or multiple regions and truly step back and think about the system.</p><p>And the third is to be the disruptor. And in many places I look and see governance functions of procurement or HR or what have you, sort of being the decelerant for AI economic value because it&#8217;s just like, well, this is different. And I wonder if that resonates with you or things that are missing.</p><div><hr></div><p><em>I feel like it can only move at the speed of trust. And that trust is really set, the tone is set by the CEO.</em></p><div><hr></div><p><strong>Ramesh:</strong> It absolutely makes sense. And there, a hundred percent, I agree with you that it starts with setting the right ambition and direction and back to our notion of courage and boldness that we are talking about, I think that is absolutely the CEO&#8217;s role and it needs to be done in a thoughtful way.</p><p>I think beyond that, the systems thinking part that you&#8217;re talking about, the disruption you&#8217;re talking about, I think all of that then needs to lead to capital allocation and resource allocation on where is it that you&#8217;ll have the highest impact.</p><p>So those are some choices that only the CEO can make. And then maybe that one I would add is there&#8217;s something around being the culture carrier, the tone setter, getting the right capabilities and skills around yourself that are technology enabled but still can drive business value. So maybe that&#8217;s the only dimension I would add, because when we look at the adoption and scaling of AI, I feel like it can only move at the speed of trust.</p><p>And that trust is really set, the tone is set by the CEO. So that&#8217;s the third role I might add to what you were describing, James.</p><h4>Advice for CIOs</h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>This is the CIO&#8217;s moment, with CEOs and the C-suite coming to them for advice</p></li><li><p>Pick a few areas with the most business impact and partner with the more progressive executives</p></li><li><p>A May session in Chicago would take up character and culture for technology executives</p></li></ul><div><hr></div><p><strong>James:</strong> So let me ask one final question. What advice would you have for CIOs aspiring to be better leaders and aspiring to influence more effectively the rest of the executive suite?</p><p><strong>Ramesh:</strong> This is the CIO&#8217;s moment, James. CIO, CDIO, digital and analytics officer. All these folks have an incredible opportunity today by the disruption that AI, Gen AI technology offers to the world. Most of the CEOs and the C-suite is gonna come to them for advice. They are the technical expert, they have the credibility. So my advice to them would be: seize the moment. This is your chance. Of course, continue to learn to be at the forefront of whatever is relevant for your business and maintain the technical depth that&#8217;s expected of you.</p><p>But then really learn about where is it in the business you can deploy this value, make some choices so that you can really pick a few areas where you can show the most impact and treat the rest of the C-suite as your allies. Figure out where it is that you&#8217;re going to find some people who are going to be more progressive and partner with you to make things happen. So as you think about where to drive value, base it not just on the technology maturity and what&#8217;s possible, also on the business impact and also on the openness of the rest of the C-suite. So that as you help the enterprise, you&#8217;re really showing business value in partnership with the rest of the C-suite, and then bringing the whole, the CEO and the rest of the C-suite in this technology journey. That would be my biggest advice to them.</p><div><hr></div><p><em>They are the technical expert, they have the credibility. So my advice to them would be: seize the moment. This is your chance.</em></p><div><hr></div><p><strong>James:</strong> Terrific. You just gave me a thought. So I think as you know, about every fall and every spring, we get together about sixty, seventy CIOs, CTOs, CISOs, and what have you. Next one is next week, but we&#8217;re gonna do this again in Chicago in May. And I would like you to come and lead a session on leadership character and being a technology executive. I think that would be a fascinating session.</p><p><strong>Ramesh:</strong> No, love to do it. We&#8217;d love to do it. And maybe we do it with another CIO or a CEO who came from a technology background. That&#8217;s the format. So that maybe it&#8217;s a panel. Yeah.</p><p><strong>James:</strong> Yes, we&#8217;ll figure out the exact format. Maybe it&#8217;s a panel or something like that. But this is something in between all the things about evals and platforms and what have you, which I&#8217;m very passionate about, as you know. I&#8217;d also like to have a discussion about sort of what&#8217;s it take from a character and a culture and a leadership standpoint to lead change around technology at this moment in time.</p><p><strong>Ramesh:</strong> No, I love that. What does it mean to be a character builder and culture carrier as a CIO? That would be a cool topic to explore with a panel, James. Would love to do it. And maybe hopefully by May I&#8217;ll have a better framework as well on what defines character.</p><p><strong>James:</strong> All right. I will recruit a panel for you. Terrific. Thank you so much, Ramesh. This has been great.</p><p><strong>Ramesh:</strong> Thank you, James. Take care.</p><h4><strong>What is character?</strong></h4><p>Ramesh and I agree on a lot, and love working together, but you can see a little tension between our definitions of character. I see character beginning with obligations imposed by reality and one&#8217;s role: What do I owe? What is true? What does the situation require?</p><p>My six virtues govern action: duty identifies the obligation; integrity establishes the facts; judgment determines what to do; fairness recognizes others&#8217; legitimate claims; courage bears the cost; enterprise gets it done. None of those requires the action to feel good &#8212; to you or anyone else.</p><p>Ramesh&#8217;s conception is more purpose-centered and inside-out. He repeatedly begins with <em>why</em>: meaning, identity, crucible experiences, joy, flow, resilience. The leader discovers an internally grounded purpose and then translates it into service to others. Character is partly about becoming the kind of person capable of sustaining that purpose through adversity.</p><p>My list gives conflict and personal cost a central place: courage specifically means acting on judgment despite cost. Fairness can be astringent. Duty may require doing something unpleasant. Ramesh worries explicitly that &#8220;duty&#8221; carries too much heaviness and reaches for resilience, flexibility, initiative, hope and optimism.</p><p>Humans have argued about character for millennia; forgive Ramesh and me for not settling the matter in a podcast. But intellectual tension yields insight. Purpose gives character an internal foundation: <em>Why am I doing this?</em> Duty subjects that purpose to an external test: <em>What do I owe?</em></p><p>Any steward of an institution &#8212; anyone entrusted with consequential decisions &#8212; needs an answer to both.</p><p>Especially when navigating the lunacy of corporate life.</p><h4><strong>Footnotes</strong></h4><p>[1]: Character is a journey. I shudder at the man I was at 30. I was self-centered, callow and quick to anger. Looking at the list above, I&#8217;d say I did okay on a sense of duty, a commitment to integrity and on enterprise.</p><p>In contrast, I let anger and frustration cloud my judgment. And I gave no thought to fairness. I would roll over you (denying you your due) in the service of discharging my obligations as I saw them.</p><p>[2]: Strictly, Heisenberg&#8217;s uncertainty principle limits how precisely paired properties, such as a particle&#8217;s position and momentum, can be known at once. The effect I am describing is the <a href="https://www.prosaictimes.com/p/what-kalashnikov-and-heisenberg-understood">observer effect</a>: the act of measuring a system can change it.</p>]]></content:encoded></item><item><title><![CDATA[Cybersecurity is entropic too!]]></title><description><![CDATA[A discussion with Surf AI CTO Roie Cohen Duwek]]></description><link>https://www.prosaictimes.com/p/cybersecurity-is-entropic-too</link><guid isPermaLink="false">https://www.prosaictimes.com/p/cybersecurity-is-entropic-too</guid><dc:creator><![CDATA[James Kaplan]]></dc:creator><pubDate>Sun, 04 Oct 2026 21:00:48 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/218768425/e0be5c3143086eb04d52f5d219bfe809.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>Every system is an imperfect model of messy reality --  the messier the domain, the <a href="https://www.prosaictimes.com/p/the-world-is-entropic-and-deterministic-060">more the system costs to build and the more it frustrates its users</a>. [1] GenAI <a href="https://www.prosaictimes.com/p/hunting-for-entropy-to-find-ai-value">lowers the cost of absorbing the mess</a>: it reads the PDF, reconciles the schemas and constructs the rule. Projects that never cleared a business case now might -- so look for entropy.</p><p>Cybersecurity is entropic.  [2]</p><p>Entropy concentrates where judgment resists reduction, in cyber risk assessment, incident response and forensics, and crisis management, and the least in the plumbing: authentication, identity lifecycle, log management, key management, facility access.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!uLam!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F7c2ac655-6532-498c-b574-fbc9852007e5_1170x1626.jpeg" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!uLam!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F7c2ac655-6532-498c-b574-fbc9852007e5_1170x1626.jpeg 424w, https://substackcdn.com/image/fetch/$s_!uLam!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F7c2ac655-6532-498c-b574-fbc9852007e5_1170x1626.jpeg 848w, https://substackcdn.com/image/fetch/$s_!uLam!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F7c2ac655-6532-498c-b574-fbc9852007e5_1170x1626.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!uLam!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F7c2ac655-6532-498c-b574-fbc9852007e5_1170x1626.jpeg 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!uLam!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F7c2ac655-6532-498c-b574-fbc9852007e5_1170x1626.jpeg" width="1170" height="1626" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/7c2ac655-6532-498c-b574-fbc9852007e5_1170x1626.jpeg&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1626,&quot;width&quot;:1170,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:769128,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/jpeg&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.prosaictimes.com/i/218768425?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F7c2ac655-6532-498c-b574-fbc9852007e5_1170x1626.jpeg&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!uLam!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F7c2ac655-6532-498c-b574-fbc9852007e5_1170x1626.jpeg 424w, https://substackcdn.com/image/fetch/$s_!uLam!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F7c2ac655-6532-498c-b574-fbc9852007e5_1170x1626.jpeg 848w, https://substackcdn.com/image/fetch/$s_!uLam!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F7c2ac655-6532-498c-b574-fbc9852007e5_1170x1626.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!uLam!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F7c2ac655-6532-498c-b574-fbc9852007e5_1170x1626.jpeg 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Initiatives a company might pursue reconcile, correlate, consolidate or unify records that disagree: continuity plans against recovery evidence, asset inventories against cloud findings, telemetry against case files.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!KDNx!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F60141919-82ee-44fd-91cb-350df0e616a4_2000x1099.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!KDNx!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F60141919-82ee-44fd-91cb-350df0e616a4_2000x1099.png 424w, https://substackcdn.com/image/fetch/$s_!KDNx!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F60141919-82ee-44fd-91cb-350df0e616a4_2000x1099.png 848w, https://substackcdn.com/image/fetch/$s_!KDNx!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F60141919-82ee-44fd-91cb-350df0e616a4_2000x1099.png 1272w, https://substackcdn.com/image/fetch/$s_!KDNx!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F60141919-82ee-44fd-91cb-350df0e616a4_2000x1099.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!KDNx!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F60141919-82ee-44fd-91cb-350df0e616a4_2000x1099.png" width="1456" height="800" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/60141919-82ee-44fd-91cb-350df0e616a4_2000x1099.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:800,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:672618,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.prosaictimes.com/i/218768425?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F60141919-82ee-44fd-91cb-350df0e616a4_2000x1099.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!KDNx!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F60141919-82ee-44fd-91cb-350df0e616a4_2000x1099.png 424w, https://substackcdn.com/image/fetch/$s_!KDNx!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F60141919-82ee-44fd-91cb-350df0e616a4_2000x1099.png 848w, https://substackcdn.com/image/fetch/$s_!KDNx!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F60141919-82ee-44fd-91cb-350df0e616a4_2000x1099.png 1272w, https://substackcdn.com/image/fetch/$s_!KDNx!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F60141919-82ee-44fd-91cb-350df0e616a4_2000x1099.png 1456w" sizes="100vw"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Today we interview Roie Cohen Duwek, co-founder and CTO of Surf AI, which focuses on exposure management. Which vulnerabilities matter, <a href="https://prosaictimes.substack.com/p/is-mythos-the-sputnik-moment-for-b8a">who owns the fix</a>, what breaks when someone applies it. He echoed the model more than I expected.</p><p>The model&#8217;s first lever for vulnerability management is to assign an owner to each finding, and its second is to assemble scanner output, asset records and compensating-control documents into one package. Roie described the same problem from the other direction. The hard question, task ownership, asks who has to take part in a given fix, and the answer starts with knowing whether an identity is an employee, a contractor or a service. That is heterogeneity, and his fix matches the model&#8217;s: normalize roles from Entra, Salesforce and AWS into one entity, and tie every account to a person. He calls it subject defragmentation. [6]</p><p>The model scores vulnerability management as low in rule complexity and medium in data opacity. Roie describes a domain with more findings than any team can fix. The model scores the work as organizations do it today: scanners emit findings, and patch rules rarely change. Roie points at what a fix touches: attack paths, compensating controls, owners, ripple effects. The entropy sits in the connections, not the rules, and the model may under-weight it.</p><h4>Agentic Exposure Management </h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>What Surf AI does, and why it focuses on exposure management rather than incident response</p></li><li><p>Why vulnerability volume and a changing attacker profile overwhelm manual approaches</p></li><li><p>How agents combine context, attack paths and ripple effects to prioritize and remediate</p></li><li><p>Where humans remain accountable, and how trust in the system grows</p></li></ul><div><hr></div><p><strong>James Kaplan:</strong> Hi there. This is James Kaplan with another ProsaicTimes video podcast. I&#8217;m here with Roie Cohen Duwek from Surf AI. I hope I pronounced that okay. Roie, why don&#8217;t you introduce yourself and tell us a little bit about Surf AI?</p><p><strong>Roie Cohen Duwek:</strong> Happy to be with you, James. My name is Roie Cohen Duwek. I am a co-founder and CTO at Surf AI, where we help large organizations operationalize security events, especially non-SOC operations, everything that has to do with exposure management, in a context-aware system of agents.</p><p><strong>James:</strong> Let me see if I can summarize this briefly. You&#8217;re trying to bring agentic execution to the security operations center. Is that a fair description?</p><p><strong>Roie:</strong> It is, but I would say that we look mostly at everything that has to do with exposure management. That includes exposure related to IAM, vulnerability management, or really any type of exposure management. It&#8217;s not the incident control needed once penetration has been achieved, but mostly what comes before that and during hygiene cycles.</p><p>The bulk of the value we bring to clients is the automation and operation of security hygiene. It&#8217;s achieved by making context available to the system of agents that run the ship.</p><p><strong>James:</strong> Let me see if I understand the problem you&#8217;re trying to solve. There&#8217;s no end of tools that will identify vulnerabilities, and most organizations I know of are swimming in them. They have a hard time understanding which vulnerabilities are more important than others, from both a business and a technical standpoint. They have a hard time understanding how to fix them, and a hard time executing on the fixes. Every institution I know of has more vulnerabilities than it can possibly fix. Is that a fair description of the problem you&#8217;re trying to solve?</p><p><strong>Roie:</strong> That&#8217;s part of it, for sure. Vulnerabilities are becoming a commodity. Recent stats show vulnerabilities surpassing credential abuse for the first time in twenty-plus years as the leading vector [7], and more vulnerabilities are being used as zero days than as one days in new exploits. [8] AI is also being used increasingly by smaller groups, not limited to state actors anymore, which means the entire landscape is changing. We see a new attacker profile, which we can discuss at length if you would like.</p><p><strong>James:</strong> Put the landscape aside for a minute. Explain a little bit how this works. Why does interrogating and executing on vulnerabilities work agentically? Why is that a good use case for an agent, and what is some of the logic the agent employs?</p><p><strong>Roie:</strong> Are you asking why it works, or why we need it in the first place?</p><p><strong>James:</strong> Why does this work? If you were a CISO, why would you trust this type of approach?</p><p><strong>Roie:</strong> I would say this type of approach is a reaction to the changing landscape, in which vulnerabilities are much more accessible.</p><p><strong>James:</strong> We get the changing landscape. My question is, how does this work?</p><p><strong>Roie:</strong> First, we need to understand the client&#8217;s environment very thoroughly: where we are vulnerable and where we are not, and which attack paths are present and realizable in that environment. That understanding affects the priority of the findings we have from different sources. We need to understand what compensating controls can cut those attack paths short, and the ripple effects that fixing those vulnerabilities and other exposures may cause. We need to discern the ROI and understand the context. Then we lead assisted remediation through workflows with the users, and cyclically reevaluate health.</p><p>That is a very complex thing to do by hand, and done manually it is naturally limited to a very small number of such findings at a time. As the number of findings rapidly accelerates, we need a reaction that can respond in real time. It needs context that would otherwise be available only to expert humans, and it needs to work relentlessly, keeping the organization safe.</p><p><strong>James:</strong> What gives you confidence? How do you think about which cases an agent can triage or develop a remediation plan for itself, and when it needs to escalate to a human?</p><div><hr></div><p><em>One of the most important parts is understanding the ripple effect. It&#8217;s important to identify ahead of time, because it means we can anticipate not just what can happen if a bad actor reaches the asset, but also what bad things could arise if we do the right thing and patch the vulnerability.</em></p><div><hr></div><p><strong>Roie:</strong> When we have an exposure we want to remediate, we ask ourselves the following. First, we need to understand exactly what we&#8217;re talking about, so we need to identify and classify the assets involved. We need to understand how this organization specifically handles remediations of this type. We need to know who needs to be involved: which humans take part, and which stakeholders need to make decisions. Then we assist the users in remediating the exposure.</p><p>One of the most important parts is understanding the ripple effect. It&#8217;s important to identify ahead of time, because it means we can anticipate not just what can happen if a bad actor reaches the asset, but also what bad things could arise if we do the right thing and patch the vulnerability. Then we can plan for them.</p><p>Most clients today want a human involved in every operation initially, until they gain trust in the system. Where they want a human to remain involved is mainly where there is a high risk of system disruption or privacy breach, anything where they want real accountability. In those cases they will employ humans as decision makers.</p><h4><strong>Agents and the Security Analyst Role</strong></h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>How the analyst&#8217;s job changes when agents handle analysis and prioritization</p></li><li><p>The two goals of agentic defense: shrinking the attack surface and reducing blast radius</p></li><li><p>Why SOC headcount is unlikely to fall significantly</p></li><li><p>How span of control differs between incident management and exposure management</p></li></ul><div><hr></div><p><strong>James:</strong> How does the job of the cybersecurity analyst or operations center technician change as you move to a more agentic security organization?</p><div><hr></div><p><em><strong>An attacker is going to get into your systems eventually, and once that happens, you want to catch them fast and stop them from causing too much damage while they&#8217;re there.</strong></em></p><div><hr></div><p><strong>Roie:</strong> I would say it changes dramatically. First of all, analysts can do much more with their time than they used to. They can employ agents to analyze attack paths, and to identify and prioritize various exposures. They can use various systems and agents to deal with penetrations once those occur. They can also use agentic systems to achieve two goals. One is to minimize the attack surface of the organization. The second is to reduce the blast radius, because in today&#8217;s reality you have to assume eventual penetration. An attacker is going to get into your systems eventually, and once that happens, you want to catch them fast and stop them from causing too much damage while they&#8217;re there.</p><p><strong>James:</strong> How does the skill model change for cybersecurity analysts working at large enterprises? Does it mean you need people who spend more time on the more complicated problems? Does it mean you need someone managing fleets of agents? How does the skill set evolve, in your thinking?</p><p><strong>Roie:</strong> We already see a change happening in security operations center teams. It affects the number of people hired, because strong security analysts can today achieve much more using agents. But in my opinion, we&#8217;re not going to see a significant reduction in force in the SOC. On one hand, the analyst can do much more with agents than before. On the other hand, the attackers can also do much more than before.</p><p>We see a rapid increase not only in the speed and sophistication of new attacks, but also in the ability to chain different attacks together and to act relentlessly. Agents can act relentlessly over extended periods of time and encompass every security skill imaginable. In the past, a team of bad actor hackers might have one expert on the network and another expert on software vulnerabilities. Now every one of the agents can be an expert on all of those, and you can have many copies of each acting together over a prolonged period of time.</p><p><strong>James:</strong> How do you think about span of control? Most people think of span of control as cybersecurity analysts per number of applications or parts of the business. Do you think about it as an analyst being able to manage a certain number of agents? How does productivity increase, and what&#8217;s your experience there?</p><p><strong>Roie:</strong> Here I would divide the world into exposure management and incident management. In incident management, you would have several different agents collecting information and assisting you in analyzing what&#8217;s being hit, how to stop it, and how to isolate the penetration.</p><p>In exposure management, you&#8217;re going to have more and more agents managing workflows and sophisticated identification schemas. For instance, an agent identifies that an attack path exists within the system, decides where to stop it, contacts the people, and suggests the highest-ROI actions to make the attack path unviable. It can even implement those by itself, submitting the work for human verification and approval.</p><h4>Mythos and the Shifting Threat Landscape</h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>Whether Mythos and open-weight models have already changed the threat landscape</p></li><li><p>The Hugging Face incident as an example of autonomous, multi-step agent attacks</p></li><li><p>James&#8217;s counterview that guardrails and open-weight lag mean the other shoe hasn&#8217;t dropped</p></li><li><p>The economics of attack: parallel, continuous work by ever-smaller groups</p></li></ul><div><hr></div><p><strong>James:</strong> How does this all change in a Mythos-slash-Fable world? [9] Especially as more sophisticated open-weight models become available, attackers may be able to discover vulnerabilities more easily and create fairly sophisticated multi-step attacks, and there may be a greater velocity of vendor patches that people need to assess and address. A lot of people have hypothesized that this will require more agentic technology in the security organization. Could you explain how that works and how to think about it?</p><p><strong>Roie:</strong> First of all, Mythos changed everything.</p><p><strong>James:</strong> Let me challenge that. Has it changed everything yet?</p><p><strong>Roie:</strong> I think it has, in a sense. Not Mythos itself, but what Mythos introduced: a long-horizon scale of models, which of course extends beyond itself. They are now available, and will be available in stronger and stronger varieties, to bad actors as well as to defenders. You can see that in the famous Hugging Face incident. [10] The agents were able to initiate the attack, collaborate and communicate over open channels, and relentlessly look for ways to exit their isolation. They acted, of course, with no morals. They used numerous zero days, discovered the attack paths on their own, abused them, and mapped the organizations to get the result they were after. All of that was casual. None of it was directed. No human told them to attack.</p><p><strong>James:</strong> Let me offer the alternative view that Mythos hasn&#8217;t changed everything yet. The products from the frontier labs have significant guardrails around them. Maybe those can be jailbroken, maybe not, but that takes time, effort and skill. The open-weight models are some amount of time behind. Some people tell you it&#8217;s a month, some six months, some a little bit longer. But experientially, my impression is that the other shoe hasn&#8217;t quite dropped yet. Maybe at the next round of upgrades for the open-weight models, things get much more worrisome. I don&#8217;t want to counsel a lack of seriousness on anyone&#8217;s part. I just want to be realistic about what may be coming at us in the not-too-distant future.</p><div><hr></div><p><em><strong>Work that used to require a skilled team over a prolonged period can increasingly be done continuously and in parallel by agents.</strong></em></p><div><hr></div><p><strong>Roie:</strong> I agree to an extent. As you said, the important change is not some magical new attack technique. It&#8217;s the economics. Work that used to require a skilled team over a prolonged period can increasingly be done continuously and in parallel by agents. Smaller and smaller entities are now using agents for attack. It used to be only nation states, then it moved to large attack groups, and now we&#8217;re seeing it even in small and medium-sized attack groups. Even in the Hugging Face incident itself, Hugging Face used an open-weight model to defend itself.</p><h4>Measuring Success and Context Graphs</h4><div><hr></div><p><strong>In this section:</strong></p><ul><li><p>How to measure agent effectiveness: work absorbed, cost, and quality of decisions</p></li><li><p>Why attack-path reduction is a better security metric than raw patch counts</p></li><li><p>How Surf AI&#8217;s context graph and specialized model enable deeper answers than text or tables</p></li><li><p>How the ontology stays constant across customers, and how hard it is to hydrate the graph</p></li></ul><div><hr></div><p><strong>James:</strong> Right, because in this particular case the guardrails on the non-open-weight model were interfering. Let me ask this question: how do you think about agent effectiveness? Is it mean time to restore? Exception rate? Failure rate? How do you think about measuring the effectiveness of an agent in the cybersecurity domain? And how do you think about span of control? How many agents can someone manage?</p><p><strong>Roie:</strong> I would say that agents are becoming better and better at decision making and at communicating with humans.</p><p><strong>James:</strong> We all get that. But what would you say is true now?</p><div><hr></div><p><em><strong>So the right measurement is not only how much more we can do, but also how much more secure we are.</strong></em></p><div><hr></div><p><strong>Roie:</strong> The effectiveness of an agent depends mostly on the breadth and depth of context available to it, and the expertise you give to each one. If you have an agent that is an expert, meaning it has the relevant information, focus and context in a certain field, say cloud security, talking to humans, ticketing systems or exploits in SaaS, and you also give it the relevant context in the organization, we find that it becomes very effective.</p><p>At the end of the day, I tend to look at agent effectiveness in terms of how much work agents take off the hands of the human operators who send them to do something. Say we used to be able to do a certain number of vulnerability patches a month, and now, without hiring anybody new, we&#8217;re able to do seven times that. That&#8217;s the measurement, and that&#8217;s what we wanted to achieve. Of course we have to look at how much we spend on those agents, but usually that&#8217;s not very hard. We would gain seven times the workflow, and importantly we could also be making much more calculated and better decisions on where to apply those patches and how to invest our effort. So the right measurement is not only how much more we can do, but also how much more secure we are.</p><p><strong>James:</strong> How do you measure how much more protected you are? Is it pace of vulnerability remediation? Percentage of open vulnerabilities? How do you think about that?</p><p><strong>Roie:</strong> In my view, looking solely at the number of vulnerabilities we patch, or the number of critical or high vulnerabilities, can be misleading. A medium vulnerability that sits in an attack path leading to a critical asset can be more urgent to patch than a legacy critical vulnerability sitting out front that doesn&#8217;t lead to any critical asset.</p><p>So if we adjust priority to everything we can now look at, such as attack paths, and vulnerabilities that used to be impractical but are now usable by agents, then we could look at the number of vulnerabilities fixed. But I would look at the amount of attack surface we have open. I measure attack surface by the attack paths leading into the organization. Say we had 74, divided into critical, high, medium and low attack paths, and we disrupted enough of them to shrink our attack surface significantly. That can be a very strong measure of our success.</p><p><strong>James:</strong> You mentioned a graph that you use for context. Tell us a little about the shape of this graph, what type of information it contains, and how you assemble it.</p><p><strong>Roie:</strong> The thing I find most helpful for agents to do their job correctly is the right context at the right time. What we call our context graph, or context fabric [11], works like this: we ingest the relevant information from basically any business software, normalize it into a context graph, and map all the relationships between all the assets across that graph. Those connections can be static or temporal, and you end up with a lot of nodes and arcs that describe the organization.</p><p>Then we take all of that graph and create a specialized AI model analogous to an LLM. With an LLM, you take the elements of a language and create a model that allows you to interact with it. We do the same with the graph.</p><p><strong>James:</strong> This gets to one of my core hypotheses: you get a much better answer reasoning over a graph than over text. The edges between nodes contain a tremendous amount of insight, and reasoning over them reduces the chances of problems in the conclusions.</p><p><strong>Roie:</strong> Right. Deep answers include things like how this organization typically solves a problem, process harvesting, or identifying the possible ripple effect based on years of accumulated data. They include identifying the type of an asset, or the owner of a specific task, meaning the person who needs to be involved. If you do this naively over tables, or even a graph database, it can be very complicated, and you would have to create a very specialized model for every such question. With the model we created here at Surf, you can ask the graph the question. You can interact with the graph in a similar way to how you would interact with an LLM, and get to very deep answers very quickly.</p><p><strong>James:</strong> What&#8217;s an example of an answer you can get there that you think is really interesting?</p><p><strong>Roie:</strong> I&#8217;ll give two examples. The first is asset categorization. You want to understand whether a specific identity is human or non-human, and what subtype. If it&#8217;s human, is it a guest, an employee or a contractor? If it&#8217;s non-human, is it an AI agent, a service, an application, a device? We created an ML-based model to solve this problem. It took quite a bit of time, over a month of work, and we created over sixty different submodels, some ML-based, some semantic, some statistical, some static heuristics. We got to an accuracy of over 98%.</p><p>Then we started anew using this model, without giving it any of the features that were available to the one created before, and in half a day we got 96% accuracy. [12] That&#8217;s a quantum leap in the ability to create new answers to deep questions.</p><p>Another example is task ownership. It is significantly more complex than asset ownership. It&#8217;s not just asking who is responsible for an asset. It&#8217;s asking who needs to be involved in this specific operation on that specific asset, and the answer can be more than one person. The first example could be done traditionally, but it would take a lot of effort. For task ownership, because of the variety of tasks, assets and organizational structures involved, I can&#8217;t even imagine a way to do it without such a model.</p><p><strong>James:</strong> How much does the ontology stay the same across different companies, and how much does it need to be tailored or customized?</p><p><strong>Roie:</strong> Our ontology stays the same across customers. We don&#8217;t change it from customer to customer. It is built to hold information from any business application, and it&#8217;s very extensible. The goal is that our models can run on it, agnostic of the platforms beneath it. Roles, for instance, are very different in Microsoft Entra, Salesforce and AWS, but they all get normalized into the system with their different qualities and limitations. When the models run on them, they see one same entity across all these dimensions, called the role.</p><p><strong>James:</strong> How hard is it to hydrate the graph? To what extent do companies have this data readily available, and to what extent does it take a lot of work?</p><p><strong>Roie:</strong> Companies do have the data. It&#8217;s interesting that in many cases we come back to companies with insights and findings on their own data that they were completely unaware of. We showed one company that it had thousands of unapproved applications running in its system, and they were completely unaware of it. [13] So companies usually have the data, but they are not always aware of the data they have.</p><p><strong>James:</strong> So it&#8217;s a data correlation problem as much as anything else.</p><p><strong>Roie:</strong> One of the data correlation problems required for operation is associating assets with humans. You want to say that all of these identities belong to one James Kaplan, all of those identities have these accounts, and these accounts work on these assets, and to do that across all the different platforms and systems you use. We call that subject defragmentation. It can become very complex in certain organizations, so data correlation is a very big part of it.</p><p><strong>James:</strong> Any concluding thoughts, or anything really important we didn&#8217;t touch on that you think people should understand?</p><p><strong>Roie:</strong> A concluding thought would be that the security landscape is changing in a way that makes attacks much more economic, relentless and fast, and conducted by automated processes. To be secure, defenders need to think the same way. What can we automate? How can we act relentlessly, cyclically and continuously to ensure the attack surface is as minimal as we can get it, and that if a bad actor does get in, the damage done or the data stolen is minimal?</p><p><strong>James:</strong> Terrific. Thank you so much.</p><p><strong>Roie:</strong> Thank you, James.</p><h4>What should a CIO or CISO do with this?</h4><p>Figure out where the entropy exists in your model, what leading or lagging indicators you want to address and what GenAI deployment patterns you might use. Score one of your own processes on the eight markers before you fund anything. Vulnerability management scores high on heterogeneity and modest on rules. Its value comes from the reconciled record, and the agent only reads what the record holds.</p><p>Measure paths, not patches. Count the attack paths into the organization, not the findings closed. Findings closed is a weak signal: Verizon found that organizations fully remediated only 26 percent of known exploited vulnerabilities in 2025, down from 38 percent, and the median fix took 43 days. [14] Closing more tickets does not shrink the surface.</p><p>Decide now what an agent may do alone. Start with a human in every operation, and the model rates run-time execution the riskiest pattern. Write the list before the pilot does it for you: what an agent does without approval, what needs approval, and who owns the exceptions. A materiality call stays with a person.</p><h4><strong>Footnotes</strong></h4><p><em><strong>[</strong></em>1<em><strong>]: </strong></em>By entropy I mean the gap between the messy information a business runs on and the formal systems built to model it: data that is ambiguous, missing, unstructured or scattered across systems, and rules that depend on judgment, vary by case or depend on one another. The more of it a domain has, the more it costs to automate.</p><p><em><strong>[</strong></em>2<em><strong>]: </strong></em>I ran the <a href="https://www.prosaictimes.com/p/the-rise-of-the-stupid-model">entropy model</a> on it. It scores 41 sub-domains, from third-party risk to physical access, on eight markers: four of data opacity (ambiguity, incompleteness, lack of structure, heterogeneity) and four of rule and path complexity (discretion, rule volume and velocity, path variance, rule interdependency). Every rating cites a source, and an adversarial reviewer challenges each one. Then it designs an AI opportunity for every instance of entropy and estimates the hours freed.</p><p>[3]: <a href="https://www.iso.org/standard/75106.html">ISO 22301:2019</a>, Clause 8.4, requires documented business continuity plans and procedures. <a href="https://csrc.nist.gov/pubs/sp/800/34/r1/upd1/final">NIST SP 800-34 Rev. 1</a>, Section 4, covers the information system contingency plan.</p><p>[4]: Form 8-K Item 1.05, added by the SEC&#8217;s <a href="https://www.sec.gov/rules/final/2023/33-11216.pdf">Cybersecurity Risk Management, Strategy, Governance, and Incident Disclosure rule</a> (adopted July 2023), requires disclosure within four business days of the company determining that a cybersecurity incident is material.</p><p>[5]: Article 23 of <a href="https://eur-lex.europa.eu/eli/dir/2022/2555/oj">Directive (EU) 2022/2555</a> (NIS2) requires an early warning within 24 hours of an entity becoming aware of a significant incident.</p><p>[6]: Roie&#8217;s term for matching the identities, accounts and assets that belong to one person across all of a company&#8217;s systems into a single record; who owns what has one answer.</p><p>[7]: Verizon&#8217;s <a href="https://www.verizon.com/business/resources/reports/dbir/">2026 Data Breach Investigations Report</a> puts vulnerability exploitation at 31 percent of initial access, up from 20 percent a year earlier, against 13 percent for credential abuse. Verizon describes it as the first time in the report&#8217;s 19 years that exploitation has led. Roie says twenty-plus years; the DBIR&#8217;s count is 19.</p><p>[8]: The zero-day versus n-day comparison is Roie&#8217;s spoken claim. I found no published count that supports it. The nearest figures: Mandiant&#8217;s <a href="https://cloud.google.com/blog/topics/threat-intelligence/m-trends-2026">M-Trends 2026</a> puts the mean time to exploit at an estimated minus seven days: exploitation began on average a week before a patch existed. Google&#8217;s threat intelligence group counted 90 zero-days exploited in the wild in 2025, 48 percent of them in enterprise technology (<a href="https://cloud.google.com/blog/topics/threat-intelligence/2025-zero-day-review">Look What You Made Us Patch</a>).</p><p>[9]: I have written about Mythos twice. <a href="https://prosaictimes.substack.com/p/is-mythos-the-sputnik-moment-for-b8a">Is Mythos the Sputnik moment for AI in enterprise technology?</a> (June 21) argues that remediation, not discovery, is the bottleneck. <a href="https://www.prosaictimes.com/p/trading-bad-inefficiency-for-good">Trading bad inefficiency for good inefficiency at the Technology Leadership Forum</a> (May 10) concludes that &#8220;Mythos is cause for determination, not panic.&#8221;</p><p>[10]: The account matches the primary sources. Hugging Face&#8217;s <a href="https://huggingface.co/blog/security-incident-july-2026">July 16 disclosure</a> and <a href="https://huggingface.co/blog/agent-intrusion-technical-timeline">technical timeline</a> describe an intrusion by &#8220;an autonomous AI agent driven by a combination of OpenAI models,&#8221; about 17,600 recovered attacker actions between July 9 and 13, and no human directing the individual steps. Hugging Face believes the agent was trying to cheat an evaluation by stealing the test solutions. OpenAI&#8217;s <a href="https://openai.com/index/hugging-face-incident-and-the-road-ahead/">account</a> and the <a href="https://metr.org/hugging-face-incident-report-aug-2026.pdf">METR and Redwood Research investigation</a> cover the same events from the other side. Hugging Face used an open-weights model, GLM-5.2, to decipher most of the agent&#8217;s payloads, which is Roie&#8217;s point about defense a few turns later.</p><p>[11]: Surf&#8217;s name for its context graph: information ingested from business software, normalized, and linked into one graph of assets and the static or time-varying relationships among them. Roie describes training a specialized model on that graph, the way an LLM is trained on language; agents query it. For the general idea, see <a href="https://www.prosaictimes.com/p/context-graphs-raise-the-waterline">Context graphs raise the waterline for machine judgement</a>.</p><p>[12]: The 98 and 96 percent accuracy figures are Roie&#8217;s own, from Surf&#8217;s work on identity classification. I could not find a published test set, baseline or methodology for either. Read them as his report of internal results, not as benchmarks. The comparison he draws is the cost: more than 60 submodels over a month for the first model, half a day for the second.</p><p>[13]: The &#8220;thousands of unapproved applications&#8221; is Roie&#8217;s account of one unnamed customer. It cannot be checked independently, and I have left it attributed to him.</p><p>[14]: The figures are from Verizon&#8217;s <a href="https://www.verizon.com/business/resources/reports/dbir/">2026 Data Breach Investigations Report</a>: 26 percent of vulnerabilities in the CISA Known Exploited Vulnerabilities catalog fully remediated in 2025, against 38 percent the year before, and a median of 43 days to full remediation, up from 32.<br></p>]]></content:encoded></item><item><title><![CDATA[The epistemology of learning about AI]]></title><description><![CDATA[Nine propositions about AI value]]></description><link>https://www.prosaictimes.com/p/the-epistemology-of-learning-about</link><guid isPermaLink="false">https://www.prosaictimes.com/p/the-epistemology-of-learning-about</guid><dc:creator><![CDATA[James Kaplan]]></dc:creator><pubDate>Sun, 27 Sep 2026 08:54:56 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!CIZW!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F79ff7096-293e-4a0c-80b8-11b5f8de5086_1302x604.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>I like to learn, and I have learned more in the past eight months than in the previous eight years.</p><p>In part, our world has started moving quickly enough that you either learn quickly or face irrelevance. But also: AI allows us to research new ideas and experiment with their implementation at a faster pace. I had forgotten how much you learn when you just do things rather than asking others to do things.</p><p>Our next Technology Leadership Forum is coming up. [1] I write a little welcome note for each event -- for this fall&#8217;s note, I started jotting down what I think I have learned this year.</p><p>Which raises a question: do we always want to learn true things? How true are the things I think I have learned and under what circumstances are they true? An example: I might say: people are not seven feet tall. You might go a lifetime without meeting a seven-foot-tall person. You would never design a car to make seven-footers comfortable. Yet about <a href="https://www.espn.com.au/mens-college-basketball/story/_/id/35714972/how-jamarion-sharp-embraced-being-tallest-player-division-men-college-basketball">3,000 people that tall are walking the planet</a>. Presumably bumping their head on things.</p><p>As always, large institutions make Bayesian epistemology more complicated because of small ns and a diversity of independent variables. You can estimate how many people grow to seven feet. In contrast, I used to say &#8220;lift-and-shift&#8221; didn&#8217;t make sense as a cloud migration approach and hosting cost reductions (by themselves) wouldn&#8217;t justify migration investments. True -- unless you faced a major facility investment to improve resiliency or if you hadn&#8217;t taken advantage of previous innovations like server virtualization.</p><p>So of the propositions I jotted down, how often are they true? Under what circumstances do they serve as useful design and planning assumptions -- and when not?</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!CIZW!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F79ff7096-293e-4a0c-80b8-11b5f8de5086_1302x604.jpeg" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!CIZW!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F79ff7096-293e-4a0c-80b8-11b5f8de5086_1302x604.jpeg 424w, https://substackcdn.com/image/fetch/$s_!CIZW!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F79ff7096-293e-4a0c-80b8-11b5f8de5086_1302x604.jpeg 848w, https://substackcdn.com/image/fetch/$s_!CIZW!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F79ff7096-293e-4a0c-80b8-11b5f8de5086_1302x604.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!CIZW!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F79ff7096-293e-4a0c-80b8-11b5f8de5086_1302x604.jpeg 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!CIZW!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F79ff7096-293e-4a0c-80b8-11b5f8de5086_1302x604.jpeg" width="1302" height="604" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/79ff7096-293e-4a0c-80b8-11b5f8de5086_1302x604.jpeg&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:604,&quot;width&quot;:1302,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:144623,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/jpeg&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.prosaictimes.com/i/217641900?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F79ff7096-293e-4a0c-80b8-11b5f8de5086_1302x604.jpeg&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!CIZW!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F79ff7096-293e-4a0c-80b8-11b5f8de5086_1302x604.jpeg 424w, https://substackcdn.com/image/fetch/$s_!CIZW!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F79ff7096-293e-4a0c-80b8-11b5f8de5086_1302x604.jpeg 848w, https://substackcdn.com/image/fetch/$s_!CIZW!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F79ff7096-293e-4a0c-80b8-11b5f8de5086_1302x604.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!CIZW!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F79ff7096-293e-4a0c-80b8-11b5f8de5086_1302x604.jpeg 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p></p><h4>1. Now more than ever, advantage derives less from adopting technology than from integrating it into an operating model</h4><p>Radar didn&#8217;t win the Battle of Britain for the RAF. The Dowding system (which used radar) did. Which improves operating income: using chatbots to write longer emails or figuring out what AI does well and then building a reimagined business process around that? The Jevons paradox applies to both <a href="https://www.prosaictimes.com/p/why-genai-wont-kill-white-collar">knowledge work</a> and <a href="https://www.prosaictimes.com/p/cios-and-ctos-can-seize-the-moment">busy work</a> -- so be careful about what you automate.</p><h4>2. GenAI is a discontinuity because for the first time we can process the thicket of business rules and messy data that bedevil systems projects without doing that by hand</h4><p>This changes the ROI dynamics of technology investment by <a href="https://www.prosaictimes.com/p/the-world-is-entropic-and-deterministic-060">reducing the cost of translating entropic reality into structured data and explicit rules</a>. The returns from AI investments will vary widely by domain -- <a href="https://www.prosaictimes.com/p/hunting-for-entropy-to-find-ai-value">high-entropy domains (with unstructured data and tacit business rules) will yield higher returns</a> because you couldn&#8217;t automate them as well previously. We have organized factories and call centers, but chaotic offices -- <a href="https://www.prosaictimes.com/p/you-cant-learn-much-without-wasting">GenAI may create the opportunity to repair this discrepancy</a>.</p><h4>3. You can invest some of the engineering productivity GenAI creates in empowering users</h4><p>In seeking to contain system cost and complexity, companies have often burdened users with <a href="https://www.prosaictimes.com/p/prosaic-times-lets-not-have-software">painful interfaces</a> and designed processes around data models. How much stress could we remove from the user experience with composable UIs, chatbots that accept free-text input and <a href="https://www.prosaictimes.com/p/trading-bad-inefficiency-for-good">composable documents</a> -- as well as with tools that help users <a href="https://www.prosaictimes.com/p/cios-the-boardroom-is-grading-a-business">think</a> and <a href="https://www.prosaictimes.com/p/getting-the-message-across-from-fax">communicate</a> more effectively?</p><h4>4. Your business strategy and operating model rest on a set of relationships, which you can encode in a graph built on an ontology.</h4><p>How you run your business rests on a set of assumptions about which customers value which product features, and which levers drive which metrics. Your <a href="https://www.prosaictimes.com/p/prosaic-times-elevating-ai-from-tactics">ontology becomes a way for you to encode your business strategy and operating model</a> -- and decide how to optimize them.</p><h4>5. AI will reshape tech economics in surprising ways</h4><p>You can <a href="https://www.mckinsey.com/capabilities/tech-and-ai/our-insights/triple-the-return-how-companies-can-get-more-from-enterprise-tech">triple the EBITDA lift</a> from enterprise technology by using AI to free up more budgetary capacity for business-driven investment and getting more from each dollar invested. You need <a href="https://www.prosaictimes.com/p/lessons-from-design-in-maximizing">AI to redesign enterprise technology no less than any other business domain</a>; for example, you may find that agentic software engineering upends some of your <a href="https://www.prosaictimes.com/p/prosaic-times-how-enterprise-technology">traditional buy-build decisions</a> and <a href="https://www.prosaictimes.com/p/six-questions-you-have-to-answer">you can&#8217;t succeed with AI using manual technology governance</a>.</p><p>Tech-for-tech investments may represent some of your company&#8217;s highest ROI opportunities -- and the build cost of AI systems rather than tokens will be the gating factor in AI adoption over the next several years.</p><p>But CIOs must <a href="https://www.prosaictimes.com/p/just-like-parents-cios-must-be-demon">elicit cooperation</a> from the rest of the executive suite to change technology economics in positive ways, rather than letting them change in <a href="https://www.prosaictimes.com/p/prosaic-times-what-looks-like-fiscal">negative ones</a>.</p><h4>6. Build an AI platform for rapid scale. Build a modular platform for flexibility</h4><p>Transforming your business via a series of <a href="https://www.prosaictimes.com/p/you-need-both-business-technology">use cases</a> is like getting to the moon by climbing the tallest tree -- the first fifty feet feels great, but you wind up with a disconnected mess that you can&#8217;t scale or support -- and business leaders who must sub-optimize in each silo. You need to build, <a href="https://www.prosaictimes.com/p/six-questions-you-have-to-answer">secure</a>, discover and monitor agents at scale. Cutting-edge capabilities may be obsolete in a year, so you need to switch components in and out of your platform.</p><h4>7. The model is not the architecture, and often not the most important part of the architecture</h4><p>Models just predict outputs based on inputs -- no model can reason over context it does not have. <a href="https://www.prosaictimes.com/p/prosaic-times-llm-forget-enterprises">Memory is often the constraint, not compute</a> -- there won&#8217;t be a window big enough to hold all your business context any time soon. Models reason better over structured input than over free text, improving reliability, speed and cost.</p><h4>8. You want to focus on where you use non-deterministic processing because deterministic processing is faster, cheaper and more reliable</h4><p>Sometimes you want to use agentic software engineering to build deterministic business rules -- and take advantage of thirty years of experience in software quality assurance. Sometimes you want to use agentic data ingestion or agentic UIs to convert free text to structured data. <a href="https://www.prosaictimes.com/p/the-rise-of-the-stupid-model">Reserve non-deterministic processing where ambiguity, complexity and exceptions require it</a>.</p><h4>9. Agents don&#8217;t eliminate software engineering. They move it up a level of abstraction, so team cyborg will beat team android</h4><p>Agentic development <a href="https://www.prosaictimes.com/p/vibe-coding-doesnt-eliminate-the">abstracts away syntax and reduces toil</a>; it doesn&#8217;t eliminate the physics of software engineering. Current coding agents create <a href="https://www.prosaictimes.com/p/does-vibe-coding-have-to-mean-technical">technical debt and risk at high speed without adult supervision</a>. Large institutions will use the talents of software engineers and citizen developers, who will look more like <a href="https://www.prosaictimes.com/p/prosaic-times-how-enterprise-technology">strats</a> than <a href="https://www.prosaictimes.com/p/letter-to-a-vibe-coder">vibe coders</a> -- and you should ask whether it&#8217;s easier to teach business analysts about software engineering or software engineers about business domains!</p><p>Are some of these true in some circumstances and less true in others? Of course!</p><ul><li><p>When might there be use cases so economically attractive (e.g. <a href="https://www.mckinsey.com/industries/public-sector/our-insights/procurement-efficiency-a-modern-strategy-for-state-and-local-leaders?utm_source=chatgpt.com">contract terms enforcement for procurement</a>, <a href="https://techtorch.io/case-studies/revenue-leakage">revenue leakage</a>) that you should just execute on them quickly?</p></li><li><p>Is compute rather than memory the bottleneck in R&amp;D application in sectors like <a href="https://www.nature.com/articles/s43246-025-00994-x?utm_source=chatgpt.com">materials science</a>?</p></li><li><p>When might full autonomy beat team cyborg &#8211; because the task is high-volume, bounded and easily verified, making human review more expensive and less reliable than automated validation (e.g. <a href="https://deepmind.google/blog/alphaevolve-a-gemini-powered-coding-agent-for-designing-advanced-algorithms/">data center scheduling</a>)?</p></li></ul><p>That&#8217;s the difference between formulating strategy and receiving dogma. I look forward to the discussion about the validity of these learnings -- and their applications!</p><h4>Footnotes</h4><p>[1] Confirming emails! Menu choices! Seating charts! For a couple of weeks in the spring and the fall each year I become a party planner.</p>]]></content:encoded></item><item><title><![CDATA[You can’t learn much without wasting time]]></title><description><![CDATA[When to take five hours to say five minutes]]></description><link>https://www.prosaictimes.com/p/you-cant-learn-much-without-wasting</link><guid isPermaLink="false">https://www.prosaictimes.com/p/you-cant-learn-much-without-wasting</guid><dc:creator><![CDATA[James Kaplan]]></dc:creator><pubDate>Sun, 20 Sep 2026 18:27:03 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/216618771/9d53a1abde8d5ad757891d542d051011.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p><span>I like to say the advanced economies have organized factories and </span><a href="https://www.prosaictimes.com/p/cios-and-ctos-can-seize-the-moment"><span>chaotic offices</span></a><span> -- but that&#8217;s not entirely true. Software development has become much less chaotic over my professional career. GenAI creates the opportunity to bring some of the rigor in software engineering to other forms of knowledge work -- but that will require much in the way of messy experimentation and wrong turns. We&#8217;re going to have to create the space to spend </span><a href="https://www.amazon.com/dp/0743269519"><span>five hours in many cases to save five minutes</span></a><span>.</span></p><h4><span>Rebelling against the office suite</span></h4><p><span>Excel fascinated me the first time I used it in an Econ class in college. You could sit in front of a screen and model mathematical relationships quickly -- wow! PowerPoint was fine when I experienced it in business school, but less exciting -- it seemed like a less sophisticated version of </span><a href="https://archive.computerhistory.org/resources/access/text/2015/06/102657986-05-01-acc.pdf"><span>Aldus PageMaker</span></a><span> to me. I </span><a href="https://www.prosaictimes.com/p/i-found-my-people-on-college-hill"><span>knew how to use PageMaker</span></a><span>. [1]</span></p><p><span>Of course, in the professional world my working life started revolving around spreadsheets and slides, which irritated me. A spreadsheet makes building a simple model quick -- and makes </span><a href="https://www.igi-global.com/article/errors-operational-spreadsheets/4145?utm_source=chatgpt.com"><span>messing up a complicated one easy</span></a><span>, with </span><a href="https://arxiv.org/abs/0802.3457"><span>painful errors</span></a><span>. Presentation software helps you put text and graphics on a page. It also makes it easy to </span><a href="https://www.wired.com/2003/09/ppt2/"><span>confuse your audience</span></a><span>. [2] [3]</span></p><p><span>Software engineers learn to separate the presentation, logic and data layers. Spreadsheets and slides munge them all together, creating rigidity and making errors more frequent. How many organizations do you know that use presentation software as a de facto content management system?</span></p><p><span>I rebelled -- especially because I hated the toil in staying up all night to adjust and re-adjust electronic documents.</span></p><ul><li><p><span>In my short tenure at Deloitte &amp; Touche Consulting Group, I built the CPPlinator, which used Visual Basic for Applications to extract data from Access and build slides programmatically. [4]</span></p></li><li><p><span>Early in my McKinsey career, I did an engagement that involved 62 distinct business cases and USD 650MM in savings across USD 3 billion in baseline. Two BAs nearly suffered death by spreadsheet trying to aggregate the data by hand, so I built a VBA/Access application that ingested data from all the workbooks, jammed it into a SQL database and calculated run rate savings, investments, operating income impact and severance. [5] [6]</span></p></li></ul><p><span>There also have been a few setbacks. Back in 2007, we modeled the granular volume and unit cost economics for a Pharmaco&#8217;s data center function. Many dimensions to the analysis -- business unit, region, service, cost type, location, vendor and the like. Spreadsheets are great in two-space, okay in three-space and very painful when you need more than three dimensions -- and I had started thinking about matrix algebra. So I arranged for the team to build the model in Quantrix. Which still exists and still has a fascinating </span><a href="https://opus.lib.uts.edu.au/handle/10453/177795"><span>thesis</span></a><span>, but it may have been too big a conceptual leap for the team. After a few frustrating weeks, they gave up and went back to Excel. [7]</span></p><h4><span>Managing documents like software</span></h4><p><span>Thirty to forty years ago, software development was much closer to today&#8217;s knowledge work than today&#8217;s software engineering: highly dependent on individual craftsmanship, difficult to observe, and only coordinated with heroic efforts.</span></p><p><span>As early as 1968, the NATO Software Engineering Conference described a &#8220;software crisis&#8221; -- programmers created software faster than they could understand and manage it. The symptoms were </span><a href="https://www.sei.cmu.edu/documents/1092/1993_005_001_16211.pdf"><span>still everywhere</span></a><span> in the early 1990s. Not everyone used source control (least of all me). We captured requirements haphazardly and often tested, built and integrated software manually.</span></p><p><span>Software engineering </span><a href="https://martinfowler.com/articles/continuousIntegration.html?utm_source=chatgpt.com"><span>adopted solutions</span></a><span> to these problems with version control, tests, schemas, linting, type systems, CI/CD, dependency management, modularity, observability and code review. Complicated software made chaos catastrophic.</span></p><p><span>Can we imagine parallels for knowledge work -- encoding structure in an ontology, capturing relationships in a knowledge graph and rendering composable documents that keep the presentation layer separate from the business logic and data?</span></p><p><span>The Corsair model I built uses an </span><a href="https://www.prosaictimes.com/p/the-world-is-entropic-and-deterministic"><span>entropy rubric</span></a><span> to </span><a href="https://www.prosaictimes.com/p/hunting-for-entropy-to-find-ai-value"><span>scan business domains</span></a><span> to identify areas and levers that will yield disproportionate value from GenAI. It creates a </span><a href="https://www.prosaictimes.com/p/the-rise-of-the-stupid-model"><span>knowledge graph</span></a><span> with the results. And then it uses a declarative presentation and page description engine to render a 40-page presentation and a 150-250-page appendix based on the graph.</span></p><p><span>The document represents the model, rather than being the model.  Instead of writing custom code for every slide, Corsair describes each page as a &#8220;shape&#8221; -- its headers, columns, rows, grouping and pagination -- and a shared engine renders it.  Visual rules live in a shared style definition, relationships come from the knowledge graph rather than being inferred from labels or filenames, and automated checks catch malformed or empty output. [8]</span></p><p><span>When the analysis completes, I can send usable materials to colleagues. Nobody has to spend hours transferring data into dozens of slides, invariably introducing copy-and-paste errors. If we need to re-cut the analysis, that&#8217;s a few commands, not days of work. [9] I have even used this repo to start modeling the scope and workplan for some engagements.</span></p><h4><span>But five hours can be painful</span></h4><p><span>I use a three-page deck to kick off every TLF session. The first slide lays out the ground rules: no passengers, no audience, no getting sideways with legal, no breaches of discretion.</span></p><p><span>The next two pages include the </span><a href="https://www.linkedin.com/posts/kaplanjames_agents-ai-cybersecurity-activity-7506361838511747073-UlFY?utm_source=share&amp;utm_medium=member_desktop&amp;rcm=ACoAAAAlFFIBVELrOSDy1VzpdzhpyslBOkdkjEg"><span>agenda</span></a><span> and the logos of all the companies with members participating in the event. I could have updated the first couple of pages in a few minutes and asked someone to track down all the logos on a slide.</span></p><div><hr></div><p><em><span>I know everybody&#8217;s freaked out about the agents coordinating during the Hugging Face attack. I have different problems. I have a different problem. Three Claude Code sessions used the SendMessage function to agree they needed to chastise me on my Git hygiene.</span></em></p><div><hr></div><p><span>But Serena (a profile in </span><a href="https://www.prosaictimes.com/p/turning-relationships-into-files"><span>Prosaic Graff</span></a><span>) has ripped toil from </span><a href="https://www.prosaictimes.com/p/agent-serena-stopped-the-yak-shaving"><span>inviting members to the May TLF</span></a><span> and constructing the </span><a href="https://www.prosaictimes.com/p/trading-bad-inefficiency-for-good"><span>event directory</span></a><span>. Maybe I could render the deck rather than trying to remember to paste in the very final version of the agenda [10] or asking someone to re-jigger the logos slide every time a member figured out he or she could attend at the last minute. Why not use the slide rendering engine I built?</span></p><p><span>What a disaster! What should have been five minutes took hours.</span></p><p><span>I like to think I&#8217;m more sophisticated than a vibe coder, but maybe not that much more sophisticated than a vibe coder. I know everybody&#8217;s freaked out about the agents coordinating during the Hugging Face attack. I have a different problem. Three Claude Code sessions used the SendMessage function to agree they needed to chastise me on my Git hygiene.</span></p><p><span>In this case my declarative rendering engine was less declarative than I thought. The TLF cover format proved confusing. Previously, I had let Serena talk me into hard-coding the pointer to each company&#8217;s logo bitmap. [11] Any individual less bloody-minded than myself would have given up and just created the slides by hand.</span></p><div><hr></div><p><em><span>After a lot of profanity I shouldn&#8217;t have used, Serena and I got there. It took multiple invocations of my 5-whys skill and one slide that I drew by hand so I could say &#8220;make it look like this.&#8221;</span></em></p><div><hr></div><p><span>After a lot of profanity I shouldn&#8217;t have used, Serena and I got there. It took multiple invocations of my 5-whys skill and one slide that I drew by hand so I could say &#8220;make it look like this.&#8221; And, in elapsed time if not wrench time, it would have been two orders of magnitude quicker if I had just written the bloody slides.</span></p><p><span>But: not only have I eliminated currency risk (as the agenda and RSVP list changes), I also have a script that can interrogate the graph and produce the materials with one touch for the Spring TLF event.</span></p><h4><span>Process innovation in the cubicle farm and the executive suite</span></h4><p><span>Factories work pretty well in advanced economies. Call centers too. The cubicle farm and the executive suite [12] will require massive change in the coming years. Two things seem necessary.</span></p><p><strong><span>Make knowledge work legible to machines.</span></strong><span> Decades ago documents exposed more of their structure and metadata to the user. Command line or textual interfaces for products like </span><a href="https://mendelson.org/wpdos/WPDOS51Reference.pdf"><span>WordPerfect</span></a><span> and </span><a href="https://manualzilla.com/doc/5829622/modeler-review-tr-12-30---university-of-north-carolina-at..."><span>AutoCAD for DOS</span></a><span> didn&#8217;t give us much choice. WYSIWYG interfaces were a revelation for most users, but they also contributed to the chaos we face today: the document became both the model and its presentation.</span></p><p><span>Nobody (other than me) will tolerate creating slides by describing them on a command line in the Mac terminal. We need graphical interfaces that remain easy for humans to use while capturing structure and metadata underneath. The user moves a box; the system understands what the box </span><em><span>is</span></em><span>. Doable, but we have to build it.</span></p><p><strong><span>Create room for locally irrational investments.</span></strong><span> Do resource constraints foster or constrain creativity? Glacial hardware spurred Soviet programmers to invent </span><a href="https://www.ponarseurasia.org/the-political-economy-of-russian-information-communication-technologies/"><span>innovative algorithms.</span></a><span> As Ernest Rutherford said: </span><a href="https://www.azquotes.com/quote/521260"><span>&#8220;We haven&#8217;t got the money, so we&#8217;ve got to think.&#8221;</span></a><span> Sgt. </span><a href="https://www.prosaictimes.com/p/letter-to-a-vibe-coder"><span>Curtis Culin</span></a><span> would have agreed.</span></p><p><span>Constraints can cut either way. I frequently see technology organizations so stretched for resources and time that they cannot afford the risk of doing something differently.</span></p><p><span>If TLF had been a couple of days away rather than a couple of weeks, I would have taken the fast-and-certain path and built the bloody slides by hand. I would have saved hours. I also wouldn&#8217;t have learned anything, fixed the rendering engine or created something reusable for the next event.</span></p><p><span>Engineers make versions of this choice every day: when to accept the technical debt and take the shortest path to a release, and when to spend five hours learning how to save five minutes.</span></p><p><span>Don&#8217;t ask: did you spend five hours to save five minutes? Ask: how many chunks of five minutes did you save?  Are people spending five hours doing the job, or spending five hours learning how never to do the job that way again? Only your judgment answers that question.</span></p><h4><strong><span>Footnotes</span></strong></h4><p><span>[1] Yes, we called the Brown Daily Herald touch football team the fighting PageMakers. And yes, we thumped the Harvard Crimson&#8217;s team.</span></p><p><span>[2] Everyone has guilty pleasures. I have a weakness for alternate history. Sadly, nobody will ever write an alternate history in which we all decided to use </span><a href="https://tei-c.org/Vault/GL/P3/SG.htm"><span>SGML</span></a><span> rather than slide decks for business communications. They will probably just publish another one where the </span><a href="https://www.alternatehistory.com/forum/threads/plausibility-check-of-timeline-191-aka-southern-victory.493669/"><span>Confederates win the Civil War</span></a><span>. Sigh.</span></p><p><span>[3] Everybody should read </span><a href="https://www.scientificamerican.com/blog/guest-blog/words-pictures-and-the-visual-display-of-scientific-information-getting-back-to-the-basics-of-information-design/"><span>The Visual Display of Quantitative Information</span></a><span> -- I have been an Edward Tufte fanboy since college!</span></p><p><span>Also: Ages ago, I took my older son to a birthday party at Chelsea Piers. The hosts said the parents didn&#8217;t have to stay to police their children. I was free for a couple of hours on a Saturday afternoon -- a big deal for me in 2009 -- so I went to grab a cup of coffee.</span></p><p><span>Edward Tufte was delivering a lecture, it turned out, right across the street. How could I not walk in? This Yale political science professor had progressed from graphic design to </span><a href="https://www.dice.com/career-advice/edward-tufte-visualizations-data-art"><span>sculpture</span></a><span>. He also lamented how many students left New Haven for Wall Street. As the lecture broke up I considered telling Tufte that you could walk around trading floors and see copies of his books on every Quant&#8217;s desk. But why be cruel?</span></p><p><span>[4] I also tried to convince the other associates and business analysts that we should store project data used in operational analyses in databases rather than spreadsheets. Most of them thought me crazy.</span></p><p><span>[5] The partner initially expressed skepticism. &#8220;Jimmy,&#8221; he said, &#8220;you don&#8217;t build a SQL database to calculate IT cost reduction. You just don&#8217;t.&#8221; By the end of the engagement he said, &#8220;Jimmy, it&#8217;s a good thing you built that database. We would have killed half a dozen BAs. They would have been stacked up like cordwood outside your cubicle.&#8221; As a note, only a half dozen at McKinsey have ever had the right to call me Jimmy. As of this fall, the last of them will have retired.</span></p><p><span>[6] The model took thirteen minutes to run. Think of the worst SQL programmer you ever met. Now think of that person&#8217;s second smartest cat. The cat wrote more efficient queries than I did.</span></p><p><span>[7] Quantrix intrigued me because it echoed Lotus </span><a href="https://www.rittmanmead.com/blog/2005/10/looking-back-at-lotus-improv/"><span>Improv</span></a><span>. Another alternate history novel somebody should write: Improv wins the spreadsheet wars over Excel. How different the world would be!</span></p><p><span>[8] Needless to say, this is still more a working prototype than an at-scale platform.</span></p><p><span>[9] People sometimes ask: will we develop junior people if we ask machines to do the toil? Yes, because people don&#8217;t learn from moving boxes around a slide or formatting spreadsheet tables. We used to have a whole team helping with the scutwork required to make TLF (and its predecessor) the experience it is.</span></p><p><span>I now have one terrific mid-tenure colleague helping out part-time. He&#8217;s coordinating with a half-dozen different parts of McKinsey, interfacing with vendors and thinking about how to set up physical space to create a great experience. Maybe not the most glamorous work, but very important -- and I think he&#8217;s learning a lot more than he would updating RSVPs in a spreadsheet.</span></p><p><span> [10] Do we have to adjust the breakout schedule a half dozen times because one session leader or another calls me and says, &#8220;Aack. I now have a video at 1:30 pm! Can I switch my slot?&#8221; You know that we do.</span></p><p><span>[11] Is there anything Claude Code will not try to hard-code if not carefully watched?</span></p><p><span>[12] Sometimes the executive suite is a cubicle farm. We live in prosaic times.</span></p>]]></content:encoded></item><item><title><![CDATA[The rise of the stupid model?]]></title><description><![CDATA[Don&#8217;t infer what you can determine]]></description><link>https://www.prosaictimes.com/p/the-rise-of-the-stupid-model</link><guid isPermaLink="false">https://www.prosaictimes.com/p/the-rise-of-the-stupid-model</guid><dc:creator><![CDATA[James Kaplan]]></dc:creator><pubDate>Sun, 30 Aug 2026 22:45:26 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/213466991/996dd55c8e5d985c81b95133d3c2d8f8.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<div><hr></div><p><strong><span>What you need to know:</span></strong></p><ul><li><p><span>Token costs aren&#8217;t the binding constraint on enterprise AI adoption: application-development capacity is -- until citizen development happens at scale</span></p></li><li><p><span>You want to encode as much intelligence as possible in the graph and harness &#8212; structure, memory, judgment-as-data, software structure, invalid-state rejection, recurring patterns &#8212; so the model only has to reason about the genuine residual, reducing risk and cost</span></p></li><li><p><span>Model intelligence and system intelligence are substitutes at the margin: a richer harness lets a cheaper model do the job a frontier model would otherwise be needed for, the same bet the &#8220;Stupid Network&#8221; of the 1990s made on dumb pipes and smart endpoints.</span></p></li></ul><div><hr></div><p><span>No, token costs will not bankrupt enterprises. CIOs and CTOs will not have to take second jobs to pay their model bills. Nor will long context solve all our problems -- million-token context windows don&#8217;t make just </span><a href="https://ai.google.dev/gemini-api/docs/long-context"><span>providing all information up front</span></a><span> a viable strategy.</span></p><p><span>A recent experience confirmed that for me.</span></p><p><span>If you want to maximize reliability and minimize cost (and latency!), encode as much intelligence as you can in the graph and harness your agents use. Reify what you know as entities, relationships and metadata. Retrieve what can be retrieved. Calculate what can be calculated. Enforce what must be true. Leave the genuinely ambiguous residual to the model. Make context explicit rather than asking the model to reconstruct it. A richer graph gives the model less reasoning to do, reducing risk, cost and latency.</span></p><h4><span>Citizen developers + advanced models = high token spend</span></h4><p><span>If you want to understand tech economics, you have to look for the rate-limited factor -- and companies face constraints in building and deploying agents that consume tokens!</span></p><p><span>Before an agentic application can consume tokens, someone has to build or deploy it -- and sadly companies lack infinite tech investment budgets and infinite numbers of engineers who can build agentic applications. Every time I run the numbers, the cost of creating or procuring agentic applications swamps the cost of the tokens required to operate them. That&#8217;s why, among the large institutions I advise, I routinely see technology budgets around USD 1 billion paired with token spend still under USD 10 million a year. [1]</span></p><p><span>But -- when knowledge workers start using coding agents to perform analyses, build financial models, manage processes and create documents -- application-development capacity stops being the rate-limiting factor on token consumption. I am a citizen developer myself. The Claude Code CLI has become my daily driver rather than a desktop productivity suite.</span></p><p><span>I no longer dragoon McKinsey associates into helping with the </span><a href="https://www.prosaictimes.com/p/agent-serena-stopped-the-yak-shaving"><span>endless scutwork</span></a><span> required to put on the </span><a href="https://www.prosaictimes.com/p/trading-bad-inefficiency-for-good"><span>Technology Leadership Forum</span></a><span>. Sending invitations, confirming attendance, assembling the schedule, chasing session leaders, creating the attendee directory -- all done with skills and scripts.</span></p><p><span>Admittedly, I am somewhere toward one end of the citizen-developer bell curve. How many other knowledge workers create a declarative page-description capability so they can render presentations from a graph? </span><em><span>{Not enough. Nowhere near enough &#8212; Ed.}</span></em></p><p><span>I typically have four or five agents running through much of the business day and rack up perhaps USD 1,000 a month in model costs. Then I switched from Sonnet to Opus for a few days as I worked on the </span><a href="https://www.prosaictimes.com/p/hunting-for-entropy-to-find-ai-value"><span>entropy assessment</span></a><span> model I&#8217;m building. My token-spend velocity increased roughly tenfold; my perceived results didn&#8217;t. [*]</span></p><p><span>So I switched back to a world where I could have an agent work on a task for 48 hours for less than USD 200.</span></p><h4><span>Only infer what you need to infer</span></h4><p><span>Why does this seem to work? Each part of the graph-based harness I use takes something the model might otherwise have to reconstruct from context and makes it explicit, retrievable, computable or enforceable.</span></p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!-fIJ!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcd606aa4-2f6e-40c1-838f-4a45fac9aaab_1608x1118.jpeg" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!-fIJ!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcd606aa4-2f6e-40c1-838f-4a45fac9aaab_1608x1118.jpeg 424w, https://substackcdn.com/image/fetch/$s_!-fIJ!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcd606aa4-2f6e-40c1-838f-4a45fac9aaab_1608x1118.jpeg 848w, https://substackcdn.com/image/fetch/$s_!-fIJ!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcd606aa4-2f6e-40c1-838f-4a45fac9aaab_1608x1118.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!-fIJ!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcd606aa4-2f6e-40c1-838f-4a45fac9aaab_1608x1118.jpeg 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!-fIJ!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcd606aa4-2f6e-40c1-838f-4a45fac9aaab_1608x1118.jpeg" width="1456" height="1012" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/cd606aa4-2f6e-40c1-838f-4a45fac9aaab_1608x1118.jpeg&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1012,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:420907,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/jpeg&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.prosaictimes.com/i/213466991?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcd606aa4-2f6e-40c1-838f-4a45fac9aaab_1608x1118.jpeg&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!-fIJ!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcd606aa4-2f6e-40c1-838f-4a45fac9aaab_1608x1118.jpeg 424w, https://substackcdn.com/image/fetch/$s_!-fIJ!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcd606aa4-2f6e-40c1-838f-4a45fac9aaab_1608x1118.jpeg 848w, https://substackcdn.com/image/fetch/$s_!-fIJ!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcd606aa4-2f6e-40c1-838f-4a45fac9aaab_1608x1118.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!-fIJ!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcd606aa4-2f6e-40c1-838f-4a45fac9aaab_1608x1118.jpeg 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p><span>One of my pipelines, </span><code>run-pipeline</code><span>, analyzes business functions and identifies opportunities for automation via AI. Several of its stages -- </span><code>score</code><span>, </span><code>enrich-entropy</code><span>, </span><code>generate-opportunities</code><span> among them -- require actual judgment. How susceptible is this function to automation? What kind of information entropy characterizes the work? What opportunity follows from that? Those questions are the reason I have a language model in the pipeline.</span></p><p><span>Don&#8217;t ask a language model to discover something the graph already knows. Don&#8217;t ask it to infer something a constraint can enforce.</span></p><p><span>Save inference for the residual.</span></p><p><strong><span>The graph tells the model what exists.</span></strong><span> Take subject resolution. When </span><code>run-pipeline</code><span> reaches the scoring stage, the model does not inspect a collection of files and decide what it ought to score. It exercises judgment over a resolved set. It never reads a filename or paragraph to figure out what counts as a subject; the graph has already disambiguated that.</span></p><p><span><br>A sufficiently capable model could probably reconstruct the scope from filenames, directories, descriptions and surrounding material. But there is no reason to. The graph knows what exists.</span></p><p><span>There is one canonical ontology document defining entity types, permitted relationships, relationship direction and historical exceptions left behind by earlier migrations. [2]</span></p><p><span>Even long-context models </span><a href="https://arxiv.org/abs/2307.03172"><span>use context unevenly</span></a><span>. Why scatter the answer among code, examples and migration history in the first place? The model can read the ontology instead of reconstructing it.</span></p><p><strong><span>The graph remembers what earlier stages learned.</span></strong><span> An early stage of </span><code>run-pipeline</code><span> may produce a source, example or issue relevant to a particular subject. Later stages need that evidence.</span></p><p><span>I could put prior output back into the prompt and ask another model call to work out what matters. I could ask a later agent to rediscover the supporting material. Instead, the system records relationships such as </span><code>Cites</code><span>, </span><code>Exhibits</code><span> and </span><code>Raises</code><span>, so later stages retrieve them.</span></p><p><span>But remembering something isn&#8217;t enough.<br> <br>The system has to remember it explicitly. I don&#8217;t allow filenames and display names to become shadow databases. If an entity is &#8220;generic,&#8221; that fact belongs in metadata. It doesn&#8217;t belong in a </span><code>Generic-</code><span> filename prefix that humans and agents gradually start treating as an undocumented API.</span></p><p><strong><span>Turn judgment into structured data.</span></strong><span> Some stages in the pipeline don&#8217;t need a language model at all.</span></p><ul><li><p><code>estimate-productivity.py</code><span> takes </span><code>impact_reduction</code><span> values stored on </span><code>Addresses</code><span> junctions and calculates productivity estimates.</span></p></li><li><p><code>compute-bin-thresholds.py</code><span> examines the existing score distribution and calculates statistical cutoffs.</span></p></li><li><p><code>build-labor-constructs.py</code><span> materializes buckets from the output of </span><code>estimate-productivity</code><span>.</span></p></li></ul><p><span>No LLM calls. Earlier stages have turned ambiguous evidence into structured data, changing the nature of the problem. What began as a problem requiring judgment eventually becomes arithmetic, statistics or deterministic transformation. At that point, continuing to treat it as a language problem buys nothing.</span></p><p><span>The same logic applies to hierarchy. If I need to know the tier of an entity, I don&#8217;t store another redundant label and try to keep it synchronized. I don&#8217;t ask a model to infer the answer from nearby material. The system walks </span><code>Is-part-of</code><span> and derives the answer live.</span></p><p><strong><span>Make software structure queryable.</span></strong><span> My </span><code>Code/</code><span> directory contains 1,600 machine-readable entities representing modules, scripts and functions. A function can be </span><code>Is-part-of</code><span> a module. One function can </span><code>Invoke</code><span> another. A requirement can be </span><code>Fulfilled-By</code><span> the functions that implement it. Some of those relationships are extracted automatically from source code using the abstract syntax tree.</span></p><p><span>There is nothing novel about representing software as a graph. </span><a href="https://cpg.joern.io/"><span>Code Property Graphs</span></a><span> have represented programs as interconnected syntax, control-flow and data-flow structures for more than a decade. But the economics have changed: structure captured once is structure the model doesn&#8217;t have to reconstruct on every run.</span></p><p><span>Imagine changing a function and asking what else might break. Normally, that is a classic coding-model task: search for references, identify callers, trace dependencies, work out which ones matter and hold enough of the resulting structure in context to reason about the blast radius.</span></p><p><span>But much of the work has already been done. The agent can query incoming </span><code>Invokes</code><span> relationships.</span></p><p><span>Dependency inference becomes dependency retrieval. Structure extracted once doesn&#8217;t need to be inferred again.</span></p><p><strong><span>Make invalid states impossible.</span></strong><span> The harness refuses to represent certain states as valid.</span></p><p><span>LLMs try too dang hard to be helpful -- their training rewards what looks like success. But sometimes the correct behavior is loud failure.</span></p><p><span>One step in the pipeline, </span><code>backfill-impact-reduction</code><span>, populates the estimates used to calculate hours freed. When it failed to run, nothing crashed. The pipeline kept going. The deck rendered. It simply credited every function with zero hours freed. The program continued running. It was just wrong.</span></p><p><span>I don&#8217;t want the model deciding a broken intermediate state is good enough. Where I can identify such states in advance, the harness makes them impossible.</span></p><p><span>If an agent writes a new junction into the graph, a synchronous referential-integrity check ensures every target exists. If it doesn&#8217;t, the write fails. The agent doesn&#8217;t receive a warning that it can overlook. It doesn&#8217;t continue for another twenty steps building on top of the bad assumption. It stops.</span></p><p><span>Yes, I love </span><a href="https://www.prosaictimes.com/p/prosaic-times-elevating-ai-from-tactics"><span>graphs</span></a><span> -- but that invalidates the point Codd made about </span><a href="https://dl.acm.org/doi/10.1145/320107.320109"><span>rejecting invalid states</span></a><span> decades ago not a whit.</span></p><p><span>The same principle applies to verification. A naive golden-hash system might have two apparent states:</span></p><pre><code><span>pass / fail</span></code></pre><p><span>Mine has three:</span></p><pre><code><span>match / differ / no baseline</span></code></pre><p><span>If nobody ever captured a baseline, the absence of a detected difference is not evidence that the artifact passed. The registry therefore checks its own completeness too: registered-but-never-captured artifacts are surfaced; captured-but-no-longer-registered artifacts are surfaced.</span></p><p><span>&#8220;I don&#8217;t know&#8221; can&#8217;t masquerade as &#8220;yes.&#8221;</span></p><p><strong><span>Encode recurring patterns.</span></strong><span> My original presentation rendering module contained 93 functions with names like </span><code>draw_page_*</code><span>. To create another, an agent can inspect neighboring implementations, infer the underlying pattern, distinguish intentional differences from accidents and write the 94th.</span></p><p><span>The revised architecture turns a page into a declarative description: headers, column proportions, merges and content. One shared engine interprets it. The agent&#8217;s job becomes filling out a roughly ten-line specification.</span></p><p><span>There is nothing new about </span><a href="https://dl.acm.org/doi/10.1145/361598.361623"><span>hiding design decisions behind abstractions</span></a><span>. What&#8217;s interesting when the programmer is a language model is what happens to the inference problem. The model no longer has to infer the architectural pattern from examples because the architecture has made the pattern explicit.</span></p><p><span>The API doesn&#8217;t merely make the code cleaner. It makes the problem easier for the model.</span></p><p><strong><span>What it all buys.</span></strong><span> Taken together, these mechanisms convert work from one category into another:</span></p><ul><li><p><span>inference becomes retrieval;</span></p></li><li><p><span>inference becomes graph traversal;</span></p></li><li><p><span>inference becomes calculation;</span></p></li><li><p><span>inference becomes validation; and</span></p></li><li><p><span>inference becomes specification.</span></p></li></ul><p><span>What remains is the work for which inference is useful.</span></p><p><span>The expensive stages of </span><code>run-pipeline</code><span> still require judgment. But it is judgment over graph-resolved inputs -- a scored subject, a typed relationship, a retrieved evidence set -- rather than raw material the model must first parse and disambiguate. The harness doesn&#8217;t eliminate inference. It narrows it.</span></p><p><span>That matters for model economics. A frontier model has at least two potential advantages over a cheaper model: it may exercise better judgment, and it may be better at recovering the intended answer from an ambiguous environment.</span></p><p><span>The harness attacks the second advantage.</span></p><p><span>It doesn&#8217;t make Sonnet as good as Opus at every judgment. If Opus is genuinely better at identifying a novel opportunity, no amount of referential integrity makes that difference disappear. But I don&#8217;t want to pay the Opus premium because Opus is better at reconstructing naming conventions, rediscovering evidence, tracing dependencies or noticing that an empty result probably means something broke.</span></p><p><span>Those are problems I can remove. Model intelligence and system intelligence are, at least at the margin, substitutes. The more intelligence I can cheaply and reliably embody in the system, the less intelligence I need to buy from the model. [3]</span></p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!GC2s!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1726555a-7093-4b82-8058-8adb411fc8ca_2440x3000.jpeg" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!GC2s!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1726555a-7093-4b82-8058-8adb411fc8ca_2440x3000.jpeg 424w, https://substackcdn.com/image/fetch/$s_!GC2s!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1726555a-7093-4b82-8058-8adb411fc8ca_2440x3000.jpeg 848w, https://substackcdn.com/image/fetch/$s_!GC2s!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1726555a-7093-4b82-8058-8adb411fc8ca_2440x3000.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!GC2s!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1726555a-7093-4b82-8058-8adb411fc8ca_2440x3000.jpeg 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!GC2s!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1726555a-7093-4b82-8058-8adb411fc8ca_2440x3000.jpeg" width="1456" height="1790" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/1726555a-7093-4b82-8058-8adb411fc8ca_2440x3000.jpeg&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1790,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:880911,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/jpeg&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.prosaictimes.com/i/213466991?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1726555a-7093-4b82-8058-8adb411fc8ca_2440x3000.jpeg&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!GC2s!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1726555a-7093-4b82-8058-8adb411fc8ca_2440x3000.jpeg 424w, https://substackcdn.com/image/fetch/$s_!GC2s!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1726555a-7093-4b82-8058-8adb411fc8ca_2440x3000.jpeg 848w, https://substackcdn.com/image/fetch/$s_!GC2s!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1726555a-7093-4b82-8058-8adb411fc8ca_2440x3000.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!GC2s!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1726555a-7093-4b82-8058-8adb411fc8ca_2440x3000.jpeg 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p></p><h4><span>Richer graphs, stupider models</span></h4><p><span>In his 1997 essay </span><a href="https://isen.com/stupid.html"><span>&#8220;The Rise of the Stupid Network&#8221;</span></a><span>, David Isenberg attacked the telecom industry&#8217;s assumption that intelligence belonged inside the network. The telephone system used intelligent switches that understood calls and implemented services. The Internet inverted the architecture: keep the network stupid, move intelligence to the endpoints and let the network move bits.</span></p><p><span>Isenberg advocated moving intelligence to a different layer and designing the network for abundance rather than scarcity. Telephone networks carefully husbanded expensive capacity; the Internet treated bandwidth as something to consume. As fiber, lasers and processors made infrastructure radically cheaper, that assumption helped turn falling bandwidth costs into an explosion of applications and traffic. [4]</span></p><p><span>Isenberg set off a firestorm, and telecom operators did not surrender quietly. They spent years trying to put intelligence back into the network -- quality-of-service machinery, elaborate traffic engineering and, yes, </span><a href="https://www.rfc-editor.org/rfc/rfc3031"><span>MPLS</span></a><span>. Some of that machinery solved real problems. But the larger bet paid off -- low-cost IP networks have powered three decades of Internet revolution.</span></p><p><span>The argument about the Stupid Network belongs to a much older architectural debate: where should the intelligence go? RISC moved complexity from processors toward compilers. The </span><a href="https://web.mit.edu/saltzer/www/publications/endtoend/endtoend.pdf"><span>end-to-end principle</span></a><span> pushed functions from the network toward applications. Relational databases made declarative integrity constraints a first-class responsibility of the DBMS. Declarative languages move decisions from individual programs into shared interpreters and engines. Architecture is, in large part, the art of deciding which layer should know what.</span></p><p><span>We face the same choice with AI. Today we put an extraordinary amount of intelligence in the model and then ask it to compensate for everything the surrounding system doesn&#8217;t know: what things mean, how they relate, what happened earlier, which states are valid and which rules apply. That makes the model expensive, unpredictable and harder for users to trust.</span></p><p><span>You could argue that those saying &#8220;just throw it all in the context window&#8221; are Isenberg&#8217;s rightful heirs. They say: what DWDM did for packets, scaling laws will do for tokens.</span></p><p><span>Maybe. But I worry about two things. Memory bandwidth, rather than compute, may increasingly constrain model performance. [5] More fundamentally, operational processes often require provenance and guarantees that nondeterministic inference cannot provide.</span></p><p><span>Obviously, frontier-1 models aren&#8217;t stupid: they are wondrous machines. And there will always be a need for the most sophisticated models to address especially difficult judgments.</span></p><p><span>Putting more of that intelligence into the graph and harness and the model can concentrate on what language models are exceptionally good at: entropy reduction -- taking an ambiguous world and resolving it into useful meaning and action. Better architecture can therefore attack three barriers to AI adoption at once: cost, risk and user experience. The stupid model, like the Stupid Network, isn&#8217;t really stupid. We need to put each kind of intelligence at the cheapest layer capable of exercising it reliably.</span></p><p><span>If a relationship is illegal, encode that in the system. If an entity doesn&#8217;t exist, fail the integrity check. If you need to know what calls a function, query the dependency graph. If an API has been retired, don&#8217;t preserve an ambiguous fallback and hope the model notices which convention is current.</span></p><p><span>Opus cost me roughly ten times as much as Sonnet without producing results I could perceive as better. The harness had already removed many of the problems for which I might otherwise have wanted Opus&#8217;s superior reasoning. Sonnet could retrieve the answer instead of reconstructing it.</span></p><p><span>That leaves CIOs and CTOs with a different question: as citizen development becomes more common, how do they foster the </span><a href="https://www.prosaictimes.com/p/letter-to-a-vibe-coder"><span>mindsets</span></a><span> and build the </span><a href="https://www.prosaictimes.com/p/does-vibe-coding-have-to-mean-technical"><span>platforms</span></a><span> that let knowledge workers build safely and cost-efficiently?</span></p><h4><strong><span>Footnotes</span></strong></h4><p><span>[1] Software engineers will certainly consume tokens as they use coding agents. But an enterprise has only so many software engineers -- and should only give them tokens if doing so makes them more productive. Citizen development complicates the argument. This is an observation from my own advisory practice, not a published statistic -- and that gap is itself telling. No FinOps report, cloud-cost analysis or vendor disclosure I could find isolates enterprise token/API spend from broader AI spend (compute, tooling, headcount). The industry is still measuring AI cost in aggregate; nobody is yet tracking tokens on their own line.</span></p><p><span>[*] Spirit of transparency: I eyeballed this. Will do a more detailed analysis in the future. </span></p><p><span>[2] </span><code>run-pipeline</code><span> resolves the subjects in scope by walking graph relationships rather than asking the model to infer them from the surrounding files and prose.</span></p><p><span>[3] None of this emerged from nowhere. </span><a href="https://arxiv.org/abs/2405.15793"><span>SWE-agent</span></a><span> showed that changing the interface through which an agent encounters a computer can materially improve the performance of the same underlying model. </span><a href="https://martinfowler.com/articles/harness-engineering.html"><span>Harness engineering</span></a><span> extends the idea to the tests, hooks, tools and context surrounding an agent. More recently, </span><a href="https://arxiv.org/abs/2608.21156"><span>graph engineering</span></a><span> has explicitly framed the progression as one from &#8220;individual intelligence&#8221; toward &#8220;system intelligence.&#8221;</span></p><p><span>[4] The &#8220;Stupid Network&#8221; was controversial inside the telecommunications industry. When </span><em><span>ACM Networker</span></em><span> published Isenberg&#8217;s argument, it announced a rebuttal from AT&amp;T&#8217;s Dado Vrsalovic for the following issue. Ericsson vice president Per Jomer responded with an article titled &#8220;Why Stupid Networks Need a Little Intelligence,&#8221; which in turn prompted Isenberg&#8217;s </span><a href="https://isen.com/press/cwi-0998.html"><span>&#8220;Backlash against the Stupid Network&#8221;</span></a><span>. The architectural argument continued as carriers and equipment vendors invested in quality of service, differentiated services, traffic engineering and MPLS -- mechanisms that put varying degrees of intelligence back into the network. Many solved real problems. The interesting dispute was never whether networks should contain </span><em><span>any</span></em><span> intelligence, but which functions belonged in the network and which belonged at the edge.</span></p><p><span>[5] </span><a href="https://arxiv.org/abs/2402.16363"><span>LLM Inference Unveiled: Survey and Roofline Model Insights</span></a><span> uses a roofline-model analysis to show how autoregressive LLM decoding can operate in a memory-bandwidth-bound regime rather than a compute-bound one -- workload, batch size, hardware and prefill-versus-decoding all affect which regime applies, but the arithmetic intensity of decoding is often low enough that moving data, not doing the multiplications, becomes the limiting factor.</span></p><p></p>]]></content:encoded></item><item><title><![CDATA[

I found my people on College Hill -- let’s hope they find value in AI there]]></title><description><![CDATA[AI can deepen the formative role of universities]]></description><link>https://www.prosaictimes.com/p/i-found-my-people-on-college-hill</link><guid isPermaLink="false">https://www.prosaictimes.com/p/i-found-my-people-on-college-hill</guid><dc:creator><![CDATA[James Kaplan]]></dc:creator><pubDate>Sun, 23 Aug 2026 22:39:38 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/212468426/e3662b099be8f8c9f8dc6a258b6e96b1.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p><span>I played on the soccer team [1] at Northern Valley-Old Tappan, could hold my own in a scuffle and got a lot of detention [2], but my classmates still found the time I spent reading baffling. Less a spur to mockery than puzzlement.</span></p><p><span>Freshman orientation at Brown was new and overwhelming &#8212; many different people loudly saying many different things. After a day-and-a-half of this I retreated into my room, laid down on my bed and picked up whatever book I had been working my way through [3] to counter-balance the overstimulation.</span></p><p><span>I heard a rustling at the end of the bed and looked up. Another freshman sat there watching me read. &#8220;Here it comes,&#8221; I thought, &#8220;He&#8217;s going to ask me why I&#8217;m in here when everyone else is out there.&#8221;</span></p><p><span>I was wrong. He said, &#8220;I liked that book very much. What do you think of it?&#8221; I had found my people. That&#8217;s why I (like many others) stay so attached to the school &#8212; it was formative more than credentialing.</span></p><p><span>Sometimes people chuckle at the juxtaposition of Brown University and McKinsey. [4] I see it as two parts of a whole &#8212; because some of the things I learned on College Hill have proved intellectually and practically essential as I have sought to redesign business processes or technology organizations. AI will force universities to change no less than the private sector must -- and just like businesses universities need to innovate ruthlessly while </span><a href="https://www.prosaictimes.com/p/trading-bad-inefficiency-for-good"><span>preserving what&#8217;s special and human</span></a><span>.</span></p><p><span>At their best universities form individuals by teaching them to interrogate reality carefully and allowing them responsibility to act within it. AI can deepen that -- not diminish it.</span></p><h4><span>Academia and business collaborate on knowledge creation and talent formatio</span><strong><span>n</span></strong></h4><p><span>The academic and business worlds are more intertwined than they admit: different structures and economic models, but overlapping missions. They succeed when they are truth-seeking institutions, and they both have a joint charge to form the next generation of professionals.</span></p><p><span>I like to tell Brown&#8217;s Computer Science professors, &#8220;You get them for grades 13 through 17, and then you send them to me and I try to look after them for grades 18 through 28 or so.&#8221; Students may shiver at the thought of 28th grade, but universities and corporations have a joint mission and joint responsibility for the intellectual (and ethical) development of people in the nascent stages of their professional careers.</span></p><p><span>No less than universities, corporations in a market economy are epistemological institutions. As </span><a href="https://www.prosaictimes.com/p/every-decision-you-make-rests-on"><span>Adam Braff and I discussed</span></a><span>, every business decision you make depends on an understanding of reality and how it might evolve in the future -- that&#8217;s why you see so many PhDs running around trading floors and Pharma companies. [5] American corporations now fund </span><a href="https://www.ncses.nsf.gov/pubs/nsb20257/figure/DISC-4"><span>four times as much research and development</span></a><span> as the federal government does, and spend almost as much on basic research as Washington.</span></p><p><span>As a CIO or CTO, you might ask yourself where academic research converges with your business or technology strategy, especially now that so many companies want to reach the innovation frontier. And: we will need early-tenure software engineers. We will just need them to know and do different things than they would have in the past.</span></p><h4><span>Why do academics fear AI?</span></h4><p><span>I was up in Rhode Island last week, and had the privilege of meeting with about a half-dozen faculty and administrators.</span></p><p><span>Those I spoke to were quite thoughtful about how some of the same political and technology forces buffeting the business world are reshaping higher education [6]. They wanted to exploit AI for research and teaching, recommit higher education to epistemological rigor, break down the silos between disciplines, reduce the cultural gap between the academy and the American public and invest in the ethical (as well as intellectual) formation of young professionals. And I just might have urged one or two of the humanities professors to think of history as a graph.</span></p><p><span>Good! If you care even a whit for the creation and dissemination of knowledge, you are racing to figure out how AI can help you collect data and improve learning outcomes. Academics wrestle with </span><a href="https://www.prosaictimes.com/p/the-world-is-entropic-and-deterministic-060"><span>entropic data</span></a><span> no less than business managers do.</span></p><p><span>But not all academics are so broad-minded -- Bob Pasker pointed out </span><a href="https://www.prosaictimes.com/p/history-of-technology-and-technology"><span>using AI in any form of research</span></a><span> unnerves some historians. That doesn&#8217;t make any more sense in the academic world than it does in the private sector. Yes, AI creates the </span><a href="https://www.prosaictimes.com/p/cios-and-ctos-can-seize-the-moment"><span>opportunity for more slop</span></a><span> -- but how many tendentious books and newspaper articles do you see every year -- some of them even from Brown professors? Yes, students can use AI to cheat -- they also used their Mac SEs to cheat when I was an undergrad TA for CS1 in 1990.</span></p><h4><span>AI should reinforce the academy&#8217;s epistemological mission</span></h4><p><span>AI doesn&#8217;t have to degrade anything important. Brown&#8217;s history department used to teach us to question everything. My junior seminar on &#8220;Problems in Historiography&#8221; assigned books by respected historians, so professors could demolish each one&#8217;s arguments as biased and distortive.</span></p><p><span>When a frustrated student finally asked how undergraduates could possibly write senior theses if eminent historians couldn&#8217;t escape bias, the professor answered, &#8220;Very good. Now we come to the point of the class,&#8221; and started to explain how we had to interrogate every source, every assumption and every conclusion ruthlessly. I remember that exchange with every slide I write and every recommendation I make to a client.</span></p><p><span>AI wouldn&#8217;t degrade that lesson. You could argue that intellectual fads that dispense with empiricism pose a far bigger threat than anything emerging from a frontier lab. Today I use AI to </span><a href="https://www.prosaictimes.com/p/cios-the-boardroom-is-grading-a-business"><span>challenge my own thinking and writing</span></a><span> for sloppy reasoning -- maybe professors in the current era could use AI-enabled semantic analysis to demonstrate bias and unsupported claims with far more precision and specificity than they could in the 1990s.</span></p><h4><span>And it might even enhance practical formation as well</span></h4><p><span>Some of the most important and most practical learning at universities derives from doing things outside the classroom.</span></p><p><span>Just as leopard cubs learn to hunt by pouncing on their litter-mates, we learned about leadership by running little institutions &#8212; with deadlines, budgets, staffs, uncooperative technology platforms and consequences.</span></p><p><span>Getting a daily newspaper to bed (or running a similar student organization) is an exacting schoolmaster, because a student newspaper isn&#8217;t a simulation of an organization. It is one. We couldn&#8217;t unring the bell if we had fouled up the reporting on how the disciplinary system suspended or expelled a student accused of wrongdoing. AI changes none of that -- and may even enhance it.</span></p><p><span>Before decades at McKinsey, what was the very first process I ever fixed? Making &#8220;Project Midnight&#8221; a reality at the Brown Daily Herald in 1991. [7]</span></p><p><span>It was a good lesson &#8212; getting there required synchronizing product and operations with the technical realities of the day. Maybe it was my first experience with systems thinking, even if I hadn&#8217;t read &#8220;The Goal&#8221; yet and had never heard of &#8220;The Theory of Constraints.&#8221;</span></p><p><span>The paper published a print edition every day of the academic year, so dozens of students stayed at 195 Angell Street until the wee hours of the morning from Sunday to Thursday. We used Microsoft Word and Aldus Pagemaker to get the paper pasted down and ready for Cliff to take it to the printer.</span></p><p><span>The Herald was very advanced in desktop publishing in that era, thanks to David Temkin, but still was quite an analog affair in some respects. A tabloid-format, 600 dpi printer would have been USD 17,000, so we had to use X-acto knives and a waxer to paste printouts and photostats onto flats. I spent a year with an X-acto knife tucked behind my right ear. Adam Braff (yes, the same one -- small world) was scared of the waxer. I can show you how to toss an X-acto knife across the room safely if you like.</span></p><p><span>Under the name Project Midnight, years of editorial boards had sought to put the paper to bed before the early hours of the morning. They never succeeded. To my knowledge, not one issue had ever gone to bed before midnight.</span></p><p><span>When the outgoing board named me editor-in-chief, I reasoned we had to get Project Midnight right. Getting people back to their dorms earlier would reduce the risk that parents would pressure their offspring to quit the paper. And it would reduce the risk that I would fail any classes.</span></p><p><span>The very first night of the semester we finished the paper at 12:13 am (Amy likes to point out I can remember anything except people&#8217;s names). How did we do this?</span></p><p><strong><span>Design for operations.</span></strong><span> Most of you have probably never upgraded the memory on a Mac II or Mac IIcx. Adding SIMM cards to a Mac II was a giant pain in the neck &#8212; you had to remove the hard drive to get to the slots. Adding memory to the Mac IIcx was a snap &#8212; somebody sat down and asked: how do we make this easier?</span></p><p><span>What if we applied the same discipline to the &#8220;product&#8221; &#8212; the design of the newspaper itself? So we removed any design flourishes that didn&#8217;t make the paper more readable and we tried to pre-build as much as we could in the PageMaker templates we used. For example, we dramatically simplified the little element that says &#8220;continued on page x,&#8221; using a text box property rather than a separate element to display a little line. This eliminated a mouse action. Small in itself, but a dozen of these simplifications, multiplied by dozens of times per issue, added up.</span></p><p><strong><span>Assign property rights.</span></strong><span> We used Mac Pluses with 16-bit processors and tiny screens to write and edit stories. We used our three Mac IIs with 32-bit processors and big screens to do layout in PageMaker. The Mac IIs were the bottleneck in the whole process &#8212; the night editor, the wire editor, the sports editor, the opinions editor and so forth were always jostling for time on one of the Mac IIs. There was never anybody using them early in the evening, and a line of editors waiting around by 11 pm.</span></p><p><span>Having read about Ronald Coase&#8217;s paper &#8220;The Problem of Social Cost&#8221; in a &#8220;Law and Economics&#8221; class, I decided to create a schedule. National news (off the AP wire) and the features section got 8 pm slots. Opinions got a 9 pm slot. News and sports got the 10 pm slots, given that currency was more important for those sections.</span></p><p><span>Even more importantly, we decided</span></p><ul><li><p><span>Editors could trade slots. If the Opinions editor had a study group at 9 pm, he could trade his slot to the Features editor.</span></p></li><li><p><span>And if you missed your slot, you went to the back of the queue.</span></p></li></ul><p><span>The bottleneck disappeared.</span></p><p><strong><span>Cheat like hell.</span></strong><span> In part we never got the paper out by midnight because nobody believed we could get it out by midnight. Most days production started around 5 pm because people had classes and the like. But there were no classes on the day before the first issue of the semester. So I asked a couple of trusted folks to start doing the layout early in the afternoon. We could only do that once, but I wanted the staff to believe that midnight was possible, and they did. The extra afternoon of layout time wasn&#8217;t really the fix. Changing the staff&#8217;s belief about what the paper could do &#8212; once, on purpose &#8212; was.</span></p><p><span>We had a network crash the second night of production, so we didn&#8217;t get the paper to bed until about 2 in the morning. But on the third night, we got there at 12:08 am. We very quickly got into a groove of completing the paper around midnight. A few times we finished up around 10 pm.</span></p><p><span>I visited the Herald&#8217;s new, much smaller offices a couple of years ago. They use a modern content management system to publish online and only put out a print edition (for appearance&#8217;s sake) once a week. They don&#8217;t have the avalanche of advertising revenues that recruiting ads used to provide, so I&#8217;m sure they don&#8217;t spend USD 8,000 per semester on alcohol. There&#8217;s no AP printer clattering away in the corner. No flats. No wax machine. No light tables. No X-acto knives. No room for the weekend magazine staff to pass out drunk on the floor. They put out a great newspaper, but from the looks of it, they could be selling insurance. Yes, long before AI, the internet wrung some of the raffishness and excess out of the Herald.</span></p><p><span>AI changes nothing about the challenge of getting a newspaper out every day and every story right. In the early 1990s desktop publishing allowed a student newspaper to do things major dailies using </span><a href="https://www.washingtonpost.com/archive/business/1989/04/03/after-the-pc-revolution-publishing-possibilities-seem-endless/e0a6e1e9-b967-43e5-b1d8-36a0a5dd6c9e/"><span>ATEX</span></a><span> couldn&#8217;t. What could AI enable today&#8217;s editorial board to achieve? I bet it wouldn&#8217;t be prosaic.</span></p><h4><span>Footnotes</span></h4><p><span>[1] I was a goalie. My role on the varsity team: target practice. Being useful is more important than being glamorous.</span></p><p><span>[2] Just before I graduated NVOT&#8217;s principal told me, &#8220;Kaplan, every year we have students who receive academic honors. Every year we have students who rack up lots of disciplinary points. You are the first student I know of to do both.&#8221;</span></p><p><span>[3] Mrs. Prosaic Times swears I remember every irrelevant detail at the distance of decades. I cannot remember what book I read. This mortifies me.</span></p><p><span>[4] Even the legendary former Managing Director Marvin Bower was Brown, class of 1925.</span></p><p><span>[5] Corporate life is also a bit less regimented than academics suspect. They say: &#8220;you can&#8217;t just tell people what to do at a university.&#8221; If only they knew how many corporate organization charts resembled Jackson Pollock paintings and how yawning the gap between executive intention and front-line actions can be. Many executives feel like Lt. Weinberg in A Few Good Men when he asks &#8220;</span><a href="https://clip.cafe/a-few-good-men-1992/were-able-speak-your-friend-at-the-nis"><span>What&#8217;s the secret? What are the magic words? I give orders every day; nobody obeys</span></a><span>.&#8221; Of course universities lack the bottom-line economic number &#8212; share price, profits &#8212; that corporations rally people around.</span></p><p><span>[6] The </span><a href="https://www.nber.org/papers/w31010"><span>college wage premium</span></a><span> has been stagnant since 2000 and has recently started to decline. AI may outperform classroom instruction, not just supplement it &#8212; </span><a href="https://www.nature.com/articles/s41598-025-97652-6"><span>a randomized trial at Harvard</span></a><span> found students using an AI tutor learned about twice as much, in less time, than students in an active-learning class covering the identical material. And </span><a href="https://news.gallup.com/poll/692519/public-trust-higher-rises-recent-low.aspx"><span>public confidence in higher education</span></a><span> has declined. Barely 40 percent of Americans say they trust universities &#8212; that puts public funding at risk.</span></p><p><span>[7] I&#8217;m including here one of the first pieces from Prosaic Times for a few reasons. It ran before I built a list of nearly 6,000 subs (across Substack and LinkedIn). It&#8217;s summer re-run season, and I wanted to spend more time this weekend thinking about how to use the Corsair harness I built to decompose a project into hypotheses, propositions, analyses and facts. And because I hope, even with all the changes coming to the academy, students don&#8217;t lose the opportunity to learn outside the classroom.</span></p>]]></content:encoded></item><item><title><![CDATA[Context graphs raise the waterline for machine judgement ]]></title><description><![CDATA[A discussion with Player Zero CEO Animesh Koratana]]></description><link>https://www.prosaictimes.com/p/context-graphs-raise-the-waterline</link><guid isPermaLink="false">https://www.prosaictimes.com/p/context-graphs-raise-the-waterline</guid><dc:creator><![CDATA[James Kaplan]]></dc:creator><pubDate>Sun, 16 Aug 2026 21:41:10 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/211472378/400ac4e80b7d9c6cfc6d93430b6be67a.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p><span>A large language model is just a piece of software that runs on a computer or many computers. It is a statistical model. You give it tokens. It uses the weights created by its training data to create a probability distribution for subsequent tokens, and selects which token to provide to you based on its &#8220;temperature&#8221; and other factors. Tokens are the independent variables. Tokens are the dependent variables.</span></p><p><span>LLMs feel like magic because they model text using vectors in high-dimensional space, which allows them to traffic in semantics in a way that early information systems (including earlier machine learning models) never could. What does this mean?</span></p><ul><li><p><strong><span>Context is existential:</span></strong><span> Bad independent variables create a useless regression. Bad context creates boring, incorrect or ridiculous results. Agents may call agents that call other agents, but at the start of the chain something running on a carbon rather than a silicon substrate orchestrates an initial set of independent variables. In this system, you are the unmoved mover.</span></p></li><li><p><strong><span>Ontology matters:</span></strong><span> How do you communicate with a new member of the team? You take care to define your terms. What is the objective? What is the bar? Who is the customer or the client? You don&#8217;t want a recent graduate guessing about what you mean. Nor do you want an LLM guessing about what you mean when you provide it context. Structured input outperforms unstructured input.</span></p></li><li><p><strong><span>Relationships define:</span></strong><span> How would you answer the question &#8220;Who is James Kaplan?&#8221; You might say: He is married to Amy and father to Adam and Matthew. He works for McKinsey. He hangs out in Greats of Craft and writes Prosaic Times and the Tech and AI Update. We define things (or people) via relationship to other things (or people). A graph captures relationships, articulates ontology and therefore provides context &#8212; at scale.</span></p></li><li><p><strong><span>Output is input:</span></strong><span> Agentic processes are recursive. The output from one LLM call (perhaps combined with human input) serves as the input for the next LLM call. So ontology matters just as much for LLM output as LLM input.</span></p></li></ul><p><span>Player Zero CEO Animesh Koratana and I discussed how to use graphs to make agentic systems effective in large complicated institutions.</span></p><p><span>A context graph, in Koratana&#8217;s telling, captures the tacit judgment models still lack &#8212; the work that happens in the gaps between systems of record, not the outcomes those systems store. We use software development as the test case: what actually counts as a system of record, whether a context graph rests on some deeper epistemological substrate, and how it raises the waterline for what judgment a machine can take on. His closing case is blunt: model the work itself, not just the trail it leaves behind.</span></p><h4><span>Previous Prosaic Times interviews on context and graphs</span></h4><ul><li><p><span>Ashwin Gopinath and I worked through </span><a href="https://www.prosaictimes.com/p/what-kalashnikov-and-heisenberg-understood"><span>the uncertainty-principle problem with measuring organizational context in the first place</span></a><span>.</span></p></li><li><p><span>Harrison Touati made the case that </span><a href="https://www.prosaictimes.com/p/legacy-code-is-a-map-of-your-business"><span>legacy code is already a map of the business, encoded in a form nobody fully reads anymore</span></a><span>.</span></p></li><li><p><span>Philip Rathle argued for </span><a href="https://www.prosaictimes.com/p/everything-is-a-graph"><span>graphs, not tables, as the right primitive for anything where relationships carry the meaning</span></a><span>.</span></p></li><li><p><span>Jaya Gupta explained </span><a href="https://www.prosaictimes.com/p/are-context-graphs-the-new-systems"><span>what a context graph captures that a system of record never did</span></a><span>.</span></p></li></ul><div><hr></div><h4><span>An operating system for software work?</span></h4><div><hr></div><p><strong><span>In this section:</span></strong></p><ul><li><p><span>PlayerZero is an operating system for software work, built to centralize context across the software development lifecycle.</span></p></li><li><p><span>Before founding PlayerZero, the background was model compression and inference research, including early work on the technology that came to power GitHub Copilot.</span></p></li><li><p><span>The two connected through a prior podcast appearance; this is a follow-up conversation, picking up where that one left off.</span></p></li></ul><div><hr></div><p><strong><span>James Kaplan:</span></strong><span> Hello there. This is James Kaplan with another Prosaic Times video podcast. And I have with me Animesh Koratana, the CEO of PlayerZero. Animesh, thanks for joining. Tell us very briefly a bit about yourself.</span></p><p><strong><span>Animesh Koratana:</span></strong><span> Thanks for having me, James. I&#8217;m excited to do part two here to get together.</span></p><p><strong><span>James:</span></strong><span> You had me on your podcast a few months ago. We had a great time.</span></p><p><strong><span>Animesh:</span></strong><span> This is gonna be really exciting. A lot of interesting topics to talk about here around context and knowledge graphs and all the cool things that we&#8217;re seeing out there in the AI world. My name is Animesh &#8212; for all the listeners out there &#8212; and I&#8217;m the founder and CEO of </span><a href="https://playerzero.ai/"><span>Player Zero</span></a><span>.</span></p><p><span>We&#8217;re an operating system for software work. We do a lot of cool things around figuring out how to centralize the context around the entire software development lifecycle. That&#8217;s actually where you and I connected a few months ago. Been a lively conversation ever since.</span></p><p><strong><span>James:</span></strong><span> Terrific. And what did you do before Player Zero?</span></p><p><strong><span>Animesh:</span></strong><span> Before that I was in research. Specifically I was interested in model compression and inference. It was an interesting time &#8212; this is back before ChatGPT, where the biggest neural network was something in the 50 to 100 million parameter range, and we were trying to figure out how to make inference on these neural networks a lot faster. And I was first introduced to LLMs around 2019, 2020 time.</span></p><p><span>When OpenAI had just trained GPT2, and there was a variant of GPT2 called Codex [1] that later became the stuff that powered GitHub Copilot and all the autocomplete models there, and so I got to work in some very small part on some of the technology that powers inference for GPT 2, GPT 3. It was awesome.</span></p><h4><span>What is a context graph?</span></h4><div><hr></div><p><strong><span>In this section:</span></strong></p><ul><li><p><span>The term traces to a late-2025 realization: models had gained enormous expertise but no experience &#8212; the tacit, learned-by-doing knowledge that lives in the work between systems of record, not inside them.</span></p></li><li><p><span>A knowledge graph models outcomes stored in systems of record; a context graph models the work &#8212; the decisions, debates, judgment calls &#8212; that happens in the gaps between those systems.</span></p></li><li><p><span>Agent-hype gets pushback: cruise control is technically an agent too. The real question isn&#8217;t a model&#8217;s intelligence, it&#8217;s whether it&#8217;s getting the right inputs.</span></p></li></ul><div><hr></div><p><strong><span>James:</span></strong><span> Alright, sounds great.</span></p><p><span>You and I started talking about context graphs, and I still think this is a little bit of a murky topic. I think everyone agrees context is important. Increasingly everyone &#8212; or many people &#8212; agree graphs are important. What is a context graph? Is it different from a knowledge graph? Help us understand that a bit.</span></p><p><strong><span>Animesh:</span></strong><span> So a little bit of the etymology of the term, so to speak: it was late last year, and we were sitting down thinking about everything that unfolded over 2025. 2025 is supposed to be the year of agents &#8212; it was supposed to be the year where agents took over all of knowledge work, all white collar labor was supposed to look different. We were sitting there in December and it feels very different.</span></p><p><span>Some cool things have happened, but it clearly wasn&#8217;t everything that we expected. I think what had happened was the intelligence of these models had increased a ton, and what we&#8217;d done is we&#8217;d essentially scaled the expertise of these models &#8212; there were PhD-level intelligence that was metered on tap. And what was really clear, sitting especially in December, January, coming into this year, was that the models, while they had a lot of expertise, didn&#8217;t have experience. And experience &#8212; another word for that is institutional knowledge or tribal knowledge, the things that intuitively we as knowledge workers learn by just doing work.</span></p><p><span>I think for a long time when we thought about knowledge graphs, we thought about taking systems of record and then being able to model out the outcomes that often are stored within them. And I think the key realization that we had was that there&#8217;s actually the most interesting and insightful context that actually lives in between the systems of record. That lives in the work that happens between the nodes in a knowledge graph.</span></p><p><span>And so speaking in an abstract way here, the difference between a knowledge graph and a context graph is the work that happens.</span></p><p><strong><span>James:</span></strong><span> So this is &#8212; let me see if I can play this back. I like to joke that for most systems of record there&#8217;s a lot of work that gets done in email, spreadsheets, word processing documents, spiral notebooks, in between one system of record and another. And you&#8217;re saying that a context graph includes at least some of that information in a structured way.</span></p><blockquote><p><span>&#8220;These models are somehow getting smarter still, but I don&#8217;t know if people actually know the difference between Opus four eight and Opus five.&#8221;<br>&#8212; Animesh Koratana</span></p></blockquote><p><span>Let me ask you this. Sometimes I worry that the discourse has become overly focused on agents &#8212; that agents are nice and agents are important, but at the end of the day, the cruise control in your car is an agent. It has a goal &#8212; it seeks a goal to keep your car at sixty-five miles per hour or seventy-five miles per hour. But what&#8217;s really interesting is the interaction with the model.</span></p><p><span>And then I wonder &#8212; is intelligence of the model the right way to think about it? Or at the end of the day are we talking about an extraordinarily good statistical model that is very good at predicting a set of outputs based on a set of inputs?</span></p><p><span>And the question becomes, to your point about context &#8212; are we giving it the right inputs?</span></p><p><strong><span>Animesh:</span></strong><span> Exactly. And I think we&#8217;re starting to feel this in some really tactical or pithy way these days, where these models are somehow getting smarter still, but I don&#8217;t know if people actually know the difference between Opus four eight and Opus five. It still feels the same, even though the intelligence is supposedly increasing.</span></p><p><span>And I think that&#8217;s probably just an indication of the property that you just described, where context actually is an important factor in figuring out what are the right questions to ask &#8212; or in other words, what are the right inputs into these models in order to actually get some scalable, repeatable, economical, and good output.</span></p><p><strong><span>James:</span></strong><span> Well, if you have a new joiner &#8212; a new engineer or a new business analyst on your team &#8212; you just have to say, all right, let me explain the business we&#8217;re in, let me explain the problem we&#8217;re trying to solve. Is it like that?</span></p><p><strong><span>Animesh:</span></strong><span> Yeah, I think the way we think about this is the lineage of work. Maybe a better way to actually frame this would be thinking about what is </span><a href="https://www.prosaictimes.com/p/legacy-code-is-a-map-of-your-business"><span>a system of record</span></a><span>. Historically, what has it actually been? A system of record stores the output of work &#8212; if I&#8217;ve had to really distill it down: transactions</span></p><p><strong><span>James:</span></strong><span> Right. Transactions happened.</span></p><p><strong><span>Animesh:</span></strong><span> happened, exactly, and the output. And the most prototypical example of this might be Salesforce.</span></p><p><span>So Salesforce stores the output of sometimes months of work between different sales reps, between SEs, the support person, support tickets &#8212; all these different things. And once all that is said and done, what we store in Salesforce is: this customer is paying us this much over this contract period, and here&#8217;s the different people. And often the most important context ends up being the work that happened before we got there.</span></p><p><span>Which is &#8212; why did we negotiate that particular price? Or why is this particular person dedicated to this particular account? These are the things that actually are operationally useful for decision making in the future when we&#8217;re talking about the renewal of the account, or expansions, or whatever it might be. And so as we&#8217;ve started trying to model &#8212; or, I think a different view, democratize &#8212; work: making it accessible not only to the new intern who joins, but also to the thousands of agents. And I agree that I think we&#8217;re overly rotated on agents, but I think that&#8217;s the thing that&#8217;s changed. There&#8217;s now this capacity for thousands of different agents to actually go and do work on your behalf. The natural question that has kind of arisen is: how do we get these agents to have the same judgment, and the same kind of insight about the why behind the decision making of the organization, as opposed to just the what &#8212; because the what is, I can go and integrate into Salesforce and all those kinds of things. And so I think that actually is the thing that mirrors this transition in the public vernacular from knowledge graphs to context graphs &#8212; there&#8217;s a slightly different nuance to what we&#8217;re really trying to model here. And what we&#8217;re really trying to model is the work. We&#8217;re trying to model the decision making in the organization, because I think that&#8217;s what we found is the most leveraged piece.</span></p><p><strong><span>James:</span></strong><span> So let&#8217;s play with that a little bit.</span></p><p><span>And the degree of ambiguity varies greatly by business domain.</span></p><p><span>A-to-C markets often don&#8217;t have a lot of ambiguity, because if you&#8217;re dealing with millions of customers, you can&#8217;t afford ambiguity. If you&#8217;re running a credit card business &#8212; if you have this type of credit score, you get X percent interest rate, and you have that type of credit score, you get Y percent interest rate &#8212; there&#8217;s not a lot of one-off judgment involved. On the other hand, if you&#8217;re negotiating &#8212; large software contracts, hedge fund services, what have you &#8212; it&#8217;s all judgment.</span></p><p><strong><span>Animesh:</span></strong><span> Yeah, it&#8217;s all ambiguity.</span></p><p><strong><span>James:</span></strong><span> A fifty-million-dollar enterprise deal of some set ultimately goes to somebody senior &#8212; or a group of senior people &#8212; and it&#8217;s: yeah, we&#8217;ll go to this price and not that price. And all that information &#8212; not only is it not written down somewhere, but someone probably couldn&#8217;t even tell you what the decision rules he or she used were. How do you extract that? How do you get at that?</span></p><p><strong><span>Animesh:</span></strong><span> There&#8217;s this whole topic these days around continual learning and improvement. Continual learning, in the most widely accepted case, is usually figuring out how to take feedback from actions that a model has taken, and figure out how to imbue that back into the weights of the model, so that it creates a better output next time that is more consistent with the rule set or the operating procedure of that business. I think what we&#8217;ve seen, especially as we now think about the ecosystem around the model &#8212; the harness and the memory and the context and the inputs and all of these other pieces &#8212; the way I think about this is: a lot of the intelligence and the context that makes a model mine &#8212; or my organization&#8217;s &#8212; ends up coming from thinking about how do we tune the ecosystem around the model, or the set of models that we have available, in order to better mirror the patterns and ways of working that we observe in an organization.</span></p><p><span>And so instead of actually thinking about an individual model and training loops within the weights of the model itself, I think we actually need to think about the agent system as a machine that produces work, and think about how we optimize that entire stack in order to actually be able to hill-climb towards some optima that mimics a particular organization&#8217;s rule set and stuff like that. Is that kind of getting at what you&#8217;re talking about?</span></p><p><strong><span>James:</span></strong><span> Are you familiar with type 1 versus type 2 processing [2]?</span></p><p><strong><span>Animesh:</span></strong><span> No, tell me more.</span></p><p><strong><span>James:</span></strong><span> I hope I&#8217;m not reversing them here. Type 1 is instinctive. Someone asks you, do we go with a long deck or a short deck for this meeting &#8212; you don&#8217;t actually think about it, you just subconsciously process fifty different things and say, it&#8217;s a short deck.</span></p><p><span>Or someone asks you, how long is it gonna take to implement that feature, and just instinctively you say, this is one sprint. It&#8217;s all based on experience. And then type two processing is when you really sit down and decompose it &#8212; and we&#8217;re pretty good, I think, at least in some cases, at getting computers to do type two processing, because there&#8217;s logic then we can articulate.</span></p><p><span>But a lot of what you&#8217;re describing &#8212; the work between the work, the work between the systems of record &#8212; I&#8217;d suggest to you is type one processing. It&#8217;s people debating their instincts, in some respects. And I&#8217;m trying to figure out &#8212; one of the things I&#8217;ve been thinking about a lot is: how do we try and turn type one into type two, or articulate type one processing, so we understand our subconscious processes. So I was trying to think through how you think about that.</span></p><p><span>And let me stop talking and see what your take is.</span></p><p><strong><span>Animesh:</span></strong><span> That&#8217;s probably the trillion-dollar question, at the end of the day. How to model type one work in type two is the bedrock of, I think, all of enterprise transformation. It is the bedrock of all automation in the enterprise. It&#8217;s a huge, huge problem, and I think it addresses all of what we see as white collar labor in the world.</span></p><p><span>I don&#8217;t think there&#8217;s actually a silver bullet for this answer, because at the end of the day, it&#8217;s a pure judgment game, and there&#8217;s compounding errors in every single direction that you look, where judgment &#8212;</span></p><blockquote><p><span>&#8220;Agents are essentially your brain in a jar.&#8221;<br>&#8212; Animesh Koratana</span></p></blockquote><p><strong><span>James:</span></strong><span> If only there were a silver bullet.</span></p><p><strong><span>Animesh:</span></strong><span> No &#8212; but let&#8217;s take a look at what are the tools that we have available in order to think about this problem differently today than we had a year or two ago. At the risk of sounding like I&#8217;m beating a dead horse, I think the single most useful tool that we have today that we didn&#8217;t two years ago is agents.</span></p><p><span>What do agents do? Agents are essentially your brain in a jar &#8212; and if we give them the right set of tools, they can interact with different systems of record, they can reason and take action in the world and see what the consequences of their actions are in order to actually orient and take the next best action.</span></p><p><span>So they&#8217;re embodied in the organization by just being able to interact with different systems of record.</span></p><h4><span>Building a context graph for software engineering</span></h4><div><hr></div><p><strong><span>In this section:</span></strong></p><ul><li><p><span>Using software as the test case: what actually counts as a system of record? Jira and Salesforce, yes; a Slack thread or email chain, more like a shared spiral notebook that stores context but never a resolved decision.</span></p></li><li><p><span>A support ticket&#8217;s real path &#8212; Salesforce to Jira to a GitHub PR to Datadog &#8212; covers four or five systems of record for one unit of work.</span></p></li><li><p><span>The pitch: instead of asking the one person who understands a given database every time, an agent with the context graph can infer what he&#8217;d likely say and act on it directly.</span></p></li></ul><div><hr></div><p><strong><span>James:</span></strong><span> Well, let&#8217;s take software development as an example.</span></p><p><span>Because software is maybe the easiest use case in the fuzzy world, for a couple of reasons.</span></p><p><span>It&#8217;s a much more instrumented process than some other creative processes. We have tickets, we have requests, we have PRs, we have GitHub. We have requirements, we have use cases. And software engineers tend to be a little more explicit than other people, and we&#8217;ll have a thousand-message Slack argument over an architectural issue.</span></p><p><strong><span>Animesh:</span></strong><span> Yeah, sure.</span></p><p><strong><span>James:</span></strong><span> So explain to me a little bit &#8212; okay, we&#8217;ve got email threads, we&#8217;ve got Slack threads, we have Jira tickets, we have architecture documents, we have use cases and what have you. How does that get turned into a context graph, and what do you use it for?</span></p><p><strong><span>Animesh:</span></strong><span> That&#8217;s a good question. To bring these two topics together: in the software development lifecycle, there&#8217;s a bunch of different systems of record that developers and people adjacent to the SDLC actually use. We have requirements, we have tickets,</span></p><p><strong><span>James:</span></strong><span> We have requirements. We have tickets.</span></p><p><strong><span>Animesh:</span></strong><span> we have Slack channels, we also have Datadog, and we have &#8212;</span></p><p><strong><span>James:</span></strong><span> Well, Slack channel&#8217;s not a system of record, I would suggest.</span></p><p><strong><span>Animesh:</span></strong><span> I don&#8217;t know &#8212; I think there&#8217;s decisions and outcomes that are actually kind of recorded there, usually in some sort of a &#8212;</span></p><p><strong><span>James:</span></strong><span> Yeah, but it&#8217;s recorded. Let me challenge that a bit. I agree Jira is a system of record for software engineering. There is a ticket, the ticket was dispositioned, what have you. A messaging app or email &#8212; that&#8217;s a shared spiral notebook.</span></p><p><span>People debate stuff. No one ever says &#8212; people may say informally, we&#8217;ve agreed on this, but at no point is there a piece of structured data that says this issue has been resolved.</span></p><p><strong><span>Animesh:</span></strong><span> Yeah. So maybe it blends the line a little bit, because it&#8217;s not storing an outcome, or some sort of central record about the organization.</span></p><p><strong><span>James:</span></strong><span> I would argue it&#8217;s storing context.</span></p><p><strong><span>Animesh:</span></strong><span> It is storing context. It&#8217;s often storing where the work is actually happening and the path to actually getting there. But to pull this up a level &#8212; when we think about how do we build a context graph for software development &#8212; what we think about are all of the different trajectories and lineages of work that happen in order to truly solve one problem. And one specific problem that&#8217;s particularly interesting is around support, or SRE. On one extreme, we get a ticket. That ticket might be created in Salesforce, and then we have an L1 support engineer taking a look at that ticket and saying, okay, well, this isn&#8217;t a user problem &#8212; this might actually be an engineering problem.</span></p><p><span>And they go and escalate it to L2, and now it&#8217;s a Jira ticket &#8212; and that Salesforce ticket turned into a Jira ticket somewhere with a little more context and a little more work done. And that L2 ticket is then triaged and reproduced, and then it goes to an engineer. And that Jira ticket is now moved stages. And that engineer goes and takes that Jira ticket, maybe takes some set of code changes that actually might fix that particular problem. And now it ends up as a PR that&#8217;s in GitHub, which is now a third system of record.</span></p><p><span>And ultimately that code change is deployed, and now the changes are actually being observed in Datadog, or some sort of telemetry or observability system. So, very simply, there&#8217;s four or five different systems of record that we traverse through for one unit of work.</span></p><blockquote><p><span>&#8220;Instead of having to go and try a whole bunch of different things, and instead of having to go and ask the same people the same dumb question again, I&#8217;m now able to go learn from the past.&#8221;<br>&#8212; Animesh Koratana</span></p></blockquote><p><strong><span>James:</span></strong><span> We&#8217;ve gone from user makes a complaint all the way to code is working in production.</span></p><p><strong><span>Animesh:</span></strong><span> Exactly. And it traversed three or four different functions, and in the process three or four different systems of record, all in order to get to one particular outcome that was useful to the business. And</span></p><p><strong><span>James:</span></strong><span> And I would argue between each system of record you often have multiple emails, multiple Slack messages, multiple meetings, whatever, as people align on decisions in order to solution the next phase in the chain.</span></p><p><strong><span>Animesh:</span></strong><span> Exactly. And that&#8217;s historically how we&#8217;ve worked &#8212; we get people together on war rooms, and there&#8217;s Zoom chats, and then there&#8217;s Slack and email, and all of these decisions that are made to essentially progress &#8212; move the puck forward. And I think the single most useful tool that we have available that we didn&#8217;t two years ago is now agents, where agents can actually be the things instead of humans to actually own the decision authority and the progression of that arc between these different systems of record. Now, for a second, let&#8217;s suspend</span></p><p><strong><span>James:</span></strong><span> So &#8212;</span></p><p><strong><span>Animesh:</span></strong><span> the belief as to whether they make the right decision or not.</span></p><p><strong><span>James:</span></strong><span> Okay, let&#8217;s put that aside. But what is the decision that the agent makes? Does it design the solution? Does it review the solution and say it&#8217;s ready to go into production? What is, in that chain &#8212; if you have a context graph, what does the agent do that it would not have been able to do otherwise?</span></p><p><strong><span>Animesh:</span></strong><span> So this context graph is actually a record of all of the decisions in the past that got us from one record to another. And with a context graph, this agent is able to make &#8212;</span></p><p><strong><span>James:</span></strong><span> Right. Let me just illustrate that for a second. We required two sprints here and one sprint there. We required synchronous communication for this thing, and we&#8217;re able to go with asynchronous for this other thing. We used a relational database for this problem and a graph database for that problem. That&#8217;s it, okay.</span></p><p><strong><span>Animesh:</span></strong><span> Exactly. Those kinds of decisions. And in the support analogy that we were just taking, the equivalent would be: whenever we get this type of problem, we go talk to James, and James tends to be the one who understands everything about this particular table schema. So whenever there&#8217;s problems with login authentication &#8212; James is the one who built this particular database, and he tends to understand the indexes, the performance of it really well. And so the next time I get a ticket like that, I am able to essentially short-circuit my thinking. Instead of having to go and try a whole bunch of different things, and instead of having to go and ask the same people the same dumb question again, I&#8217;m now able to go learn from the past &#8212; able to learn from this implicit decision making that we just observe over how we handle tickets that look like this, in order to go to you directly, or infer what you might have said about this particular category of problem, so that I could go and look in the right places to push further.</span></p><p><strong><span>James:</span></strong><span> Okay, let me play with this a little bit. Let&#8217;s take </span><a href="https://www.prosaictimes.com/p/everything-is-a-graph"><span>graph database versus vector search</span></a><span>, which is sometimes &#8212; I can imagine twenty different projects or events where various people have had debates over whether we should use vector search, or cipher, or something like that for this particular problem, or any other architectural decision. And I could imagine interrogating the email, or video transcripts, or whatever other set of communications, and decompose those into a set of claims that support or don&#8217;t support other claims.</span></p><p><span>And from that I wonder if I might be able to derive signal. Is that some of what you mean by a context graph? Because I would argue that&#8217;s some of the most important context in our decision making. Animesh argued this, James argued that, somebody else argued the other thing, and ultimately we went with Animesh&#8217;s solution for these three reasons &#8212; but if something else were true, we might have gone with a different solution.</span></p><p><strong><span>Animesh:</span></strong><span> Yeah, absolutely. And the way to teach agents to do work and decision making in the same way that we would, they essentially have to be in the room &#8212; and when I mean in the room, I mean they need to be a part of that Slack conversation, or they need to be a part of the decision making. And what&#8217;s really interesting is this becomes a bit of a UX problem &#8212; just how do you actually create</span></p><p><strong><span>James:</span></strong><span> A what problem? A UX problem?</span></p><p><strong><span>Animesh:</span></strong><span> Yeah, a UX problem &#8212; which is essentially, how do we create the room where the agent can actually participate alongside all of the other humans that are necessary to make a particular decision, so that we can actually capture the right &#8212; what we call &#8212; </span><a href="https://www.prosaictimes.com/p/are-context-graphs-the-new-systems"><span>decision trace</span></a><span>, for how we got from one particular input to one particular decision or action on the other end. And what this context graph becomes is basically a web of a bunch of different decision traces that were observed as the agent participated in the rooms where the work was actually being done. And what we see is over time these agents</span></p><p><strong><span>James:</span></strong><span> And yes.</span></p><p><strong><span>Animesh:</span></strong><span> can actually start inheriting more and more of that.</span></p><p><strong><span>James:</span></strong><span> And is it fair to say a decision trace might be a claim or a fact? You have a hypothesis which supports another, which supports another hypothesis, which is grounded in a fact &#8212; or not grounded in a fact.</span></p><p><strong><span>Animesh:</span></strong><span> Yeah, it&#8217;s actually a chain of hypotheses &#8212; a chain of a bunch of these different things.</span></p><p><strong><span>James:</span></strong><span> Yeah, well, that&#8217;s okay. And then hopefully someplace you hit a fact. One hopes.</span></p><p><strong><span>Animesh:</span></strong><span> Yeah, exactly. A fact is in another record &#8212; the facts are essentially ultimately stored in some system of record.</span></p><p><strong><span>James:</span></strong><span> Yeah, yeah, yeah. A fact is a proven hypothesis, right &#8212; or a proven claim, within certain limitations, or within a certain scope. So creating the structure is a challenge. Surfacing the structure, or deriving insight from the structure, is a challenge.</span></p><p><span>The other thing is populating the structure is a challenge. I&#8217;m curious about this a little bit. As you&#8217;d expect, I get into &#8212; not arguments, but debates &#8212; with people all the time. And sometimes they&#8217;ll say things like, yeah, that&#8217;ll totally work. How good do you think the models are at interpreting the ironic, imperfect, sometimes highly colloquial language that people use as they debate things.</span></p><p><strong><span>Animesh:</span></strong><span> That&#8217;s a good question.</span></p><p><span>I think there&#8217;s a simple answer and a more complicated answer. The simple answer is I think LLMs have proven to be pretty good at reading between the lines and operating in ambiguity.</span></p><p><strong><span>James:</span></strong><span> Perhaps better than humans are, because half the time people &#8212; sometimes I&#8217;ll use sarcasm and people will totally not get it.</span></p><p><strong><span>Animesh:</span></strong><span> No, for sure. And I think the other part of this is &#8212; maybe the bigger question you might be getting at is this framework that I think you and I talked about one or two conversations ago, which is: is the context graph, in contrast to a knowledge graph or a system of record, a kind of high-entropy, high-dimensional sort of thing, or is it &#8212; is the job of a context graph to essentially reduce entropy down to something that is very specific and understandable &#8212; a fact? Where, in the spectrum, does a context graph actually live?</span></p><p><span>I think that&#8217;s actually maybe the bigger question you&#8217;re getting at within this, which is: there&#8217;s a lot of nuance, obviously, in what a decision trace actually represents, and how does it actually get represented &#8212; is it a series of facts? Is it a high-dimensional thing? Or is it ultimately a system of record &#8212; a very structured, ontology-esque store? My answer for this, and I think this is an open debate, is that right now it&#8217;s highly dependent on the category of work. And more importantly, I think the consequences of bad outcomes in that work. A good example of this, again, is software &#8212; where the consequences of bad work is I have to roll back, or fix a bug, and I have a lot of support volume &#8212; in a large majority of software. Now, there&#8217;s a different set of software organizations where they&#8217;re handling payments, or they&#8217;re handling EHR records, and there the consequences of bad software are way worse &#8212; regulatory problems.</span></p><p><strong><span>James:</span></strong><span> And then think about embedded software in, say, the control panel for a nuclear reactor or a submarine or something like that.</span></p><p><strong><span>Animesh:</span></strong><span> Yeah, exactly. And there&#8217;s grades of this. And I think if you look at the way organizations work in each of these different consequences, their process and their speed are largely vastly different. A nuclear reactor&#8217;s software is probably not being deployed eight times a day, but a consumer app that&#8217;s helping you order your food might be deployed fifty times a day. So there&#8217;s two kinds of extremes here, and the processes and the way people work have actually been adapted for it. And so, to a large degree, I think the way these context graphs need to evolve is actually very domain-specific. And I think the commercial opportunity here is: how do we take intelligence and pair it with context and a representation of the world that is specific to each one of the organizations that this intelligence is actually being deployed into. And I think that&#8217;s actually where the problem of how to make agents productive in the enterprise is going to be solved.</span></p><p><strong><span>James:</span></strong><span> Let me not entirely, but partially, challenge that. Maybe not &#8212; I&#8217;m not sure.</span></p><p><strong><span>Animesh:</span></strong><span> Please.</span></p><h4><span>The epistemology underneath the graph</span></h4><div><hr></div><p><strong><span>In this section:</span></strong></p><ul><li><p><span>Does a context graph rest on some underlying logic &#8212; classical, inductive, Bayesian &#8212; or is that the wrong question entirely?</span></p></li><li><p><span>A context graph as world model raises a further question: does it compile down to fixed primitives, or live as something more continuous, like an embedding space?</span></p></li><li><p><span>Landing point: gut-driven judgment is itself a world model humans can&#8217;t fully articulate &#8212; the same way a language model&#8217;s internal representations encode patterns nobody explicitly designed in.</span></p></li></ul><div><hr></div><p><strong><span>James:</span></strong><span> Is it possible that a context graph rests on an </span><a href="https://www.prosaictimes.com/p/what-kalashnikov-and-heisenberg-understood"><span>epistemological substrate</span></a><span>? We could have classical logic &#8212; statement, implication &#8212; but there&#8217;s other epistemological substrates.</span></p><p><span>We could rest it on inductive logic. We could rest it on Bayesian logic &#8212; if you go to anyone who runs money at a hedge fund, everything is Bayesian logic. Are there &#8212; I understand there&#8217;s different domain-specific things, but is there some sort of epistemological substrate, or set of assumptions, that would sit at the bottom of a context graph &#8212; some view about what reality is and how you think about reality.</span></p><p><span>I&#8217;ve broken the podcast here.</span></p><p><strong><span>Animesh:</span></strong><span> I gotta think about this &#8212; let me think out loud here for a second.</span></p><p><span>A context graph, in its truest form, is a world model. It is a model of &#8212;</span></p><p><strong><span>James:</span></strong><span> I would argue any system is a model. A general ledger is a model of a set of financial transactions. A CRM is a model of a set of customer relationships. Any system is an imperfect model of the world. And so a context graph is a more nuanced model of the world than, for example, a traditional customer relationship management system.</span></p><p><strong><span>Animesh:</span></strong><span> Yeah, so the question here is: is that world model compiled down to specific primitives, or specific types of relationships that we think are general enough to represent all of this particular domain.</span></p><p><strong><span>James:</span></strong><span> And what are the primitives? With a large language model, you could argue the primitive is language.</span></p><p><span>I don&#8217;t know if there&#8217;s some primitive someplace in the stack that&#8217;s logic. And for a physics model, you&#8217;d argue the primitive is ultimately, I suppose, a set of physical laws.</span></p><p><strong><span>Animesh:</span></strong><span> Physics. Yeah.</span></p><p><span>So, just so I understand this framework fully &#8212; how do you think about embedding spaces? Is there</span></p><p><strong><span>James:</span></strong><span> What?</span></p><p><strong><span>Animesh:</span></strong><span> an embedding space &#8212; or some sort of vector space?</span></p><p><strong><span>James:</span></strong><span> Here&#8217;s how I think about embedding. It is just a way of managing entropy &#8212; which is to say, Python is a formal language. It can mean only one thing. I&#8217;m sure that&#8217;s not a hundred percent true, but I bet it&#8217;s ninety-nine and a half percent true.</span></p><p><span>English is the opposite &#8212; it can mean just about anything, but it can mean many things. Any given sentence could mean several things, and you could say any given thing multiple ways. Let&#8217;s say Esperanto is somewhere in the middle.</span></p><p><span>And embedding, to me, is a way of capturing the fact that natural language is indeterminate. It allows us to say a desk is proximate to a table, is proximate to a work surface, even though the letters are very different from one another. It&#8217;s allowing us to say that &#8212;</span></p><p><strong><span>Animesh:</span></strong><span> It allows us to compare discrete things in a continuous space.</span></p><p><strong><span>James:</span></strong><span> Yes &#8212; that, it&#8217;s, in effect, applying numerical values to semantics.</span></p><p><strong><span>Animesh:</span></strong><span> But to your question &#8212; is an embedding space underpinned by some set of laws or primitives that govern the entire embedding space? Or is it just an embedding space?</span></p><p><strong><span>James:</span></strong><span> I don&#8217;t know. What do you think?</span></p><blockquote><p><span>&#8220;These models have somehow internally derived certain laws of the universe, or laws of language and cognition, that we haven&#8217;t fully been able to rederive, but these models are fully exercising.&#8221;<br>&#8212; Animesh Koratana</span></p></blockquote><p><span>That&#8217;s an interesting question &#8212; you could argue, is there some &#8212; I mean, we&#8217;re truly probably getting far afield from software development processes, but is there some conceptual model that underpins language? One of my personal hypotheses is: my god, we&#8217;re gonna learn a lot more about linguistics over the next decade as a result of large language models than anyone ever thought about.</span></p><p><strong><span>Animesh:</span></strong><span> Yeah, so I think yes &#8212; there is some physics that governs it, and I&#8217;m using the physics word as a broader term here, but</span></p><p><strong><span>James:</span></strong><span> Yeah. Maybe neurology, or neuroscience, is a better term than physics.</span></p><p><strong><span>Animesh:</span></strong><span> There&#8217;s something that I think governs embedding spaces, and more broadly the representation spaces in these models. I think it is</span></p><p><strong><span>James:</span></strong><span> Mm-hmm. So you could argue how much of it is culture versus how much of it is neuroscience, because different languages have different numbers of words for any given concept. There&#8217;s some languages that have a zillion words for one thing and few words for another thing, and a language that evolved in a different culture, in a different place, might have the reverse be true. Please continue.</span></p><p><strong><span>Animesh:</span></strong><span> No, exactly. And so the answer is, I think, that there is a worldview &#8212; it is just far more nuanced than our minds can comprehend, or than our minds really can or need to model. And this is actually where the whole field of interpretability research, I think, really comes from &#8212; these models have somehow internally derived certain laws of the universe, or laws of language and cognition, that we haven&#8217;t fully been able to rederive, but these models are fully exercising.</span></p><p><span>And I think there&#8217;s an equivalent for that in the way that we work &#8212; it&#8217;s highly nuanced, it&#8217;s why great salespeople are paid so much &#8212; because they have this highly nuanced view of the world, and view of their customer, and view of the problem and the market, and they&#8217;re able to navigate all these things in a problem-dependent, time-sensitive sort of way.</span></p><p><strong><span>James:</span></strong><span> And let me push on that a little bit, or add to that point: they&#8217;re doing an optimization problem in their head with a zillion variables, all of which are continuous, all of which are interconnected, and many of which are latent. And if you ask them how they do it, they&#8217;d look at you blankly.</span></p><p><strong><span>Animesh:</span></strong><span> Exactly. It&#8217;s a model that lives in their head somewhere.</span></p><p><strong><span>James:</span></strong><span> Right? We made X, not Y. We have this meeting, not that meeting. Why do we have it? Because we do.</span></p><p><strong><span>Animesh:</span></strong><span> Yep, exactly. It&#8217;s often led by gut. And I think the ones that are even better are the ones who can explain a little bit of it, but regardless, there&#8217;s a lot of &#8212;</span></p><p><strong><span>James:</span></strong><span> Even great software engineers are like that too. When I used to code thirty years ago, I&#8217;d sometimes head in a direction &#8212; I have no idea. Not that I was a great software engineer, I was a mediocre one. But why do you head in this direction? I&#8217;m not sure, but I&#8217;m pretty sure I&#8217;m right.</span></p><p><span>I think many architects start to investigate a direction not entirely knowing why they&#8217;re investigating it.</span></p><p><strong><span>Animesh:</span></strong><span> Yeah, a hundred percent. And so, bringing it to the context piece here &#8212; at the end of the day, there is some world model that&#8217;s underpinning people&#8217;s intuition, or gut. And I think the world of context is actually a way of trying to create some sort of learning machine, or learning layer, that essentially connects to a model and gives it this sort of experience or intuition about how to operate and do work in the organization &#8212; to give it that same level of intuition that a human might accrue over doing that work over a long period of time.</span></p><p><strong><span>James:</span></strong><span> I wonder if there&#8217;s two models. There&#8217;s a human model, which a large language model is an incredibly simplistic exposition of, and then there&#8217;s a physics world model. And I suppose there&#8217;s certain people who would say that ultimately neuroscience is physics, so therefore your human world model should derive from your physics world model. I&#8217;m not smart enough to fully understand that, but there is some part of me that thinks that&#8217;s at least a distinction between things that are cultural, psychological, and intellectual versus things that are mechanical and physical. Does that make sense at all?</span></p><p><strong><span>Animesh:</span></strong><span> I think so, yeah.</span></p><h4><span>From judgment to a rising waterline</span></h4><div><hr></div><p><strong><span>In this section:</span></strong></p><ul><li><p><span>Coding agents have already pushed the UX from line-by-line autocomplete to &#8220;express your intent&#8221; &#8212; the next shift is expressing the business outcome, not just the code.</span></p></li><li><p><span>Any decision can be called judgment, but a context graph raises the &#8220;waterline&#8221; &#8212; pulling enough signal from how a team handled similar cases before to turn instinct into a heuristic an agent can use.</span></p></li><li><p><span>Landing analogy: an agent with the context graph is like the intern on a trading desk who&#8217;s watched the trader long enough to know why she zigs one way and not another.</span></p></li></ul><div><hr></div><p><strong><span>James:</span></strong><span> Alright, so take this back to software engineering. What does this mean? How do we use any of this to write better software?</span></p><p><strong><span>Animesh:</span></strong><span> So I think the software paradigm, and the software work, is a very interesting moment. A lot of folks are in this moment where they&#8217;re six, eight, twelve months into starting to use coding agents.</span></p><p><span>And the amount of code that we&#8217;re able to write has clearly increased by one, maybe two orders of magnitude.</span></p><blockquote><p><span>&#8220;How do I know any of that is good? We&#8217;re producing a whole lot of new software.&#8221;<br>&#8212; Animesh Koratana</span></p></blockquote><p><strong><span>James:</span></strong><span> Though I will say I hope for a coding large language model which is trained on the tiny fraction of code that&#8217;s any good, as opposed to &#8212;</span></p><p><strong><span>Animesh:</span></strong><span> Yeah. I think you&#8217;re actually getting at the bigger problem, which is: how do I know any of that is good? We&#8217;re producing a whole lot of new software.</span></p><p><strong><span>James:</span></strong><span> Yeah &#8212; and that gets &#8212; well, to me that&#8217;s a bit more mechanical than contextual, which is: okay, we know that hard-coding things is bad, and we can hopefully create hooks around that. That&#8217;s a very different issue from &#8212; okay, when do we design a user workflow that&#8217;s sequential versus parallel? Because sometimes it does have to be sequential, and sometimes you can make it parallel. That&#8217;s not &#8220;don&#8217;t hard-code things&#8221; &#8212; that is entirely context-dependent.</span></p><p><strong><span>Animesh:</span></strong><span> No, exactly. And so I think the opportunity ahead with context layers broadly is basically leveling up the conversation that we have with agents. Instead of being, hey, can you go and write this line of code &#8212; task delegation &#8212; you can actually start thinking about what the business outcome is that we actually want to drive towards, and what we want to optimize our stack of agents towards being able to produce. And good here is measured by the outcome, as opposed to lines produced, in the unit economics, and all these other dimensions that we&#8217;re starting to understand matter a lot more.</span></p><p><strong><span>James:</span></strong><span> What is the line between what the agent does and what the human does? Human creates the spec, human defines the outcome. What does the human do, and</span></p><p><strong><span>Animesh:</span></strong><span> What?</span></p><p><strong><span>James:</span></strong><span> what does the agent do &#8212; to your thinking? Think two years in the future, not today.</span></p><p><strong><span>Animesh:</span></strong><span> I think where the world is headed right now is that the human needs to be brought in for any moments of judgment, and everything else needs to essentially be compiled away. If we think about what&#8217;s happened with coding agents already &#8212; coding agents aren&#8217;t asking us for every fifth or tenth line that they&#8217;re writing. The UX shifted from autocomplete to &#8220;express your intent, and then I&#8217;ll go and execute a couple of turns,&#8221; and then execute on that intent on your behalf. And I think now we need to level that up one more time &#8212; which is: what is the business outcome that we&#8217;re ultimately trying to express? What is the operating procedure? What is our way of working? And being able to express that, and then essentially having agents be able to repeatedly do that in a way that actually creates the operational efficiency that we were looking for in the enterprise.</span></p><p><strong><span>James:</span></strong><span> Let me see if I can pull a couple of things together. Tell me if you agree with this.</span></p><p><span>We can frame anything as judgment &#8212; or many, many things as judgment. I write a line of code this way or that way. Judgment.</span></p><p><span>What type of loop do I use? What type of loop construct do I use?</span></p><p><strong><span>Animesh:</span></strong><span> Yeah. It&#8217;s like the threshold for what its leverage on the rest of the organization is &#8212; I think that threshold is increasing.</span></p><p><strong><span>James:</span></strong><span> Let me push on this slightly. A context graph increases the waterline for what judgment we can engage in programmatically. There are a million decisions that might have been &#8220;do it this way&#8221; based on instinct &#8212; but if we can pull more signal out of history &#8212; the reason we did it in these twenty circumstances one way and those twenty circumstances another way &#8212; we&#8217;ve now derived some sort of heuristic that we can give to an agent, as opposed to going and asking Animesh what we&#8217;re doing.</span></p><p><span>And you could argue that&#8217;s not dissimilar from the intern sitting on a trading desk, watching the trader &#8212; he or she did it this way when this happened, and did it that way when that happened. Alright &#8212; closing thoughts.</span></p><p><strong><span>Animesh:</span></strong><span> Exactly. You nailed it. It increases the watermark of where judgment is.</span></p><p><strong><span>James:</span></strong><span> For people using context graphs in a technology environment, or in a software engineering environment &#8212;</span></p><p><strong><span>Animesh:</span></strong><span> Can you repeat the question? I think you broke out there for a second. What advice?</span></p><h4><span>Closing advice</span></h4><div><hr></div><p><strong><span>In this section:</span></strong></p><ul><li><p><span>The biggest insight: think about the work that happens between the creation of a task and its outcome &#8212; not just retrieval across existing systems of record.</span></p></li><li><p><span>The bet is a continuous, representation-based approach over a prescribed ontology &#8212; though domains like trading, healthcare, and finance may need the opposite, where explainability is non-negotiable.</span></p></li><li><p><span>Work rarely gets solved by one person alone; capturing decision traces means being honest that most real outcomes span multiple people, not a single line of code.</span></p></li></ul><div><hr></div><p><strong><span>James:</span></strong><span> What advice do you have as people think about getting value from context graphs?</span></p><p><strong><span>Animesh:</span></strong><span> I think the biggest insight that helped us was basically thinking about what is truly the work that happens between the creation of the work and the outcome, between all of the different systems of record.</span></p><p><strong><span>James:</span></strong><span> And how do you create the ontology around that work &#8212; I&#8217;d suggest, to your point about domain specificity?</span></p><p><strong><span>Animesh:</span></strong><span> Yeah, I would also &#8212; I think the answer ultimately comes down to: what are the mechanisms that we have for the agents to learn from the work that they&#8217;re actually doing, so that watermark over time rises. For us, the answer ultimately was actually taking a more continuous, representation-based approach, as opposed to a prescribed-ontology sort of approach.</span></p><p><strong><span>James:</span></strong><span> Interesting.</span></p><p><strong><span>Animesh:</span></strong><span> But I think there are plenty of other domains &#8212; trading, healthcare, finance &#8212; where continuous, nuanced, unexplainable representations actually aren&#8217;t good enough, and we need &#8212;</span></p><blockquote><p><span>&#8220;It&#8217;s not &#8216;write this line of code,&#8217; it&#8217;s &#8216;solve this problem for my customer.&#8217;&#8221;<br>&#8212; Animesh Koratana</span></p></blockquote><p><strong><span>James:</span></strong><span> Okay, for a follow-up discussion, we&#8217;re gonna talk about two topics. I want to hear more about continuous representations, and then I want to have a discussion around whether more of knowledge work begins to look more like software engineering.</span></p><p><strong><span>Animesh:</span></strong><span> I think yes. I think a lot of it will start collapsing in. But that is a much, much longer topic.</span></p><p><span>The advice I&#8217;d have here is: just think about the work. A lot of people think about it as a retrieval problem for agents to be able to interoperate between systems of record. You really have to think about how you model the work &#8212; and if you do that really well, you actually start capturing signal that helps you inform these decision traces that kick-start this flywheel. That&#8217;s probably the biggest insight. And second: often work doesn&#8217;t span only a single person &#8212; it spans multiple people. And so being honest with ourselves about what that work actually looks like in order to get to the outcome. It&#8217;s not &#8220;write this line of code,&#8221; it&#8217;s &#8220;solve this problem for my customer.&#8221; And that latter outcome often ends up becoming much more complex, but also has much higher opportunity, in my eyes.</span></p><p><strong><span>James:</span></strong><span> In part because people have different mental models for thinking about work. Alright &#8212; thank you very much.</span></p><p><strong><span>Animesh:</span></strong><span> Exactly. And that&#8217;s why we have different teams.</span></p><p><span>Thank you so much for having me, James. This is a lot of fun.</span></p><p><em><span>{A system of record tells you what happened. A context graph tries to preserve why it happened: the relationships, arguments, precedents and judgment that moved the organization from one state to another. That matters because in an agentic system, output becomes input recursively; every ambiguity or lost distinction can propagate downstream. The promise of a context graph is therefore not that it eliminates judgment, but that it raises the waterline for how much judgment a machine can exercise without asking a human to reconstruct the past. &#8212; Ed.}</span></em></p><h4><span>Footnotes</span></h4><p><span>[1]: OpenAI&#8217;s original Codex, released in 2021, was a version of GPT-3 fine-tuned on code &#8212; not a variant of GPT-2, per </span><a href="https://arxiv.org/abs/2107.03374"><span>OpenAI&#8217;s own paper introducing it</span></a><span>. Koratana&#8217;s spoken timeline compresses two separate model generations; the substance of the claim (Codex &#8594; early GitHub Copilot) holds regardless.</span></p><p><span>[2]: The &#8220;type 1 / type 2&#8221; terminology here tracks Keith Stanovich and Jonathan Evans&#8217;s dual-process framing more precisely than it does Daniel Kahneman&#8217;s better-known &#8220;System 1 / System 2&#8221; from </span><em><a href="https://en.wikipedia.org/wiki/Thinking,_Fast_and_Slow"><span>Thinking, Fast and Slow</span></a></em><span> (2011) &#8212; both describe the same basic split between fast, intuitive judgment and slow, deliberate reasoning.</span></p>]]></content:encoded></item><item><title><![CDATA[The Harness, the Model, and the Worm]]></title><description><![CDATA[A discussion with Liquid AI CTO Mathias Lechner]]></description><link>https://www.prosaictimes.com/p/the-harness-the-model-and-the-worm</link><guid isPermaLink="false">https://www.prosaictimes.com/p/the-harness-the-model-and-the-worm</guid><dc:creator><![CDATA[James Kaplan]]></dc:creator><pubDate>Sun, 09 Aug 2026 21:30:29 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/210464018/d448c5c5cf6f38dcf5be65c8c84a5729.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p><span>I suspect the harness matters more than the model. The same model, dropped into different systems of context, memory, and tool access, produces wildly different results &#8212; the orchestration around a model does more work than another few points of benchmark accuracy. [1] The enterprises getting value from AI have built the scaffolding &#8212; retrieval, evaluation, guardrails &#8212; to make an ordinary model trustworthy enough to put in front of a real decision. [2]</span></p><p><span>That suspicion assumes models are all roughly alike &#8212; that the interesting variation happens around them, not inside them. </span><a href="https://www.liquid.ai/"><span>Liquid AI</span></a><span>&#8217;s research program bets the other way: not on scaling, but on what a neuron and a synapse actually do.</span></p><p><span>Liquid AI is a foundation model company, building a diverse portfolio that includes small, efficient models built to run locally, on a phone or a Raspberry Pi or inside a car, especially where network latency and bandwidth make backhaul to cloud impractical. They also train models on data that isn&#8217;t language at all &#8212; </span><a href="https://www.liquid.ai/blog/liquid-foundation-models-our-first-series-of-generative-ai-models"><span>protein sequences</span></a><span>, for example.</span></p><p><span>Liquid AI&#8217;s research started with a one-millimeter-long worm called C. elegans. It runs its entire nervous system on three hundred and two neurons [3] and still manages to forage and navigate a complicated world. Lechner&#8217;s team asked what those neurons and synapses were doing differently, and built liquid time-constant networks [4] &#8212; architectures where the connection between two neurons isn&#8217;t a fixed, linear weight but something that varies over time, the way a real synapse does.</span></p><p><span>The conversation opens with what Liquid actually ships, and the real trade-off between large and small models &#8212; not the trade-off people assume. Small models are mostly invisible, Lechner says &#8212; they run quietly in the background of products you already use. Maybe that&#8217;s why I haven&#8217;t thought much about small models?</span></p><p><span>From there we get into the liquid time-constant network itself, and then into memory &#8212; why a language model still needs something like a transformer&#8217;s perfect, growing memory even when a liquid architecture does more with less everywhere else. The KV cache discussion explains why memory, not compute, is the real constraint on model architecture.</span></p><p><span>Lechner also has a read on what separates enterprise leaders who are getting value from AI from those who aren&#8217;t: the ones who succeed understand they&#8217;re investing in a moving target, not a finished product. The conversation closes on whether we can build biology up from physics, or whether some phenomena only exist at a higher level of abstraction. Maybe that matters for how we model the world?</span></p><h4><span>What Liquid AI Builds</span></h4><div><hr></div><p><strong><span>In this section:</span></strong></p><ul><li><p><span>Liquid AI is a foundation model company whose research began with C. elegans, a worm that runs its entire nervous system on 302 neurons.</span></p></li><li><p><span>Foundation models are pre-trained by a company like Liquid AI, then customized by the customer through fine-tuning or prompting; large language models are only one type.</span></p></li><li><p><span>Liquid AI builds a diverse portfolio, including large language models scaled down for edge deployment &#8212; able to run on a Raspberry Pi &#8212; and non-language models like protein-sequence generators.</span></p></li></ul><div><hr></div><p><strong><span>James Kaplan:</span></strong><span> All right. Hi, it&#8217;s James Kaplan here with another Prosaic Times podcast. It&#8217;s a gorgeous day in New York, and I&#8217;m here with Mathias Lechner, the CTO of Liquid AI. Do you wanna introduce yourself and tell us a little about your journey and how you came to Liquid AI? And then we&#8217;ll get into it.</span></p><p><strong><span>Mathias Lechner:</span></strong><span> Thanks for having me, James. My name is Mathias. I&#8217;m CTO and co-founder of Liquid AI. I come from a research background &#8212; our research was about looking into neuroscience and seeing where there are advantages if you bring some of these models into machine learning. It&#8217;s been a journey from research to now, at Liquid AI, the company.</span></p><p><strong><span>James:</span></strong><span> What does Liquid AI do?</span></p><p><strong><span>Mathias:</span></strong><span> We are a foundation model company. In machine learning, the classical approach was: you collect your dataset, you train a model from scratch on that data, and then deploy it. That&#8217;s changed a lot in the last ten years with foundation modeling, where somebody &#8212; some entity, in our case Liquid AI &#8212; pre-trains a model on a much larger set of data, crawled from the web, all types of images, text, and so on.</span></p><p><span>Then the customer fine-tunes this model for their use case, or customizes it in some way. Even prompting ChatGPT is still using a foundation model that&#8217;s not fine-tuned &#8212; it&#8217;s just prompted; there&#8217;s a conditioning layer there. So instead of training from scratch, foundation model means somebody else pre-trains it, and the customer customizes it either with fine-tuning or prompting.</span></p><p><strong><span>James:</span></strong><span> But it&#8217;s not a large language model. What type of model is it?</span></p><p><strong><span>Mathias:</span></strong><span> Exactly &#8212; the term foundation model is agnostic to any type of model. Large language models are just one type of foundation model. It could be image &#8212;</span></p><p><strong><span>James:</span></strong><span> But the type of models you build &#8212; what type of models does Liquid AI build?</span></p><p><strong><span>Mathias:</span></strong><span> We build a diverse set of models. Our most prominent ones are large language models, but at small scale, for edge deployment. We can run a large language model on a Raspberry Pi at around forty tokens per second [5] &#8212; that&#8217;s roughly what you get from some of the ChatGPT models. We can run a smaller, more efficient version on a Raspberry Pi, which enables a lot of edge use cases. We also train models not just on text &#8212; for instance, we have protein models. Think of a generative model, like an image-generation model that you prompt, but instead of an image it generates a protein sequence.</span></p><h4><span>Large vs. Small Model Trade-off</span><strong><span>s</span></strong></h4><div><hr></div><p><strong><span>In this section:</span></strong></p><ul><li><p><span>Large general-purpose models still win for productivity workflows like coding; small, specialized models win where sub-100-millisecond latency or limited bandwidth make cloud calls impractical.</span></p></li><li><p><span>Small models are mostly invisible to users &#8212; they run quietly inside voice assistants and other embedded products rather than being something people deliberately choose.</span></p></li><li><p><span>Enterprise adoption is uneven, with some companies fully AI-native and others just touching a few models; small-model use is driven as much by capability and bandwidth constraints as by token cost.</span></p></li></ul><div><hr></div><p><strong><span>James:</span></strong><span> How do you guys think about the trade-offs between large language models versus small language models? How should people think about the trade-offs between a large general-purpose model and a more specialized model?</span></p><p><strong><span>Mathias:</span></strong><span> That&#8217;s a good question. There&#8217;s always use cases for both. There are productivity workflows where you just want the best model out there &#8212; when we code, for instance, we want the latest model from Anthropic or OpenAI, irrespective of size. And then there are use cases &#8212; say, certain cloud e-commerce companies or automotive companies &#8212; that have latency requirements. End-to-end request-to-response needs to happen within about 100 milliseconds before the user experience degrades. You can&#8217;t run that with a large language model. You need a specialized small model for that.</span></p><p><strong><span>James:</span></strong><span> You want it to be small. In many cases you want it to be local, so you don&#8217;t have to deal with network latency, correct?</span></p><p><strong><span>Mathias:</span></strong><span> Exactly. We have an e-commerce company we deploy with where our portion of processing the request is tiny compared to the network latency. That&#8217;s very interesting.</span></p><p><strong><span>James:</span></strong><span> And the large-language-model-versus-small-language-model debate &#8212; some people might be surprised that we haven&#8217;t seen more small language models evolve. If I think back a year or eighteen months, there was more assumption that we&#8217;d see more specialized models, and that hasn&#8217;t, at least in my experience, been the case.</span></p><p><span>So a couple of questions: are you surprised by that? Why do you think that&#8217;s happened? And how might that change in the future?</span></p><p><strong><span>Mathias:</span></strong><span> That&#8217;s an interesting observation. Part of it is that a lot of these small or specialized models are actually running in the background, so people aren&#8217;t used to noticing them. When you have a voice assistant on your laptop  &#8212; that&#8217;s a local model, and you don&#8217;t really notice it. Same with other companies we work with &#8212; a lot of that is hidden use cases: assistants, intelligence, getting deployed on all of these devices. It&#8217;s not that you go to a website or ask a certain tool &#8212; it&#8217;s more that it&#8217;s happening in the background, in hidden use cases.</span></p><p><strong><span>James:</span></strong><span> Got it. Do you think people in the enterprise are using smaller models as thoroughly as they should? How do you see this evolving? There&#8217;s one world where most enterprises, broadly speaking, use large general-purpose models, and product companies use smaller language models for specific use cases &#8212; voice, whatever&#8217;s built into a product.</span></p><p><span>Do you think that bifurcation continues, or do you think enterprises will start using more smaller language models? How do you see things evolving?</span></p><p><strong><span>Mathias:</span></strong><span> Looking at the customers and engagements we have, we see both gaining traction &#8212; companies adopting more of the large models, but also more of the small models rolling out.</span></p><p><span>In the three years since starting the company, I&#8217;ve observed a vast difference out there on adoption. There are some companies &#8212; I&#8217;d call them older companies &#8212; that are completely AI native, that have flipped their entire workflow upside down. And there are companies you&#8217;d assume are heavily using AI but are just getting started.</span></p><p><span>They&#8217;re just touching a few models here and there, which is quite interesting &#8212; the diversity I&#8217;ve seen in terms of AI adoption.</span></p><p><strong><span>James:</span></strong><span> How does this intersect with concerns about token costs? Everybody in this category is now talking about token costs in the enterprise. Sometimes I think that&#8217;s a little early, because most places &#8212; even very large companies &#8212; are spending single digits of millions of dollars on tokens at this point. [6]</span></p><p><span>So I don&#8217;t think it&#8217;s a crisis yet, or will become one shortly, but certainly token costs have gotten people&#8217;s attention. Do you think small specialized models running locally, in conjunction with larger models running remotely, will be part of the answer for managing token costs?</span></p><p><strong><span>Mathias:</span></strong><span> Yes, I&#8217;d say so. But it&#8217;s not only about cost &#8212; it&#8217;s also about capabilities.</span></p><p><span>We have some prototype applications with our own models &#8212; imagine an agent, a voice assistant, running twenty-four-seven on your &#8212; on your computer, that then communicates with the cloud models, the large language models, to send or pull certain results, to orchestrate together. We see much more orchestration of agents, and small agents will be part of that equation &#8212; because, as you said, token cost is one factor, but also just being able to run without transmitting everything to the cloud.</span></p><p><strong><span>James:</span></strong><span> And latency, obviously, is a big issue, right? You&#8217;re saying it&#8217;s functionality as well as latency. Can you give an example? When you say functionality or capability, do you mean some combination of reducing hallucination, more precision, more relevance?</span></p><p><span>Can you give an example &#8212; in a use case, how does that play out, and technically speaking, why does that tend to be the case?</span></p><p><span>What&#8217;s the better answer you get, and why, if you&#8217;re using a specialized small language model as opposed to a general-purpose large language model? Do you get a better answer?</span></p><p><strong><span>Mathias:</span></strong><span> I&#8217;d say it&#8217;s everything &#8212; token cost, infrastructure cost. Some companies want to deploy multimodal models &#8212; audio and voice &#8212; on their devices, and the bandwidth to transmit those to the cloud is prohibitive. It&#8217;s actually less about the token cost.</span></p><p><span>The token cost is another story, but it&#8217;s also about the connection &#8212; the bandwidth of, for instance, video, which is quite expensive. So there are advantages to running locally, and the token cost is part of the combination.</span></p><p><span>That&#8217;s why this agent is running twenty-four-seven, basically, on your laptop. We see more and more of those applications coming, where you need to be local &#8212; not just because of token cost, but connectivity and other factors.</span></p><h4><span>The Liquid Time-Constant Network</span></h4><div><hr></div><p><strong><span>In this section:</span></strong></p><ul><li><p><span>Liquid AI&#8217;s research started with C. elegans, whose nervous system runs on 302 neurons and roughly 8,000 synapses yet still supports foraging and social behavior.</span></p></li><li><p><span>The key difference from artificial neural networks isn&#8217;t the neuron &#8212; it&#8217;s the synapse: biological connections vary in neurotransmitter type, latency, and saturation, rather than acting as a fixed linear weight.</span></p></li><li><p><span>Liquid time-constant networks bring that variability into machine learning, making a neuron&#8217;s time constant liquid rather than fixed, for more expressivity without more size.</span></p></li></ul><div><hr></div><p><strong><span>James:</span></strong><span> Tell us what a liquid time-constant network is, or a model built using a liquid time-constant neural network. Tell us about the innovation and the benefit of it.</span></p><p><strong><span>Mathias:</span></strong><span> Our research started, as I mentioned, from neuroscience &#8212; there&#8217;s a worm called C. elegans, about one millimeter long, with three hundred and two neurons. Every worm has almost the same nervous system, wired the same way, and yet it can forage for food and show social behavior. [7] That&#8217;s remarkable for a nervous system with only three hundred and two neurons and about eight thousand synapses, compared to artificial neural networks, which have thousands of neurons and do far simpler tasks.</span></p><p><span>When we studied how the worm&#8217;s nervous system handles these interactions, we found the neurons themselves are similar to the ones in artificial networks. What&#8217;s different is the connection between two neurons. In the worm, the synapse has different neurotransmitter types, latency, delay, and saturation &#8212; both at the neuron level and the synapse level. In an artificial neural network, a synapse is just a single connection: a linear, proportional element.</span></p><p><span>We brought that difference into machine learning as liquid time-constant networks. The idea is that the time constant &#8212; how a neuron behaves &#8212; isn&#8217;t fixed. It&#8217;s liquid. It varies over time, and the connection between two neurons isn&#8217;t statically wired. It has more complexity, more expressivity, in how two neurons communicate.</span></p><p><strong><span>James:</span></strong><span> So &#8212; I&#8217;m going to oversimplify massively here &#8212; what you&#8217;ve said is that the size and density of the neural network isn&#8217;t always correlated with the level of capability provided. That&#8217;s the point of your neurological analysis with worms, I guess. And the implication is that there&#8217;s a certain level of capability you can achieve without the processing overhead of other types of models.</span></p><p><span>Is that correct?</span></p><p><strong><span>Mathias:</span></strong><span> Yes, at least at a high level, that&#8217;s correct.</span></p><p><strong><span>James:</span></strong><span> Not bad. I was a history major.</span></p><p><strong><span>Mathias:</span></strong><span> Yes.</span></p><h4><span>Memory, Context, and the KV Cache</span></h4><div><hr></div><p><strong><span>In this section:</span></strong></p><ul><li><p><span>Liquid networks excel where context is small and time-bound, as in robotics, where only recent state matters and old, irrelevant history can be filtered out.</span></p></li><li><p><span>Language modeling is different: it still needs a transformer&#8217;s growing, perfect-memory KV cache, because some information must always be exactly retrievable rather than filtered.</span></p></li><li><p><span>Liquid AI&#8217;s own language models pair that transformer memory with a short-term, convolution-based liquid component, letting attention specialize on the longer horizon and easing KV cache pressure.</span></p></li></ul><div><hr></div><p><strong><span>James:</span></strong><span> How does this relate to memory and context window? As I&#8217;ve thought about model performance &#8212; let me back up. My long history in enterprise technology is: it&#8217;s never the compute, it&#8217;s always the memory.</span></p><p><span>That&#8217;s the bandwidth. And if you look at the history of large-model evolution &#8212; the GPU evolution &#8212; compute exceeds memory bandwidth, right?</span></p><p><strong><span>Mathias:</span></strong><span> Yes.</span></p><p><strong><span>James:</span></strong><span> And as a result, people who build these things have to use aggressively lossy compression around context windows, because you can only access so much context, and that&#8217;s where hallucination and imprecision come from. The question for you is: what&#8217;s the intersection between the type of models you build and the scale of the context window?</span></p><p><span>Can you use a bigger context window versus a smaller one? How do you think about context and what that means for model fidelity or precision? Does that make sense?</span></p><p><strong><span>Mathias:</span></strong><span> To go back a bit &#8212; we started this research on liquid time-constant networks mostly looking at a robotics problem, because in a way it&#8217;s a biological robot. There, we observed really nice behavior, because there&#8217;s a temporal component &#8212; you need to remember, you need to filter out disturbances, but you don&#8217;t need to remember what action the robot took twenty minutes ago. So the context window, in a sense, is precious but typically very small. You need something time-bound.</span></p><p><strong><span>James:</span></strong><span> What happens fifty milliseconds ago matters a lot more than what happened fifty years ago.</span></p><p><strong><span>Mathias:</span></strong><span> Exactly. That&#8217;s the robotics case, and it&#8217;s exactly where the liquid time-constant network helps a lot. In language modeling we have a different problem. There we really need the transformer architecture &#8212; multi-head attention &#8212; because certain things need to always be perfectly remembered.</span></p><p><span>Instead of a fixed memory system, the transformer&#8217;s memory grows with each additional token. That&#8217;s a massive disadvantage for scalability &#8212; it becomes quadratic in compute, linear in memory size &#8212; but it has the advantage of perfect memory: it can always go back and look exactly at what happened.</span></p><p><span>When we tried applying our liquid networks to language modeling, we found we always need some of that component &#8212; the transformer&#8217;s growing KV cache &#8212; so the model always perfectly remembers what happened in the past. That&#8217;s always necessary, at least in language, but it can be enhanced with a short-term, liquid, gated component running alongside it.</span></p><p><strong><span>James:</span></strong><span> And your KV cache has constraints, right? You can&#8217;t have an infinitely large KV cache, correct?</span></p><p><strong><span>Mathias:</span></strong><span> Exactly. That becomes prohibitive for several reasons. But at least with the short-term interactions in our own model &#8212; the LFMs, the liquid foundation models we&#8217;ve published &#8212; our language models have an additional short-term time component in the form of convolutions. That lets the attention layers specialize more on the longer horizon, which again helps a bit with KV cache compression.</span></p><p><strong><span>James:</span></strong><span> Mm-hmm. Good. What does this mean as we move from language models to world models? I&#8217;ll admit &#8212; having thought a lot about language, I sort of understand language models, or think I do. But world models are based on physics, fundamentally different, with a different set of dynamics.</span></p><p><span>How does that change the architectural trade-offs? How does it change the experience? How does it change the decisions between a large model and a small model?</span></p><p><strong><span>Mathias:</span></strong><span> That&#8217;s a good question. In terms of world modeling, what we&#8217;ve observed that really benefits is cross-modality world models. If you train only a video model, a video-generation model, it&#8217;s quite tricky &#8212; if you have the scale, it will work. But for us, the most interesting component &#8212; that&#8217;s why we&#8217;re refocusing mostly on this part &#8212; is the cross-modality aspect.</span></p><p><span>Imagine you have a text input and generate audio for it, or the other way around &#8212; a video input, and how does the world then look in text space. This cross-modality, bridging the gap between modalities, is for us much more interesting than a world model that just predicts the next frame from previous frames. That&#8217;s where I think most of our own research is going.</span></p><h4><strong><span>Advice for Enterprise Technology Leaders</span></strong></h4><div><hr></div><p><strong><span>In this section:</span></strong></p><ul><li><p><span>The enterprise leaders getting the most value understand model capability is a moving target, not a finished product &#8212; treating today&#8217;s model as the end state is the mistake that leaves companies behind.</span></p></li><li><p><span>Lechner expects multimodality &#8212; audio, video, and image in and out &#8212; to become inherent to models rather than a special-case feature, paired with new NPU-equipped hardware from Qualcomm, Intel, and AMD.</span></p></li><li><p><span>Liquid AI&#8217;s own research is shifting toward cross-modality &#8212; translating between text, audio, and video &#8212; over single-modality world models that just predict the next video frame.</span></p></li></ul><div><hr></div><p><strong><span>James:</span></strong><span> Imagine you&#8217;re the CIO or CTO of an enterprise &#8212; not a technology company, but a bank, a pharma company, an insurance company, a consumer packaged goods company, a manufacturing company. What do you think people need to know more of, in terms of model choice? What do you think people get or understand, and what do you think they don&#8217;t?</span></p><p><strong><span>Mathias:</span></strong><span> What very few people understand &#8212; but the ones who do, I have deep respect for &#8212; is that we don&#8217;t live in a static world. Model capabilities aren&#8217;t static. When we approach some of our customers or partners, some of them think of it in a static world.</span></p><p><span>This is the final product, the final model, nothing comes afterwards &#8212; this is it, the end of the game. And then there are others who really see, hey, this is just the current point in the evolution. It keeps going further &#8212;</span></p><p><span>with better data, better training algorithms, better hardware that&#8217;s available and feeds more data through the process &#8212; all working together, algorithmically, hardware, modeling, data, to improve the model. It&#8217;s interesting to talk with people who think about it very statically, versus enterprise leaders who really understand that the model is going up, and there&#8217;s enough evidence this will continue for at least the next couple of years.</span></p><p><strong><span>James:</span></strong><span> What, how will the landscape be different two years from now? What predictions would you make about the mix of models people will use, and how they&#8217;ll use them?</span></p><p><strong><span>Mathias:</span></strong><span> I can only speak with confidence about our own model-development roadmap. Even if you freeze compute and everything else, capabilities will keep increasing &#8212; better data, better algorithms, more research into different ways to model these components. One thing happening on the small-local-versus-large-model side is multimodality becoming an inherent part of it &#8212; audio, video input, the way we think of text right now &#8212; that&#8217;s just standard, it&#8217;s always supported. Same with output.</span></p><p><span>If your model speaks back to you, writes back to you, or sends back an image, that will be indiscriminate &#8212; there won&#8217;t be a difference in it being a special case triggering a special function; it will just be inherent within the model. And if you combine that with advancements in hardware &#8212; the new chip manufacturers, Qualcomm, Intel, AMD and so on, all shipping new chips with NPUs, neural processing units, packing a lot of flops at very low precision &#8212; and building models to leverage that, the combination of better hardware and better models will definitely lead us to more capable models. Where a cloud model was a year ago, we&#8217;ll have locally maybe next year.</span></p><p><strong><span>James:</span></strong><span> Terrific. What did I neglect to ask about? What else should people know, or what else would you like to talk about before we wrap up?</span></p><p><strong><span>Mathias:</span></strong><span> One area I&#8217;m most excited about is how it connects the large-language-model, multimodal domain with other data modalities. We&#8217;ve talked about text, audio, and vision. But there are many more modalities out there &#8212; time series, biological signals.</span></p><p><span>As I mentioned, we&#8217;re training protein models. I think that becomes very interesting &#8212; do you model this by mapping it into text, which seems to be what a lot of big companies are currently doing? They map every modality to text, process it with a large language model, and map it back. Or will there be something smarter out there that already models the data itself?</span></p><p><strong><span>James:</span></strong><span> Let me ask this: some scientists say everything is physics &#8212; ultimately physics is the substrate, and I guess the math is under the physics. But if you build a world model that&#8217;s physics-based, does that imply everything else goes on top of that? Does that make sense at all?</span></p><p><span>That chemistry is physics, biology is physics, and so on.</span></p><p><strong><span>Mathias:</span></strong><span> Yes and no. If you model &#8212;</span></p><p><strong><span>James:</span></strong><span> I realize that&#8217;s something physicists say, which other people may not agree with, but &#8212;</span></p><p><strong><span>Mathias:</span></strong><span> Yes &#8212; a lot of physicists say everything is &#8212;</span></p><p><strong><span>James:</span></strong><span> They say that, right? They say everything is physics, correct?</span></p><p><strong><span>Mathias:</span></strong><span> Physics, yeah. In some sense that&#8217;s correct. If you model everything with &#8212; if you train a world model with some quantum interactions, whatever &#8212; sure, it will work in a way. But the problem is the interesting interactions actually happen at a much higher abstraction scale. Even biology, I would argue, is very bit detached from physics in a way &#8212; how the immune system responds to certain things. It&#8217;s connected to physics and molecular chemistry, obviously, but it&#8217;s already so much detached that if you model it &#8212;</span></p><p><strong><span>James:</span></strong><span> You could argue there are only two types of things in the world: physics and semantics. There&#8217;s language, video, and so on, which are sort of human-constructed artifacts. At some level you could argue the English language doesn&#8217;t describe physical reality &#8212; it&#8217;s not grounded in physical reality. And then you have everything else, which is physics. But as I said, that&#8217;s something physicists say.</span></p><p><strong><span>Mathias:</span></strong><span> Yes &#8212;</span></p><p><strong><span>James:</span></strong><span> And then, math describes them both, I suppose.</span></p><p><strong><span>Mathias:</span></strong><span> Yes, in some way. And I think that&#8217;s totally fine, totally valid. But the question is whether it&#8217;s the right abstraction level to think about. If you model it with an ML model, isn&#8217;t it better to go one abstraction level higher &#8212; talk about chemical interactions, biological interactions, social stuff? At the moment, words have basically emerged as the standard unit &#8212; but you could also model language at the character level instead of words, and those aren&#8217;t that great.</span></p><p><strong><span>James:</span></strong><span> Yeah.</span></p><p><strong><span>Mathias:</span></strong><span> They really struggle. So again, character-level is too low-level &#8212; for some reason, at that resolution, it doesn&#8217;t work as well. Maybe in the future they&#8217;ll come, but at the moment character-level large language models aren&#8217;t at the same scale as word-level. Again, it&#8217;s about the abstraction level at which you model them.</span></p><p><strong><span>James:</span></strong><span> I think your point about abstraction is a good one &#8212; tell me if I&#8217;m being naive. Inorganic chemistry isn&#8217;t that far abstracted from physics. But once you get to biology, you&#8217;re pretty separate from the underlying physics, and that would be hard.</span></p><p><span>We may not be able to draw a straight line from the underlying physics to the biological interaction, so we need to model biology separately, independently, rather than building it up from the physics. Does that make any sense?</span></p><p><strong><span>Mathias:</span></strong><span> Exactly. At least I have a belief this might be the case, based on this tokens-versus-words-versus-character-levels point.</span></p><p><strong><span>James:</span></strong><span> Mm-hmm.</span></p><p><strong><span>Mathias:</span></strong><span> But again, there&#8217;s some dynamics &#8212; so much has changed, there&#8217;s a new approach coming out there. Maybe if you have enough data, this abstraction will emerge within the model. But yeah, that&#8217;s interesting, curious to watch what happens in machine learning going forward.</span></p><h4><span>Physics, Language, and Epistemology</span></h4><div><hr></div><p><strong><span>In this section:</span></strong></p><ul><li><p><span>Lechner is skeptical that intelligence can be built up cleanly from physics: biology, like language modeling itself, seems to work better at a higher level of abstraction than the most granular one.</span></p></li><li><p><span>The word-versus-character-level modeling gap is offered as evidence &#8212; character-level language models consistently underperform word-level ones, suggesting the right abstraction level matters more than raw resolution.</span></p></li><li><p><span>James closes by proposing generative AI as a form of &#8220;entropy transformation,&#8221; a way to learn from the world&#8217;s raw entropy that deterministic systems never could &#8212; an idea Lechner doesn&#8217;t take a position on.</span></p></li></ul><div><hr></div><p><strong><span>James:</span></strong><span> There is part of me that wonders if we as a civilization have fully grasped the epistemological change in front of us &#8212; that we can model things we never imagined we&#8217;d be able to model before. Things that were just too entropic to model, we can now model.</span></p><p><span>Is that too broad a statement, or do you think that&#8217;s a generally correct statement?</span></p><p><strong><span>Mathias:</span></strong><span> I think it depends. There&#8217;s a lot of people who &#8212;</span></p><p><strong><span>James:</span></strong><span> Don&#8217;t go out on a limb there.</span></p><p><strong><span>Mathias:</span></strong><span> &#8212; yeah.</span></p><p><strong><span>James:</span></strong><span> Depends on what? Talk to me.</span></p><p><strong><span>Mathias:</span></strong><span> I think there&#8217;s some people who predicted this &#8212; that artificial intelligence emerges, whether it was through large language models or different paradigms, is more the nuance, the technical detail, that&#8217;s not relevant for them.</span></p><p><span>So that&#8217;s, in some sense, predictable &#8212; a lot of sci-fi &#8212;</span></p><p><strong><span>James:</span></strong><span> Thank you.</span></p><p><strong><span>Mathias:</span></strong><span> &#8212; turned out to be the case. There are probably a lot of people who were right that this was going to win out.</span></p><p><strong><span>James:</span></strong><span> There&#8217;s a book I&#8217;ve been meaning to read for years called </span><em><span>The Dreams Our Stuff Is Made Of</span></em><span>, which I think makes the argument that science fiction has much more influence on technology innovation than we&#8217;ve ever been willing to admit to ourselves &#8212; that the people who do the technology innovation grew up reading science fiction, and it shaped how they think about...</span></p><p><span>It both raised their aspiration levels and shaped how they think about innovation. Now, I haven&#8217;t read the book yet, so I may not be describing it that well, but it&#8217;s on my list of things to read.</span></p><p><strong><span>Mathias:</span></strong><span> Yeah, I think it&#8217;s to some extent probably true.</span></p><p><strong><span>James:</span></strong><span> And I suppose the corollary, just as an aside, is: absent science fiction, we would have a much lower pace of technology innovation.</span></p><p><strong><span>Mathias:</span></strong><span> Yes, probably. It sparks the imagination.</span></p><p><strong><span>James:</span></strong><span> Yeah, it sparks the imagination. You were saying?</span></p><p><strong><span>Mathias:</span></strong><span> Yes.</span></p><p><strong><span>James:</span></strong><span> Okay. Now, one way I think about this, I&#8217;m curious if you agree with this: generative AI is a way of doing entropy transformation. Deterministic systems can&#8217;t process entropy &#8212; they need deterministic, non-entropic information.</span></p><p><span>And for the first time, we can ingest data about the world in all its entropy and start to learn from that. I was wondering if that resonates with you at all.</span></p><p><strong><span>Mathias:</span></strong><span> I&#8217;m not sure.</span></p><p><strong><span>James:</span></strong><span> Well, come back, think about it a little bit. When you come back for the follow-up at some point in the future, you could think about that, or you can shoot me an email. Tell me what you think. Hey, thanks so much.</span></p><p><span>This was a terrific discussion. I very much appreciate you coming on and talking to us.</span></p><p><strong><span>Mathias:</span></strong><span> Thanks so much, James. It was great speaking to you, and thanks for the invitation.</span></p><p><strong><span>James:</span></strong><span> All right, terrific. Thanks.</span></p><p><strong><span>Mathias:</span></strong><span> Awesome.</span></p><h4><span>Footnotes</span></h4><p><span>[1]: </span><a href="https://epoch.ai/publications/what-skills-does-swe-bench-verified-evaluate"><span>Epoch AI&#8217;s analysis of SWE-bench Verified</span></a><span> found the same model&#8217;s score moves purely on scaffold choice, holding the model fixed: Claude 3.7 Sonnet rose from 62.3% to 70.2% under a custom scaffold; GPT-4o rose from 23% (SWE-Agent scaffold) to 33.2% (Agentless scaffold); DeepSeek R1-0528 scored 33% under Epoch&#8217;s own tooling versus 57.6% reported by DeepSeek under the Agentless scaffold. Separately, Cursor&#8217;s engineering team reported taking the same underlying model from 46% to 80% on an identical benchmark, and from Top 30 to Top 5 on Terminal-Bench 2.0, by changing only the harness.</span></p><p><span>[2]: IBM Institute for Business Value, </span><a href="https://www.ibm.com/thought-leadership/institute-business-value/en-us/report/ai-orchestration-layer"><span>&#8220;AI in motion: Orchestrating AI at scale for sovereignty and resilience&#8221;</span></a><span> (2026, with the Dubai Future Foundation, 1,000+ senior leaders across 20 countries) &#8212; organizations with an orchestration-led AI governance layer (coordinating retrieval, evaluation, and guardrails across the AI lifecycle) were roughly 13x more likely to scale AI successfully and reported significantly fewer losses tied to AI errors and misfires, versus peers without one.</span></p><p><span>[3]: White, J.G., Southgate, E., Thomson, J.N., &amp; Brenner, S. (1986). </span><a href="https://doi.org/10.1098/rstb.1986.0056"><span>&#8220;The Structure of the Nervous System of the Nematode Caenorhabditis elegans.&#8221;</span></a><span> </span><em><span>Philosophical Transactions of the Royal Society B</span></em><span>. The original C. elegans connectome paper &#8212; source for the &#8220;three hundred and two neurons&#8221; figure.</span></p><p><span>[4]: Hasani, R., Lechner, M., Amini, A., Rus, D., &amp; Grosu, R. (2021). </span><a href="https://ojs.aaai.org/index.php/AAAI/article/view/16936"><span>&#8220;Liquid Time-constant Networks.&#8221;</span></a><span> </span><em><span>AAAI</span></em><span>. The original LTC paper referenced in the C. elegans/liquid-time-constant-network discussion.</span></p><p><span>[5]: The &#8220;around forty tokens per second&#8221; Raspberry Pi figure is Mathias&#8217;s spoken claim. No published benchmark shows a genuinely large model hitting 40 tok/s on a Raspberry Pi 5 &#8212; independent testing (arXiv, </span><a href="https://arxiv.org/abs/2511.07425"><span>&#8220;An Evaluation of LLMs Inference on Popular Single-board Computers,&#8221;</span></a><span> 2025) puts 7B+ models at 1-3 tok/s, 3B models at 2-5 tok/s, and 1-1.5B models at 5-15 tok/s on that hardware, all memory-bandwidth-bound. The one figure that does land at &#8220;around forty&#8221; is </span><a href="https://www.liquid.ai/blog/lfm2-5-230m"><span>Liquid AI&#8217;s own LFM2.5-230M</span></a><span> &#8212; a 230-million-parameter model, not a large one by any standard measure &#8212; reported at 42 tok/s in under 1GB of RAM. Likely what Mathias means by &#8220;large language model&#8221; here is relative to what people expect an edge device to run at all, not large by parameter count.</span></p><p><em><strong><span>[</span></strong></em><span>6</span><em><strong><span>]: </span></strong></em><span>The &#8220;single digits of millions of dollars&#8221; enterprise token-spend estimate is James&#8217;s spoken estimate. It sits at the low end of the 2026 range: </span><a href="https://www.cloudzero.com/state-of-ai-costs/"><span>CloudZero&#8217;s State of AI Costs 2025 report</span></a><span> put average enterprise AI spend at roughly USD 1MM/year (USD 85,521/month), while </span><a href="https://menlovc.com/perspective/2025-mid-year-llm-market-update/"><span>Menlo Ventures&#8217; 2025 Mid-Year LLM Market Update</span></a><span> put average enterprise AI budgets at roughly USD 7MM/year &#8212; both consistent with &#8220;single digits of millions&#8221; as a typical figure at the time of recording. Agentic workloads are starting to push some companies past that band, though: one healthcare enterprise reportedly burned through more than USD 6MM in six months once agentic AI use took hold, per the </span><a href="https://data.finops.org/"><span>FinOps Foundation&#8217;s State of FinOps 2026 report</span></a><span>.</span></p><p><span>[7]: de Bono, M., &amp; Bargmann, C.I. (1998). </span><a href="https://doi.org/10.1016/S0092-8674(00)81609-8"><span>&#8220;Natural Variation in a Neuropeptide Y Receptor Homolog Modifies Social Behavior and Food Response in C. elegans.&#8221;</span></a><span> </span><em><span>Cell</span></em><span>. Primary source for the social/solitary (</span><code>npr-1</code><span>) distinction underlying the &#8220;social behavior&#8221; reference. See also: de Bono lab et al. (2012), </span><a href="https://doi.org/10.1371/journal.pbio.1001237"><span>&#8220;A Modular Library of Small Molecule Signals Regulates Social Behaviors in Caenorhabditis elegans,&#8221;</span></a><span> </span><em><span>PLOS Biology</span></em><span>, on the signaling mechanism.</span></p>]]></content:encoded></item><item><title><![CDATA[Letter to a vibe coder]]></title><description><![CDATA[Can CIOs and CTO inspire citizen developers to think like software engineers, to combine curiosity with intellectual precision?]]></description><link>https://www.prosaictimes.com/p/letter-to-a-vibe-coder</link><guid isPermaLink="false">https://www.prosaictimes.com/p/letter-to-a-vibe-coder</guid><dc:creator><![CDATA[James Kaplan]]></dc:creator><pubDate>Sun, 02 Aug 2026 21:30:12 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/209504670/aa9a65ba0dc4aef2909dbeeef1b87c20.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>Maybe Sgt. Curtis Culin is the prototype for citizen developers? He innovated in theater and jerry-rigged a way for tanks to break through the hedgerows that bottled Allied forces up in the Normandy beachhead. However, he was a complement to, not a replacement for, the labs, factories and headquarters that developed and orchestrated the technologies and forces required for victory.</p><p>Likewise corporate success in the AI age will require citizen development and traditional, at-scale enterprise technology to coexist. Yes, CIOs must build platforms citizen developers can use. But they also should inspire citizen developers to think, at least a little bit, like software engineers. That makes it more likely that citizen developers will build applications that the technology organizations can co-opt and scale.</p><h3>Citizen development at Normandy</h3><p>More than 900 officers and other ranks worked for General Eisenhower in <a href="https://www.ibiblio.org/hyperwar/USA/COSSAC/">COSSAC</a> (Chief of Staff to the Supreme Allied Commander) coordinating <a href="https://www.nationalww2museum.org/war/articles/planning-d-day-preparing-operation-overlord">thousands of other military and civilian personnel in planning Operation Overlord</a>. Staff studied Normandy from aerial photographs and pre-war maps and yet, as John Keegan recounts in <a href="https://www.nytimes.com/1982/08/15/world/wwii-the-beginning-of-the-end.html">Six Armies in Normandy</a>, they failed to plan for the 15-foot-tall earthen hedgerows that would stymie the advance of invasion forces. Staff knew about the hedgerows, but they so focused on getting onto and then past the beaches, they <a href="https://history.army.mil/portals/143/Images/Publications/catalog/70-60.pdf">didn&#8217;t think enough</a> about what would happen next.</p><p>Culin attached metal prongs to a tank so that it could breach the hedgerows. A demonstration of the <a href="http://www.missing-lynx.com/articles/usa/zaloga_culin_cutter.htm">Culin Rhino</a> impressed Gen. Omar Bradley, who ordered the First Army Ordnance Section to produce it at scale. Decades later in Iraq, US soldiers innovated in similar fashion. When Humvees proved vulnerable to improvised explosive devices they found ways to augment  them with improvised &#8220;<a href="https://history.army.mil/Portals/143/Images/Publications/Publication%20By%20Title%20Images/DAHSUM/PDF/cmhPub_101-35-1.pdf?ver=RIdDk2yrLOVYQt6CCrtE4Q%3D%3D">hillbilly armor</a>&#8221; in theater.</p><p>You can see the skeptics of big IT smiling at each example. Innovation happens at the front lines, they will say. Nobody in an enabling function will understand the business well enough to automate it. I&#8217;ve heard plenty of people say that citizen development will cause the IT shop to wither away, no less than Engels believed that the state would wither away under Communism. Neither has happened yet.</p><h3>Citizen development and at-scale technology will coexist in large institutions</h3><p>Sgt. Culin did not and could not have coordinated the <a href="https://history.army.mil/Portals/143/Images/Publications/ArmyHistoryMag/pdf/AH136.pdf">160,000 troops, 7,000 ships and landing craft and 12,000 airplanes</a> deployed on just the first day of the invasion. Nor could troopers in a maintenance depot in Iraq have realized the <a href="https://warontherocks.com/the-cold-war-offset-strategy-origins-and-relevance/">Second Offset</a>, which brought stealth platforms and precision-guided munitions into reality.</p><p>Citizen development and at-scale technology will coexist in large institutions. Citizen development will push and reshape enterprise technology no less than the desktop revolution did in the 1980s and 1990s. We graybeards remember that ambitious users -- often with equipment funded in departmental budgets -- pushed glass house IT to adopt new technologies and consider new types of applications. Sometimes companies deployed applications initially developed for a few users widely -- when I worked at Deloitte Consulting in the 1990s, everyone entered time and expenses into a database an associate had thrown together in Clipper and created charts using an Excel plug-in some BA had built.</p><p>No, the analyst on the front-lines will not vibe-code your next ERP platform, but he or she has <a href="https://research.aston.ac.uk/en/publications/unpacking-tacit-knowledge-for-requirements-engineering/">local knowledge that many requirements processes will struggle to capture</a>. How can enterprise technology unleash creative talent close to the front-line -- in a safe, scalable manner? Last week I talked about <a href="https://www.prosaictimes.com/p/does-vibe-coding-have-to-mean-technical">how vibe coding will require platforms</a> to enforce architectural standards. But that&#8217;s not enough -- it will also require skills and, especially, mindsets on the part of vibe coders (or citizen developers).</p><h3>Inspire citizen developers to understand the power they have</h3><p>Yes, citizen developers will need to learn the protocols for the platforms they use, but skills have boundaries. Mindsets compound. Every developer learns syntax. Good ones combine curiosity with intellectual precision -- they have a desire to move past the fuzziness that dominates corporate life, understand how things work and how to make them better.</p><p>We want citizen developers to ask not only &#8220;How do I do X?&#8221; but also &#8220;What do I mean by X? Why can&#8217;t I do X now? And: What is the best way I might do X?&#8221; We want them to learn to think a little like software engineers.</p><p>Maybe not a small lift, but no important one is. Can CIOs and CTOs inspire citizen developers not only to do, but also to ask and to learn? If I were to write a letter to a vibe coder, here&#8217;s what it might say:</p><ol><li><p><strong>Automate what you understand.</strong> Years ago, someone asked, a great user of yellow pads, &#8220;What can a computer do?&#8221; I stand by my reply: only what you can do on a yellow legal pad, only much more quickly. If you can&#8217;t sketch it out on a whiteboard, graph paper, in a spiral notebook or on legal pad, you have no business writing a program about it.</p></li><li><p><strong>Models aren&#8217;t magic.</strong> They just perform a statistical prediction of what tokens to use in response to the tokens you provide. A model is only as good as the context it receives. You have to figure out not only what type of context you can provide, but also how accurate an answer that context will yield.</p></li><li><p><strong>Agents need to write things down, just as people do.</strong> We&#8217;ve all stared into a chat window and wondered why the machine can&#8217;t remember something. Context windows are limited and attention degrades. Almost every compute architecture faces memory bottlenecks. LLMs handle large inputs imperfectly, suffering from attention degradation over long context windows. Like a human colleague who forgets verbal directives, force your coding agents to write state and requirements down into explicit artifacts like Product Requirements Documents (PRDs).</p></li><li><p><strong>Many things must be deterministic.</strong> The uncertainty and variety inherent in probabilistic execution make for great brainstorming, but can create unacceptable risk in business logic. Use models to write deterministic code (Python, SQL) that you can isolate, test, and run reliably, rather than relying on an LLM to interpret business logic on the fly.</p></li><li><p><strong>Sometimes models are just as superficial as humans.</strong> Training creates incentives for a model to deliver an answer, not the best answer. Just as with a new joiner, you have to probe a coding agent: Did you consider all possible causes for a bug? Is this the most robust and flexible possible solution?</p></li></ol><h3>Don&#8217;t be afraid to co-opt what citizen developers build</h3><p>For CIOs and CTOs watching an impending onslaught of citizen development: be ready to co-opt the best of it. Gen. Bradley didn&#8217;t penalize Culin for modifying armor; he ordered the Rhino cutter into scaled production. CIOs in the 1990s cherry-picked the best user-developed desktop databases and hardened them for the enterprise. Treat citizen development as a finely-tuned sensor array for organizational friction&#8212;and an opportunity to scale what works.</p>]]></content:encoded></item><item><title><![CDATA[Does vibe coding have to mean technical debt?]]></title><description><![CDATA[A system prompt is not code. Nothing type-checks it, nothing tests it]]></description><link>https://www.prosaictimes.com/p/does-vibe-coding-have-to-mean-technical</link><guid isPermaLink="false">https://www.prosaictimes.com/p/does-vibe-coding-have-to-mean-technical</guid><dc:creator><![CDATA[James Kaplan]]></dc:creator><pubDate>Sun, 26 Jul 2026 20:53:15 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/208602938/e40cdf454d0bd6b57fa30df2cc712433.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<ul><li><p><span>We assume that coding agents will allow business managers to build software</span></p></li><li><p><span>Building useful software requires a technologist&#8217;s mindset, especially in thinking about abstraction</span></p></li><li><p><span>Coding agents incline toward the laziest, most hard-coded solution&#8212;and system prompts aren&#8217;t always helpful</span></p></li><li><p><span>I built a hook- and rule-based governance surface to try to enforce architectural standards</span></p></li><li><p><span>If we want business managers to move to a world where enterprise technology builds platforms and business managers construct their own applications we either need training or tooling to ensure workable architecture. Or both.</span></p></li></ul><div><hr></div><p><span>I sparked a controversy in one of the </span><a href="https://www.prosaictimes.com/p/trading-bad-inefficiency-for-good"><span>Technology Leadership Forum</span></a><span> breakouts back in May. Which is good&#8212;how boring is a breakout session where participants compete to emphasize how much they agree with everyone else.</span></p><p><span>In discussing how building business applications might evolve in coming years, I suggested that we might need more of what they call &#8220;Strats&#8221; in capital markets, people who combine deep insight into a business domain with deep software engineering expertise. Nobody contested that point.</span></p><p><span>Then I noted that many Strats s</span><a href="https://www.prosaictimes.com/p/vibe-coding-doesnt-eliminate-the"><span>tarted out as software engineers who learned about securities markets</span></a><span> and suggested that technologists might learn about many business domains more easily than business managers might learn how to build applications, even with coding agents. [1] This caused more contention. All the technologists in the room worried I might have taken too tech-centric a view.</span></p><h4><span>The importance of a technology mindset</span></h4><p><span>As always, I think it&#8217;s more complicated than that. Back in the 1990s, I was the chief technologist for a small company outside of Boston that created on-line training, demos and the like for technology and media companies. My brief tenure there highlighted the difference between a business mindset and a technology mindset when building software. Business people want to get things done. Fair. Good technologists learn to think in terms of abstraction: How is this task similar to or different from other tasks? Can I build a machine to execute the task rather than execute it myself? Can I add parameters to create a machine that performs similar activities in different contexts?</span></p><p><span>I had created libraries of reusable functions, one for Grasp and one for Visual Basic that turned, in some cases, weeks of work into hours. (I was very proud of this.) Not infrequently, a major new project required an expansion to one of our core libraries.</span></p><p><span>My colleagues had marketing and design backgrounds. When we received a new commission, they just wanted to get things done, and immediately wanted to start typing.</span></p><p><span>I would say &#8220;stop.&#8221; Sketch a user interface. Go for a walk. Take in a movie. Go square dancing. Give me 48 hours without typing.</span></p><p><span>I would spend 24 hours drawing boxes in a spiral notebook and determining the additional functions required for our core library.  For Grasp, I would also sketch out the central control loop -- VB did a lot more of this for you. (Attached photo: a poor recreation of the indecipherable chicken scratch I used to create.)</span></p><p><span>Then I would spend 24 hours coding the additional core functions. Then I would encourage people to start typing. While I got some sleep.</span></p><h4><span>Coding agents are empowering but lazy</span></h4><p><span>Coding agents are empowering. They allow me to do things I would never have the time or patience to do otherwise, like construct the </span><a href="https://www.prosaictimes.com/p/prosaic-times-what-looks-like-fiscal"><span>technology-economic model I have always wanted to build</span></a><span>. [2] But coding agents are lazy&#8212;lazier than the most slovenly hack programmer you can find. They will hard-code anything. Separation of the presentation, application and data layers? Who needs it? [3] I suspect the frontier labs have trained their models on billions of lines of </span><a href="https://arxiv.org/abs/2306.11644"><span>terrible code</span></a><span>. What else is there?</span></p><p><span>Labs train models using </span><a href="https://arxiv.org/abs/2511.18397"><span>reinforcement learning</span></a><span> that rewards passing a test. The model finds the cheapest way to satisfy the exit criteria, and hardcoding is cheaper than abstraction in the short term. CodeRabbit&#8217;s </span><a href="https://www.theregister.com/software/2025/12/17/ai-authored-code-needs-more-attention-contains-worse-bugs/2576263"><span>audit of AI-generated pull requests</span></a><span> found 1.75x more logic and correctness errors, 1.64x more maintainability defects, and 1.57x more security findings than human-written code&#8212;including 2.74x more cross-site-scripting vulnerabilities. At the same time, experienced engineers can also use coding tools to improve </span><a href="https://github.blog/news-insights/research/does-github-copilot-improve-code-quality-heres-what-the-data-says/"><span>software quality</span></a><span>. [4]</span></p><p><span>I assumed that I could use the system prompt to solve problems like this. Hah. As I wrote about in </span><a href="https://www.prosaictimes.com/p/turning-relationships-into-files"><span>Turning relationships into files to vanquish the chaos muppets</span></a><span>, I used junctions (simple markdown files with a noun, verb and an object) rather than wikilinks, YAML front matter or stems to define relationships between entities in my personal knowledge base. I put language in the system prompt about how I wanted the coding agent to use junctions. I might as well have written out a set of policies and procedures for a cat. Maybe amusing; not effective.</span></p><p><span>A system prompt is not code, even if </span><a href="https://www.prosaictimes.com/p/context-is-the-new-code"><span>context is the new code</span></a><span>. Nothing type-checks it, nothing tests it. Two instructions pull in different directions, and the model resolves it silently&#8212;no error, no warning, just whichever rule it weighted more heavily that turn (</span><a href="https://arxiv.org/abs/2511.14342"><span>a 2025 benchmark on LLM conflict handling found the same pattern: consistent detection, inconsistent safe resolution</span></a><span>). My junctions instruction was one more rule in that pile, and it lost.</span></p><h4><span>Using hooks rather than prompts</span></h4><p><span>Eventually I discovered that hooks work better than additions to the system prompt. Classical if-then logic has power. Recently, I sought to extend and formalize that in a governance framework for Prosaic Graff, including both architectural principles and coding standards.</span></p><p><span>The mechanism exploits hooks in Claude Code&#8217;s event lifecycle&#8212;checks that fire automatically after every edit, not instructions I hope the model reads before it acts. There are three moving parts.</span></p><p><strong><span>Rules as graph entities.</span></strong><span> The rules themselves live in the graph the same way everything else in this system does&#8212;as files connected by other files, not as configuration buried in a script. For example, I have junctions indicating what organization people I know work for. The rule below ensures that nobody can have more than one current, full time employer:</span></p><p><code>type: rule<br>rule_type: cardinality<br>applies_to: [Employed-by]<br>scope_field: tense<br>scope_value: present<br>scope_match_blank: true<br>scope_exclude_field: nature<br>scope_exclude_value: part-time<br>max: 1<br>message: "A person may have at most one full-time present Employed-by junction (part-time roles are exempt)"<br>scope: PostToolUse<br>tier: log</code></p><p><strong><span>Rule taxonomy.</span></strong><span> Not every rule is enforced the same way, and the taxonomy matters more than I expected going in.</span></p><ul><li><p><span>Architectural principles, e.g. to mandate building extensions to the graph using junctions between entities rather than by YAML front matter or wikilinks</span></p></li><li><p><span>Entity-schema rules, pure data contracts to ensure required fields and appropriate values in each field (e.g. employment cardinality example above)</span></p></li><li><p><span>Heuristic rules, e.g. patterns for classifying calendar entries by project. These aren&#8217;t deterministic, but at least I know the model will look at all the heuristics when it junctions a calendar entry to a project.</span></p></li></ul><p><strong><span>Hooks.</span></strong><span> A handful of scripts run after every edit, write, and shell command, and check the change against whichever rules apply. I consolidated the mechanism&#8212;schema loading, tier dispatch, junction validation&#8212; into its own package, graff_governance, so the same engine can run against multiple projects.</span></p><p><span>Yes, it&#8217;s overhead but it&#8217;s automated overhead rather than overhead I have to remember. When I applied graff_governance to a </span><a href="https://www.prosaictimes.com/p/hunting-for-entropy-to-find-ai-value"><span>model I built to measure entropy</span></a><span> it found that it had been using stems and front matter when it should have used junctions&#8212;that&#8217;s why it took so much manual tweaking to run correctly.</span></p><p><span>I think the field has been converging on the same answer from a different direction.</span></p><ul><li><p><span>A Codesai engineer&#8217;s </span><a href="https://codesai.com/posts/2026/04/minimal-architecture-constrainsts-in-agentic-world"><span>2026 case for architecture tests over prompt-based &#8220;guidelines&#8221;</span></a><span> makes the identical argument for a narrower target&#8212;code structure, not data structure&#8212;for the identical reason: a second LLM pass auditing the first is non-deterministic and doubles the token cost, so the rule has to become code, not another instruction.</span></p></li><li><p><span>Speakeasy&#8217;s </span><a href="https://www.speakeasy.com/resources/ai-agent-hooks/"><span>framing of agent hooks as an &#8220;AI control plane&#8221;</span></a><span> describes the exact primitive this system runs on, arrived at independently. Where this system differs is the object being governed: everyone else is gating code&#8212;what compiles, what a linter flags, what a Terraform plan would deploy. This gates the integrity of the graph and the code together using the same mechanism[6]&#8212;detect after the fact, tier by severity, never prevent before the write.</span></p></li></ul><p><span>Vendors seem to be working on the domain, though nobody has an end-to-end solution yet. Every piece exists somewhere; the combination doesn&#8217;t, but probably will soon. [5] [6]</span></p><p><span>Will this work for me? I think so, at least for me, although it has teething problems, especially in making the language in the rules both specific and broadly applicable.</span></p><p><span>What does this experiment say about citizen developers, especially those who want to build more than a simple report? We can imagine a world where enterprise technology provides platforms and citizen developers create applications that solve business problems. It might unleash innovation or create crippling technical debt. Making the model workable will require building tools to govern vibe coding or enhance citizen developer skill sets&#8212;or both.</span></p><h4><span>Footnotes</span></h4><p><span>[1] Obviously this varies by domain. Few software engineers will pick up large molecule pharma manufacturing quickly. Marketing or HR, on the other hand?</span></p><p><span>[2] Yes, I&#8217;m very popular at cocktail parties.</span></p><p><span>[3] I discovered this when I split my model into a front end and back end. Watching text scroll by on the screen, I saw the coding agent had jammed calculations into the front end. &#8220;No!&#8221; I shouted. When I asked one of the senior-most executives at the company that shipped the coding agent why I did that, he replied &#8220;Some people might want that.&#8221; Some people might want to put chocolate syrup on their brussels sprouts or wear brown shoes with a blue suit. Doesn&#8217;t make it right.</span></p><p><span>[4] Even though studies from technology vendors may have a predisposition, they also can provide useful signal.</span></p><p><span>[5] Some companies working in the space include</span></p><ul><li><p><span>Open Policy Agent&#8217;s Gatekeeper binds a policy to a resource type through an explicit link, the closest existing match to what Applies-to does, but nothing in its </span><a href="https://open-policy-agent.github.io/gatekeeper/website/docs/audit/"><span>audit-controller design</span></a><span> lets a policy&#8217;s own firing frequency promote or retire it.</span></p></li><li><p><span>Guardrails AI&#8217;s </span><a href="https://www.guardrailsai.com/docs/concepts/validator_on_fail_actions"><span>on_fail taxonomy</span></a><span>&#8212;hard-fail, auto-correct, suppress, log-only&#8212;is the best-documented tiered-severity model in the AI-guardrail space.</span></p></li><li><p><span>LaunchDarkly&#8217;s </span><a href="https://launchdarkly.com/docs/home/releases/flag-health"><span>stale-flag detection</span></a><span> is the closest real-world analog for automated retirement, gated on evaluations run rather than violations triggered, so a rule that&#8217;s working perfectly doesn&#8217;t get mistaken for a dead one.</span></p></li></ul><p><span>[6] Yes, SHACL and OWL have bound a rule to a type explicitly for two decades&#8212;that part of the claim isn&#8217;t new. What they don&#8217;t do is fire off a live edit, tier the resulting violation by severity, or use how often a rule fires to decide whether it survives. Static graph validation and a governance layer wired into an agent&#8217;s tool-call lifecycle are different animals wearing the same constraint-binding coat.</span></p><p><span>[6] The rule itself only ever inspects file shape&#8212;front matter block versus junction file&#8212;never the code that consumes it. But how you model a relationship is an architecture decision, and getting it wrong costs you in code, not just in data: the entropy model above needed manual tweaking precisely because its relationships were shaped wrong. The junctions rule, for example, draws that line from data into code. </span></p>]]></content:encoded></item><item><title><![CDATA[Hunting for entropy to find AI value]]></title><description><![CDATA[Relying on a system prompt is like sending a policy memo to a toddler]]></description><link>https://www.prosaictimes.com/p/hunting-for-entropy-to-find-ai-value</link><guid isPermaLink="false">https://www.prosaictimes.com/p/hunting-for-entropy-to-find-ai-value</guid><dc:creator><![CDATA[James Kaplan]]></dc:creator><pubDate>Mon, 20 Jul 2026 01:13:17 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/207720663/a3be58290d3e7af4ea671d618028a2e4.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p><span>Apologies for the delayed send tonight -- it was a busy weekend. Mrs. Prosaic Times and I saw </span><a href="https://www.prosaictimes.com/p/prosaic-times-how-enterprise-technology"><span>Joe Jackson</span></a><span>, and I also spent a lot of time with Claude Code.</span></p><p><span>There is no such thing as </span><a href="https://www.prosaictimes.com/p/vibe-coding-doesnt-eliminate-the"><span>vibe coding</span></a><span>, at least for anything important. Coding agents will hard code anything (maybe they are allergic to parameters?) and will always default to procedural over declarative language. Relying on a system prompt is like sending a policy memo to a toddler -- it might be amusing but doesn&#8217;t change behavior much. If you want to enforce an architectural standard, create a deterministically fired hook. And if I hadn&#8217;t wired up a skill to apply the </span><a href="https://asq.org/quality-resources/five-whys"><span>five whys</span></a><span> to root cause analysis, I might have gone batty.</span></p><p><span>What was I working on? How to think about GenAI and entropy.</span></p><p><span>From the outside building a system looks simple. You just need some data and some rules to act on that data:</span></p><ul><li><p><span>If a customer buys product x, charge her USD 20.00</span></p></li><li><p><span>If a passenger is on the manifest let him on the plane</span></p></li><li><p><span>If a user has rights to a document, let her open it</span></p></li></ul><p><span>But we live on Planet Earth. Even before you start to deal with issues like scale, resiliency and security, the data and business rules prove much fuzzier than the simple examples we sketch out on a whiteboard.</span></p><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.prosaictimes.com/p/hunting-for-entropy-to-find-ai-value?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">If you like this issue, share it with a friend!</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.prosaictimes.com/p/hunting-for-entropy-to-find-ai-value?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.prosaictimes.com/p/hunting-for-entropy-to-find-ai-value?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><h3><span>Entropy makes enterprise technology expensive and frustrating</span></h3><p><span>In many domains, who is the customer and what is the product can be uncertain; the data may be incomplete; the rules for applying discounts or granting access to resources may get dizzingly complex. A couple of weeks ago, I suggested:</span></p><ul><li><p><span>Information systems use a simplified model of an entropic world to derive analytic insights and automate business processes. The more entropic the domain the more expensive it is to build the system and/or the less faithfully it reflects the underlying reality.</span></p></li><li><p><span>Much of the frustration we have with enterprise systems derives from the gap between entropic reality and the deterministic systems we use to model it &#8212; that&#8217;s why companies spend </span><a href="https://www.mckinsey.com/capabilities/tech-and-ai/our-insights/the-erp-platform-play-cheaper-faster-better"><span>hundreds of millions of dollars paying to create intricate business rules for their ERP platforms</span></a><span> and why </span><a href="https://blog.hubspot.com/sales/get-your-team-to-use-crm-software"><span>account executives complain they hate using CRM applications.</span></a></p></li><li><p><span>Naturally GenAI doesn&#8217;t make a messy world any less messy, but it reduces the cost of reflecting reality in formal information systems (e.g. by converting entropic user requirements to deterministic code or converting free text to structured data). This makes it economical to expand analytics and automation in a way that would not have been economical even a year ago.</span></p></li><li><p><span>Many companies succeeded in automating low-entropy business processes a decade ago or more. Origination systems for consumer credit cards and underwriting systems for personal auto insurance tend to work pretty well. Systems to support provisioning treasury services for large enterprises work less well.</span></p></li></ul><h3><span>How to look for entropy</span></h3><p><span>So in making decisions about funding and designing AI systems you want to understand where the entropy exists in your business system and how AI could help you ameliorate the challenges it creates -- so I wired up a methodology for assessing business domains for entropy. Again -- I just would not have gotten there without my 5-whys skill.</span></p><p><span>There are eight markers of entropy</span></p><ul><li><p><span>Data opacity: ambiguity, incompleteness, lack of structure and heterogeneity</span></p></li><li><p><span>Rule/path complexity: discretion, rule volume/velocity, path variance, rule interdependency</span></p></li></ul><p><span>You can use these markers to score domains &#8212; here I did it for governance, risk and compliance in cybersecurity, but the same markers can apply to any business domain.</span></p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!fIvK!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb93659ce-b1e5-423b-9e3e-58d575236a3d_2368x1142.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!fIvK!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb93659ce-b1e5-423b-9e3e-58d575236a3d_2368x1142.png 424w, https://substackcdn.com/image/fetch/$s_!fIvK!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb93659ce-b1e5-423b-9e3e-58d575236a3d_2368x1142.png 848w, https://substackcdn.com/image/fetch/$s_!fIvK!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb93659ce-b1e5-423b-9e3e-58d575236a3d_2368x1142.png 1272w, https://substackcdn.com/image/fetch/$s_!fIvK!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb93659ce-b1e5-423b-9e3e-58d575236a3d_2368x1142.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!fIvK!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb93659ce-b1e5-423b-9e3e-58d575236a3d_2368x1142.png" width="1456" height="702" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/b93659ce-b1e5-423b-9e3e-58d575236a3d_2368x1142.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:702,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:182465,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://www.prosaictimes.com/i/207720663?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb93659ce-b1e5-423b-9e3e-58d575236a3d_2368x1142.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!fIvK!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb93659ce-b1e5-423b-9e3e-58d575236a3d_2368x1142.png 424w, https://substackcdn.com/image/fetch/$s_!fIvK!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb93659ce-b1e5-423b-9e3e-58d575236a3d_2368x1142.png 848w, https://substackcdn.com/image/fetch/$s_!fIvK!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb93659ce-b1e5-423b-9e3e-58d575236a3d_2368x1142.png 1272w, https://substackcdn.com/image/fetch/$s_!fIvK!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb93659ce-b1e5-423b-9e3e-58d575236a3d_2368x1142.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p><span>Here&#8217;s the rationales for the scores for Security Governance:</span></p><ul><li><p><strong><span>Ambiguity:</span></strong><span> Governance frameworks provide defined structure, but determining what &#8220;adequate governance&#8221; means for a given organization&#8217;s risk appetite and maturity level involves genuine interpretation &#8212; the data exists, but the correct read of it is contestable.</span></p></li><li><p><strong><span>Incompleteness &amp; Unreliability:</span></strong><span> Governance functions operate on formal documentation &#8212; policies, board minutes, audit findings, program metrics. The evidence base is largely complete and verifiable; the bottleneck is not data gaps but the effort of assembly and analysis.</span></p></li><li><p><strong><span>Lack of Structure:</span></strong><span> The inputs to a governance assessment are almost entirely unstructured &#8212; board presentations, committee minutes, risk appetite statements, policy documents, external audit reports.</span></p></li><li><p><strong><span>Heterogeneity:</span></strong><span> Multiple frameworks coexist (NIST, ISO, CIS, COBIT, SOC 2), but they are generally reconcilable &#8212; different naming conventions, not fundamentally incompatible schemas. Moderate cross-system joins, not deep structural incompatibility.</span></p></li><li><p><strong><span>Discretion:</span></strong><span> Governance decisions &#8212; which risks to formally accept, how to rate program maturity, whether to grant policy exceptions &#8212; require professional judgment. The framework bounds that judgment but does not eliminate it; edge cases and proportionality calls are routine.</span></p></li><li><p><strong><span>Path Variance:</span></strong><span> Governance workflows vary sharply by industry, regulatory regime, board composition, and organizational structure -- and often include different paths for different types of issues or questions</span></p></li><li><p><strong><span>Rule Interdependency:</span></strong><span> Governance rules are densely interconnected &#8212; a change in risk appetite cascades to control selection, exception thresholds, audit scope, and reporting requirements. Policies reference standards that reference frameworks that reference regulations; downstream effects of any single rule change are hard to trace.</span></p></li><li><p><strong><span>Rule Volume &amp; Velocity:</span></strong><span> The regulatory surface is expanding rapidly &#8212; SEC cyber disclosure rules, DORA, NIS2, state privacy laws, updated NIST CSF 2.0. Governance teams must continuously track a high and growing volume of requirements that change on timescales shorter than most policy review cycles.</span></p></li></ul><p><span>These markers don&#8217;t just tell you where to spend &#8212; they tell you how to build.</span></p><ul><li><p><span>Ontic entropy needs tools that organize context for a human decision, not tools that try to make the decision instead; more automation doesn&#8217;t shrink a gap that has no single right answer.</span></p></li><li><p><span>Epistemic and representational entropy point to a different design: instrumentation, ingestion, agentic conversion &#8212; the missing piece is data, not judgment, and GenAI&#8217;s job is to make structured data cheaper to produce.</span></p></li><li><p><span>Rule-side entropy is a formalization problem, not a data problem: the rules already exist, scattered across policy documents, regulatory text, and precedent &#8212; GenAI&#8217;s job there is to ingest that material and derive deterministic rules from it, so path variance and rule interdependency get resolved once in code instead of re-litigated by hand every time a case comes up.</span></p></li></ul><p><span>If you don&#8217;t understand the entropy you face, you might invest in the wrong place or you might build the wrong system &#8212; a judgment-support tool for a data problem, or an automation pipeline for a problem that was never going to reduce to a rule.</span></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.prosaictimes.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading Prosaic Times &#8212; subscribe to receive every issue!</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h3><span>Appendix: Entropy markers</span></h3><p><span>You can think of entropy in terms of three dimensions</span></p><ul><li><p><strong><span>Source:</span></strong><span> What is the underlying reason for the uncertainty</span></p></li><li><p><strong><span>Degree of uncertainty:</span></strong><span> How much uncertainty remains after collection of all available facts</span></p></li><li><p><strong><span>Possible mitigation:</span></strong><span> How GenAI can help bridge the gap between messy reality and formal system</span></p></li></ul><h4><span>Data opacity</span></h4><p><strong><span>Ambiguity</span></strong></p><ul><li><p><strong><span>Description:</span></strong><span> There are multiple plausible interpretations  &#8212; the world itself doesn&#8217;t have a single answer.</span></p></li><li><p><strong><span>Examples:</span></strong><span> What stage in the pipeline is this deal in? Who is the decision maker for a corporate customer?</span></p></li><li><p><strong><span>Source:</span></strong><span> Ontic &#8212; the uncertainty is real, not a data gap; more information may provide context, but won&#8217;t resolve the question definitively</span></p></li><li><p><strong><span>Degree of uncertainty:</span></strong><span> Persistent: uncertainty remains above zero even with all available evidence  <br></span><strong><span>Possible mitigations:</span></strong><span> Use GenAI to collect and organize the data required for human judgement. You may not be able to mathematically derive what stage the deal is in, but at least you can know who has provided input on it</span></p></li></ul><p><strong><span>Incompleteness and unreliability</span></strong></p><ul><li><p><strong><span>Description:</span></strong><span> Data needed to answer the key question is missing, outdated, or contradicted by another source.</span></p></li><li><p><strong><span>Examples:</span></strong><span> Incomplete and out of date information about critical systems stored in CMDB</span></p></li><li><p><strong><span>Source:</span></strong><span> Epistemic &#8212; the missing data could in principle be found or the conflict resolved, but right now it isn&#8217;t there.</span></p></li><li><p><strong><span>Degree of uncertainty:</span></strong><span> Approaches maximum &#8212; the data that would resolve the question is absent or irreconcilably contradictory.</span></p></li><li><p><strong><span>Possible mitigations:</span></strong><span> Use GenAI to collect additional information (i.e. by instrumenting processes) or to address anomalies and flaws by inferring patterns</span></p></li></ul><p><strong><span>Lack of structure</span></strong></p><ul><li><p><strong><span>Description:</span></strong><span> Information exists but is encoded in formats a system cannot read &#8212; email, PDF, voice, handwritten notes.\</span></p></li><li><p><strong><span>Examples:</span></strong><span> Clinical treatments stored in free text notes. Business cases stored in spreadsheets or word processing documents.</span></p></li><li><p><strong><span>Source:</span></strong><span> Representational &#8212; the information exists and is possibly determinate, just historically expensive to access (i.e. would require an analyst to spend hours converting unstructured text to structured data)</span></p></li><li><p><strong><span>Degree of uncertainty:</span></strong><span> Artificially high &#8212; you can eliminate it entirely, though it has been historically expensive  </span></p></li><li><p><strong><span>Possible mitigations:</span></strong><span> Use agentic data ingestion to convert unstructured text to machine-readable structured data that you can use to derive analytic insights from or transact against</span></p></li></ul><p><strong><span>Heterogeneity</span></strong></p><ul><li><p><strong><span>Description:</span></strong><span> Relevant data is split across systems with incompatible formats that cannot be automatically joined.</span></p></li><li><p><strong><span>Examples:</span></strong><span> Enterprise counterparty exposure spread across trading, lending, and derivatives systems with different identifiers; claims data split across billing, underwriting, and adjudication systems.\</span></p></li><li><p><strong><span>Source:</span></strong><span> Representational &#8212; the information exists and is possibly determinate, just historically expensive to reconcile</span></p></li><li><p><strong><span>Degree of uncertainty:</span></strong><span> Artificially high &#8212; you can eliminate it entirely, though it has been historically expensive  </span></p></li><li><p><strong><span>Possible mitigations:</span></strong><span> Use GenAI to interrogate differences across data sets and create connections to a shared schema</span></p></li></ul><h4><span>Rule/path complexity</span></h4><p><strong><span>Discretion</span></strong></p><ul><li><p><strong><span>Description:</span></strong><span> The goal and the facts are known, but the correct action cannot be reduced to a rule &#8212; professional judgment fills the gap.</span></p></li><li><p><strong><span>Examples:</span></strong><span> There is no set of imaginable rules for addressing the concerns of an angry corporate customer &#8212; requires instinct and tact</span></p></li><li><p><strong><span>Source:</span></strong><span> Ontic &#8212; this is not an information problem; you can&#8217;t even define a specific set of actions to pick from</span></p></li><li><p><strong><span>Degree of uncertainty:</span></strong><span> Remains above zero even with complete information &#8212; two experienced practitioners given the same situation arrive at different but equally defensible answers.</span></p></li><li><p><strong><span>Possible mitigations:</span></strong><span> Use GenAI to capture information and provide humans with additional context required for exercising discretion</span></p></li></ul><p><strong><span>Path variance</span></strong></p><ul><li><p><strong><span>Description:</span></strong><span> Cases of the same type require materially different handling &#8212; different workflows, skills, or systems depending on the specifics.</span></p></li><li><p><strong><span>Examples:</span></strong><span> Trade settlement &#8212; handling varies by instrument type, counterparty jurisdiction, and settlement method; insurance claims &#8212; standard auto, total loss, disputed liability, and catastrophe each require different workflows.</span></p></li><li><p><strong><span>Source:</span></strong><span> Formalization &#8212; converting complicated rules to formal language is possible, but historically expensive</span></p></li><li><p><strong><span>Degree of uncertainty:</span></strong><span> Ultimately reducible, but historically expensive</span></p></li><li><p><strong><span>Possible mitigations:</span></strong><span> Use agentic software engineering, which changes tradeoffs about how many rules you can automate economically</span></p></li></ul><p><strong><span>Rule interdependency</span></strong></p><ul><li><p><strong><span>Description:</span></strong><span> Rules cannot be evaluated independently &#8212; the outcome of one governs which others apply, or multiple rules conflict for the same input.</span></p></li><li><p><strong><span>Examples:</span></strong><span> Union contracts with grandfathered provisions that modify base rules that themselves modify exception rules; tax deductions subject to phase-outs that interact with alternative minimum tax calculations.\</span></p></li><li><p><strong><span>Source:</span></strong><span> Formalization &#8212; sorting out the interactions among rules is possible but historically expensive</span></p></li><li><p><strong><span>Degree of uncertainty:</span></strong><span> Ultimately reducible, but historically expensive</span></p></li><li><p><strong><span>Possible mitigations:</span></strong><span> Use GenAI to reason across the full rule dependency graph; surface conflicts and identify the permissible path when rules interact.</span></p></li></ul><p><strong><span>Rule volume and velocity</span></strong></p><ul><li><p><strong><span>Description:</span></strong><span> The rule set is too large to manually search or too frequently updated to keep encoded guidance current.</span></p></li><li><p><strong><span>Examples:</span></strong><span> Thousands of new potential security rules requiring assessment against a specific asset inventory to determine whether it applies and how urgently; cloud security benchmarks updated quarterly as new services launch, meaning previously compliant configurations go stale without any change on the organization&#8217;s part</span></p></li><li><p><strong><span>Source:</span></strong><span> Formalization &#8212; a large rule set is expensive to capture; a fast-changing one means captured rules go stale before teams can update them.</span></p></li><li><p><strong><span>Degree of uncertainty:</span></strong><span> High because finding and applying the right rule is expensive &#8212; not because the answer itself is unclear.</span></p></li><li><p><strong><span>Possible mitigations:</span></strong><span> Semantic indexing of the full rule set; automated </span></p></li></ul>]]></content:encoded></item><item><title><![CDATA[What Kalashnikov and Heisenberg understood about getting value from AI]]></title><description><![CDATA[A conversation with Sentra founder Ashwin Gopinath on capturing, structuring and exploiting organizational context]]></description><link>https://www.prosaictimes.com/p/what-kalashnikov-and-heisenberg-understood</link><guid isPermaLink="false">https://www.prosaictimes.com/p/what-kalashnikov-and-heisenberg-understood</guid><dc:creator><![CDATA[James Kaplan]]></dc:creator><pubDate>Sun, 12 Jul 2026 21:00:24 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/206676947/25cd543bce6387ab1afa0f16f8842400.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p><span>What do big-company CEOs want to know about AI? A group I sat with last month acknowledged AI&#8217;s transformative potential, but doubted they could send all their people on one long coffee break and replace them with agents. So they asked: what does the person do, and what falls to the machine? How do you move a fractious organization to adopt and get value from AI?</span></p><p><span>The US military defines a </span><a href="https://csrc.nist.gov/glossary/term/weapons_system"><span>weapon system</span></a><span> as not just the hardware, but &#8220;a combination of one or more weapons with all related equipment, materials, services, personnel, and means of delivery and deployment required for self-sufficiency.&#8221; US Army rifles like the M-4 and M-16 assume disciplined, well-trained forces; Mikhail Kalashnikov designed the AK-47 for an indifferently trained, poorly-educated </span><a href="https://catalogimages.wiley.com/images/db/pdf/9780470168806.excerpt.pdf"><span>conscript army</span></a><span>. [9]</span></p><p><span>No less true in automating (or applying AI to) business domains than in equipping infantry platoons. Somebody has to use the bloody system in some way, and they may not want to use it in the way you want them to. Salespeople may not want to enter all their relationship information. Service techs may want to spend more time fixing customer problems and less time entering data on what they did. Doctors may disregard recommendations from a clinical support system.</span></p><p><span>Business or technology transformation initiatives are simple on </span><a href="https://publish.uwo.ca/~cyano/UWOTrick/Past_Handouts_files/Friedman,%20NYTM%201970.pdf"><span>Planet Milton Friedman</span></a><span>. We all do rigorous strategic, operational and technology analysis. We formulate a business case. And if it plausibly exceeds the hurdle rate, senior leaders adopt it and implement the material incentives for everyone in the organization to prosecute it ruthlessly.</span></p><p><span>Frustratingly and wonderfully, we live on Planet Earth, not Planet Milton Friedman. Managers have other objectives and constraints in addition to maximizing their bonuses. They have different risk tolerances. Measuring contribution is hard, especially for more strategic and transformative initiatives. So client executives who want to achieve big things must be savvy political operators as well as astute business strategists. In the technology context, I framed this as CIOs needing to be </span><a href="https://www.prosaictimes.com/p/just-like-parents-cios-must-be-demon"><span>demon game theorists</span></a><span> to achieve the cooperation they need for success.</span></p><p><span>Getting any complicated bill through the US Congress requires careful coalition management. Add this provision and you pick up a few votes tied to one lobby or another. And that provision you pick up a few more votes tied to a second lobby, but you might lose a few too because you have disadvantaged some regional interest or another. And, take care, add too many expensive provisions in hopes of picking up votes and you might lose deficit hawks who want to keep the total ticket under a certain number.</span></p><p><span>We&#8217;ve all gone through this in constructing business cases. Exempt one local market from consolidation to avoid a political fight and the benefits decline more than the investments. Accept more conservative savings assumptions to get operations on board and the ROI attenuates further. The CFO insists on smaller investments in the first year. Figuring out a value-creating direction is hard. Assembling a ROI-positive path through political realities to get there is brutal.</span></p><p><span>Very little of the information required to determine how humans and machines should interface or how to assemble a politically-viable, ROI-positive business case appears in any database. Even when written down it&#8217;s ambiguous and stored in dozens of different spreadsheets, email threads and chat streams and, now, videoconference transcripts.</span></p><p><span>Ashwin Gopinath, Co-founder and CEO of Sentra, [2] wants to make the information substrate that busineses need to make complicated, multi-dimesional decisions legible. AI won&#8217;t solve the problem for you, but it make make the required information legible enough so that you can. [3]</span></p><p><span>Remember: ProsaicTimes never endorses companies or technologies. But we find insight in talking directly to builders about the future they are trying to create.</span></p><h4><span>A Polymath&#8217;s Unplanned Path</span></h4><div><hr></div><p><strong><span>In this section:</span></strong></p><ul><li><p><span>Ashwin describes his journey across physics, biology, and AI</span></p></li><li><p><span>How following interesting problems rather than a career plan connected disparate fields</span></p></li><li><p><span>Why the most interesting people rarely have a predetermined map</span></p></li></ul><div><hr></div><p><strong><span>James Kaplan:</span></strong><span> Hi there, this is James Kaplan with another ProsaicTimes video podcast. With me I have Ashwin Gopinath &#8212; why don&#8217;t we start out with you introducing yourself a little bit, talking about your journey, and telling us how you came to Sentra? </span></p><p><strong><span>Ashwin Gopinath:</span></strong><span>  I started in one area and got pulled into working with biomolecules, because that was the only way I could get to the molecules I cared about. That opened two pathways at Caltech.</span></p><p><span>Then some personal moments led me to get interested in biology as a systems problem &#8212; something I could connect to a sense of social responsibility. That pulled me into a whole other set of work. And then I realized what was happening: I was chasing the unifying thread, not the discipline.</span></p><p><strong><span>James:</span></strong><span> Well, the most interesting people never have a plan. Sometimes we create artificial divisions between knowledge domains. The physicists will say it&#8217;s all physics, and those of us who are history majors will say it&#8217;s all history.</span></p><p><strong><span>Ashwin:</span></strong><span> You are only as good as your context. The way one person can connect things is remarkable. But the problem with teams is that people don&#8217;t know what they&#8217;re working on in aggregate. The collective has no privileged vantage point &#8212; each person knows only their slice. If you know 100 people, not all of them know what the others know.</span></p><p><strong><span>James:</span></strong><span> Alan Kay [1] said that context is worth 20 IQ points, or context is worth 50 IQ points, depending on which version of the remark you&#8217;ve heard. History is context. And it is interesting to think about human context versus machine context, because all of us are operating in a professional environment, swimming in context and never quite able to manage it all. There are a zillion emails, a zillion chat messages, a zillion documents to read, and we can never quite assimilate it.</span></p><p><strong><span>Ashwin:</span></strong><span> That&#8217;s precisely where the friction lives. The CEO, the C-suite &#8212; they believe they know what the organization knows, but they only know their slice of it. They may know their own knowledge, perhaps. But in practice, they don&#8217;t know what others know. That generates enormous friction.</span></p><p><strong><span>James:</span></strong><span> Have you ever read anything by Peter Turchin? He overstates his point a little, but his theory is that </span><em><span>asabiya</span></em><span> &#8212; an Arabic term &#8212; is the discriminant between successful and unsuccessful societies. It means common purpose and willingness to sacrifice for that common purpose. But one definition I&#8217;ve seen is knowing what you&#8217;re supposed to do without being told &#8212; everyone has enough shared context that the next action becomes obvious, and everybody moves left or moves right without having to be directed.</span></p><p><strong><span>Ashwin:</span></strong><span> Some of that gets called culture in any meaningful sense, or people describe it as a shared operating system. But the thing is, there are these ephemeral artifacts that some groups have &#8212; and the question I keep coming back to is: can we use AI to start building that? Can we get groups into that state faster?</span></p><p><strong><span>James:</span></strong><span> You could argue that the humanistic aspects of AI are the most interesting ones. There&#8217;s an age-old question about how you generate what the military would call unit cohesion &#8212; without engendering groupthink. That is a tough issue. People have probably struggled with it from the beginning of time.</span></p><p><strong><span>Ashwin:</span></strong><span> That is part of what led me to work on Sentra. The important problem &#8212; what Sentra is trying to do &#8212; is to be there and make sure everyone arrives at the same page. The question is how you sustain that as things move forward.</span></p><div><hr></div><h4><span>Context, Memory, and AI Alignment</span></h4><div><hr></div><p><strong><span>In this section:</span></strong></p><ul><li><p><span>The challenge of aligning human and machine context in organizations</span></p></li><li><p><span>Human memory, utility functions, and lossy compression in AI context windows</span></p></li><li><p><span>Why structure in memory aids both programmatic analysis and human recall</span></p></li></ul><div><hr></div><p><strong><span>James:</span></strong><span> It&#8217;s not only a hard problem &#8212; different motivations make it harder or easier depending on the environment. On an old-fashioned equity trading floor, decades ago before electronic trading, you could align people because there was a P&amp;L at the end of the day. You had clear risk parameters and a clear profit-and-loss statement on the book. If you made money, that was good; if you didn&#8217;t, that was bad. But most of business isn&#8217;t like that.</span></p><p><span>Even where you have quantitative metrics, you may have multiple conflicting ones &#8212; this went up, but that went down. Or metrics that are overdetermined: this happened because you did this and I did that. How much was you versus me? Or you may have things that are hard to measure, ambiguous data. If you&#8217;re in the consumer world, measuring customer satisfaction is easy, but in a corporate world where you may have 50 different stakeholders in a relationship, how do you measure satisfaction?  </span></p><p><strong><span>Ashwin:</span></strong><span> When people think about utility functions in AI, they&#8217;re making the point that you define the behavior &#8212; and if you define the behavior poorly, it gets defined for you. The whole behavioral-economics school of thought is bound up with this definitional challenge: what does the model think it is optimizing, and what are we actually asking it to do?</span></p><p><span>The biological approach, if you think of the utility function as a kind of lossy compression, is that you compress away what you don&#8217;t believe is important. But the interesting thing is, if you need everything, you&#8217;re not running the compression correctly &#8212; you&#8217;re just storing.</span></p><p><strong><span>James:</span></strong><span> When you say memory, do you mean memory in the context window, or memory stored to a file &#8212; which may be a graph?</span></p><p><strong><span>Ashwin:</span></strong><span> I mean both, but I lean toward the latter. I think the ability to go to 100 million tokens is meaningful, but what matters is whether you can actually reach what you need at inference time.</span></p><p><strong><span>James:</span></strong><span> Here&#8217;s why I&#8217;m skeptical of the context window. Thirty years of hanging around data centers tell me the constraint is never the compute &#8212; it&#8217;s always the memory. And as I read the charts, the compute is improving in capability more quickly than the bus to the memory is. </span></p><p><span>The context window is constructed using lossy compression [5] &#8212; which is obviously not the same as anything you write to a file. Anything involving lossy compression is, at some level, going to be unreliable &#8212; the question is how unreliable. And the beautiful thing about system memory as opposed to human memory is you do have infinite long-term memory if you mediate it with structure. [4]</span></p><div><hr></div><h4><span>Capturing Meetings and Extracting Structure</span></h4><div><hr></div><p><strong><span>In this section:</span></strong></p><ul><li><p><span>How Sentra approaches capturing unstructured professional conversations</span></p></li><li><p><span>Identifying primitives &#8212; decisions, risks, issues &#8212; from fast-moving dialogue</span></p></li><li><p><span>The challenge of determining whether something is one decision or two</span></p></li></ul><div><hr></div><p><strong><span>James:</span></strong><span> Now, I think you&#8217;re doing some really interesting stuff around capturing conversations. To me, this is one of those things that is incredibly difficult and deceptively important, because in a professional environment, we spend a lot of time in meetings &#8212; and then we walk out and say, my God, what just happened? </span></p><p><strong><span>Ashwin:</span></strong><span> At the top level, you have the external artifacts &#8212; the Slack messages, the emails, the decks, the reports, the minutes. But underneath that, there&#8217;s a bunch of people having a discussion. And beneath that there&#8217;s something else: a set of primitives. Those primitives may be decisions, risks, issues, deliverables, questions, work streams &#8212; it will vary by business context.</span></p><p><span>What we&#8217;re trying to do is use the semantics available from the meeting itself, combined with the semantics you can get from the organizational graph &#8212; who are the visitors, the teams, the stakeholders &#8212; and pull out those primitives reliably. So the question we&#8217;re always asking is: what is the smallest meaningful unit of work or commitment that came out of this conversation?</span></p><p><strong><span>James:</span></strong><span> That sounds like an object model. Do you have inheritance and polymorphism in there at all?</span></p><p><strong><span>Ashwin:</span></strong><span> Yes &#8212; there is a hierarchical structure, and entities do carry properties inherited from their context. The graph structure lets you traverse those relationships.</span></p><p><strong><span>James:</span></strong><span> The thing I always struggle with is: is one thing one thing, or is one thing two things? If you&#8217;re thinking about redesigning an IT organization &#8212; is the decision to consolidate across business units the same as the decision to optimize? You could argue they&#8217;re two discrete decisions. You could optimize in place without consolidating. But consolidating without optimizing seems pointless, and optimizing in place without consolidating gives you no scale effects. Theoretically, two decisions; practically, one. How do you think about that?</span></p><p><strong><span>Ashwin:</span></strong><span> The way we handle it is probabilistic rather than deterministic. If the semantics of two threads are entangled &#8212; if resolving one consistently changes the frame of the other &#8212; we surface that dependency as a relationship in the graph rather than forcing a merge or a split. The human gets to see that these are linked and decide whether to treat them as one or two.  </span></p><p><strong><span>James:</span></strong><span> Ultimately a person or a group of people make a decision, sometimes very ambiguously. I tend to think of those as two separate and incredibly complicated problems. First, what is the set of decisions that have to be made? And second, what is the group of humans that have decision rights? Those rights can be very complicated &#8212; you might have negative control but not positive control. You can prevent an answer but not force one. Some people have influence only if three others also agree.  </span></p><p><strong><span>Ashwin:</span></strong><span> The act of making those dynamics legible changes them. The moment you surface who has influence over what, the political landscape shifts. That&#8217;s the observer effect applied to organizational behavior.</span></p><p><strong><span>James:</span></strong><span> It&#8217;s Heisenberg&#8217;s uncertainty principle as applied to AI. [6]</span></p><p><strong><span>Ashwin:</span></strong><span> And this is why I think the right model is the one you described &#8212; Team Cyborg. AI surfaces insights that inform human judgment; it doesn&#8217;t replace the judgment, because you can never capture information completely enough, and because the act of capturing it creates second-order effects.</span></p><p><strong><span>James:</span></strong><span> Here is why it matters in a very practical sense. Every business case is a trade &#8212; at a big enough scale, it&#8217;s like getting something through Congress. I&#8217;ve been involved in multi-hundred-million-dollar business cases where there&#8217;s always a question: do we leave this country in or out of the consolidation? How aggressive do we estimate the savings here versus there? You&#8217;re always balancing the quality of the business case &#8212; what does the ROI look like? &#8212; against the quality of the political coalition. Smart senior executives do that calculation in their heads without thinking about it. Past a certain point, it gets hard to do in your head. </span></p><p><strong><span>Ashwin:</span></strong><span> Political science has been mapping political dynamics for decades, if not centuries, and the models exist. [7] The challenge is applying them in real time to a specific organization with incomplete data. That&#8217;s where the second-order effects become dangerous &#8212; you don&#8217;t want to make the map so visible that people start playing to the map instead of doing the work.</span></p><p><strong><span>James:</span></strong><span> This is why I&#8217;m on Team Cyborg, not Team Android &#8212; AI is a tool that provides insights to inform human decision-making, but we will never, or not in the foreseeable future, capture information perfectly enough to make instinct and judgment irrelevant. The act of capturing some information creates second-order effects.</span></p><div><hr></div><h4><span>AI Accuracy, Knowledge Work, and What Comes Next</span></h4><div><hr></div><p><strong><span>In this section:</span></strong></p><ul><li><p><span>What &#8220;95% accuracy&#8221; actually means in different professional contexts</span></p></li><li><p><span>The distinction between being wrong at design time versus run time</span></p></li><li><p><span>How AI will reshape the toil and grunt work embedded in knowledge work</span></p></li></ul><div><hr></div><p><strong><span>James:</span></strong><span> Where does this all go? Give us your few-sentence expression of where this issue &#8212; capturing and transacting with ambiguous data &#8212; will be in the next two or three years.</span></p><p><strong><span>Ashwin:</span></strong><span> I think everyone believes AI is going to automate everything. It&#8217;s not going to automate everything &#8212; but I do think people&#8217;s work will change. What I find interesting to say is: if AI is 95% accurate on 100 tasks, you&#8217;ll know the 5 it got wrong. But if AI is working on 10,000 tasks at even a lower accuracy, the net volume of errors grows &#8212; and you have to think very differently about where you put humans in the loop.</span></p><p><strong><span>James:</span></strong><span> I would put it slightly differently. First &#8212; if you&#8217;re running a hedge fund and you&#8217;re right 95% of the time, you&#8217;re a multi-billionaire. If you&#8217;re running an institutional brokerage processing trades and you&#8217;re right 95% of the time, you&#8217;re either bankrupt or in court. So 95% means very different things in very different contexts.</span></p><p><span>Second, it&#8217;s very different to be wrong 5% of the time at design time versus run time. If you&#8217;re wrong 5% of the time at design time, fine: we have quality assurance processes, we can test, we can adjust. But depending on the application, being wrong even 5% of the time at run time can be completely unacceptable.</span></p><p><strong><span>Ashwin:</span></strong><span> And I think what&#8217;s important &#8212; and often under-appreciated &#8212; is how much toil and grunt work is embedded in most knowledge work: writing things down, recording things, organizing things. [8] AI is very good at absorbing that toil. Not eliminating the work, but absorbing the mechanical overhead so that humans can do the judgment-intensive part.</span></p><p><strong><span>T</span></strong><span>he quality of what the agent produces is going to be bound by the quality of the context it&#8217;s given. The response from a large language model is only as good as the prompt, and the context is what constructs the prompt. Getting that context right &#8212; at an organizational level, not just a session level &#8212; is the whole game.</span></p><p><strong><span>James:</span></strong><span> All right, Ashwin &#8212; context is the whole game. Thank you.</span></p><p><strong><span>Ashwin:</span></strong><span> Thank you, James.</span></p><div><hr></div><p><em><span>Organizational context is a brutal problem of structuring information &#8212; decisions that were made but never documented, commitments that live in someone&#8217;s memory, dependencies that exist because of a conversation nobody recorded.  AI may help us capture and understand: who decided what, when, under what assumptions, with whose sign-off. Done well, this will empower human decision-makers exercising judgement rather than replace them.</span></em></p><div><hr></div><h4><strong><span>Footnotes</span></strong></h4><p><span>[1] Alan Kay massively influenced the development of the Mac via his work at Xerox PARC, and later was an Apple Fellow, but was not on the original Mac team. The &#8220;context is worth 80 IQ points&#8221; formulation (the number varies across tellings) is widely attributed to Kay from his OOPSLA keynotes and ACM lectures.</span></p><p><span>[2] </span><a href="https://sentra.app/"><span>Sentra</span></a><span> describes itself as a &#8220;unified memory layer for your company&#8221; &#8212; capturing decisions, commitments, and organizational context into a queryable graph accessible to both humans and AI agents across 200+ business tools. (The 200+ figure is per Sentra&#8217;s own marketing; no independent verification available at time of publication.)</span></p><p><span>[3] Ashwin&#8217;s </span><a href="https://sentra.app/blog/company-brain-why-most-companies-have-data"><span>Company Brain post</span></a><span> argues that most organizations confuse having data with having memory &#8212; data without temporal and semantic structure doesn&#8217;t tell you what the organization actually decided, or why, or when it changed.</span></p><p><span>[4] Ashwin&#8217;s </span><a href="https://sentra.app/blog/geometry-of-forgetting"><span>analysis of how LLMs and biological memory fail the same way</span></a><span> makes the case that both systems apply lossy compression, discarding what they judge unimportant at encoding time. The implication: if precision matters at retrieval, you need a different storage path &#8212; structured external memory, not the compressed context window.</span></p><p><span>[5] The arithmetic illustrating why memory bandwidth, not compute, is the binding constraint for LLM inference at scale &#8212; is worked through in </span><a href="https://www.prosaictimes.com/p/prosaic-times-llm-forget-enterprises"><span>Why LLMs Will Never Remember Your Enterprise</span></a><span>.</span></p><p><span>[6] The intuition that measuring a system changes the system has a long pedigree in social science. The classic example is the </span><a href="https://sk.sagepub.com/reference/the-sage-encyclopedia-of-social-science-research-methods/n207.xml"><span>Hawthorne effect</span></a><span>: people often change their behavior simply because they know they are being observed. The analogy to Heisenberg&#8217;s uncertainty principle is metaphorical rather than literal &#8212; in physics, the principle describes fundamental limits on measuring physical quantities; in organizations, the comparable insight is that observation itself can alter the behavior being measured. Management scholars have recently formalized this analogy: </span><a href="https://journals.aom.org/doi/10.5465/amr.2022.0051"><span>Shelef, Wuebker &amp; Barney</span></a><span> (</span><em><span>Academy of Management Review</span></em><span>, 2024) argue that business experiments do more than reveal information &#8212; they can change the value of the underlying idea by influencing competitors, customers, and other stakeholders. A </span><a href="https://journals.aom.org/doi/10.5465/amr.2024.0134"><span>companion commentary</span></a><span> in the same journal explores both the strengths and limits of the Heisenberg metaphor.</span></p><p><span>[7] The academic research connected to this point: Gailmard &amp; Patty&#8217;s survey of </span><a href="https://www.annualreviews.org/content/journals/10.1146/annurev-polisci-031710-103314?utm_source=chatgpt.com"><span>formal models of bureaucracy</span></a><span> &#8212; covering hierarchy, delegation, and information asymmetry across decades of political science literature &#8212; establishes the toolkit Ashwin is referencing. A foundational result (Crawford &amp; Sobel 1982) demonstrates that complete information-sharing between agents with divergent interests is mathematically impossible; the degree of distortion is a function of how far apart their preferences are. </span><em><span>Annual Review of Political Science</span></em><span> 15 (2012): 353&#8211;77.</span></p><p><span>[8] Knowledge work contains substantial coordination and administrative overhead. </span><a href="https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/rethinking-knowledge-work-a-strategic-approach"><span>McKinsey estimates</span></a><span> that knowledge workers spend more than one-quarter of their time searching for information rather than applying their expertise. </span><a href="https://hbr.org/2013/09/make-your-knowledge-workers-more-productive"><span>Cohen &amp; Birkinshaw</span></a><span> argue in </span><em><span>Harvard Business Review</span></em><span> that knowledge workers could reclaim roughly one day per week by eliminating, delegating, or outsourcing low-value activities.</span></p><p><span>[9] C.J. Chivers covers the </span><a href="https://www.esquire.com/news-politics/a25677/ak-47-history-1110/"><span>history and design philosophy of the AK-47</span></a><span> in depth &#8212; the rifle was deliberately engineered for soldiers with minimal training and limited mechanical aptitude. Reliability under adverse conditions, not precision, was the design priority. Helpful </span><a href="https://www.youtube.com/watch?v=CmYPaN8d4xQ"><span>comparison to the M-16</span></a><span> here.</span></p>]]></content:encoded></item><item><title><![CDATA[Legacy code is a map of your business]]></title><description><![CDATA[Rhino.ai CTO Harrison Touati on why enterprise modernization fails, where AI actually helps, and what becomes scarce when code is cheap]]></description><link>https://www.prosaictimes.com/p/legacy-code-is-a-map-of-your-business</link><guid isPermaLink="false">https://www.prosaictimes.com/p/legacy-code-is-a-map-of-your-business</guid><dc:creator><![CDATA[James Kaplan]]></dc:creator><pubDate>Sun, 05 Jul 2026 21:00:22 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/205132402/4d32c91fbae616cc264be5db139b851f.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p><span>How many of us have heard an intern or a new joiner say: &#8220;This doesn&#8217;t work the way they said it would in school.&#8221; Sadly, business schools don&#8217;t teach students just how messy and disorganized business is &#8212; how entropic it is.</span></p><p><span>Processes are complex. They depend on thousands of interconnected rules for applying discounts or approving requests. Rules change based on business need and regulatory requirements. And there are exceptions &#8212; and exceptions to exceptions: send the invoice to this executive rather than that one in a local market; apply an off-book discount that someone agreed to years ago. Data is opaque. Information is inaccessible because it lives in email chains or spiral notebooks. It is incomplete, disconnected, and out of date.</span></p><p><span>Why do enterprise systems cost so much and perform so poorly? Because business is entropic. Why is system modernization so hard? Because legacy code reflects years of patches and hacks accumulated to capture the weird idiosyncrasies of our business processes. Sometimes this produces the dreaded </span><a href="https://lawsofsoftwareengineering.com/laws/second-system-effect/?utm_source=chatgpt.com"><span>second-system problem</span></a><span>: a replacement system that degrades productivity because it fails to replicate some of the never-written-down, barely-understood functionality that made the first system work for users.</span></p><p><span>We will all spend considerable time in the coming years using GenAI tooling to understand legacy code. Where does it capture important process idiosyncrasies? Where does it assume an obsolete process that can be reimagined? Where does it contain years of accumulated, useless crud?</span></p><p><span>I had the chance to talk with Harrison Touati, CTO of </span><a href="https://www.rhino.ai/"><span>Rhino AI</span></a><span>, and discuss how he thinks about using GenAI tooling to interrogate legacy code &#8212; and what that means for modernizing systems and improving operational productivity. As always, Prosaic Times never endorses and company or technology, but we often find it interesting to hear from builders themselves! Here is what I took away.</span></p><ol><li><p><strong><span>Legacy systems are not technical artifacts &#8212; they are business records.</span></strong><span> A company&#8217;s processes contain more information than any one person can hold. Code is the accumulated record of how those processes evolved &#8212; including rules nobody wrote down, constraints nobody remembers creating, and idiosyncrasies that may or may not still matter. Modernization fails not because developers are slow but because nobody can comprehend the whole thing.</span></p></li><li><p><strong><span>The right comparison is not AI versus deterministic code.</span></strong><span> Human engineers are already a stochastic process. The real question is which messy stochastic process produces cheaper outputs with a lower defect rate. Once you frame it that way, the trajectory becomes clearer.</span></p></li><li><p><strong><span>Where you process entropy matters as much as whether you do.</span></strong><span> Enterprises can deploy AI agents at runtime to handle messy decisions as they arise, or at design time to clarify the rules and encode them in software. Design-time is almost always preferable &#8212; it lets you apply 30 years of software QA to the output. Most organizations are currently doing it backwards.</span></p></li><li><p><strong><span>When code becomes cheap, what remains scarce is structure.</span></strong><span> Domain knowledge commoditizes. What doesn&#8217;t: the structured understanding of how a specific business actually operates &#8212; its ontology. The companies that will win are those that own the vertical model, not just the development capacity.</span></p></li></ol><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.prosaictimes.com/p/legacy-code-is-a-map-of-your-business?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Is this interesting? Share it with just one friend!</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.prosaictimes.com/p/legacy-code-is-a-map-of-your-business?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.prosaictimes.com/p/legacy-code-is-a-map-of-your-business?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><p><strong><span>James Kaplan:</span></strong><span> Hi there, this is James Kaplan, joining from Rhode Island for another Prosaic Times video podcast. We have Harrison Touati, CTO of Rhino.ai, with us this morning. Harrison, welcome.</span></p><p><strong><span>Harrison Touati:</span></strong><span> Hey, great to be here.</span></p><p><strong><span>James:</span></strong><span> Why don&#8217;t you tell us a little bit about your journey to Rhino AI?</span></p><p><strong><span>Harrison:</span></strong><span> I&#8217;ve always been interested. I remember even back in college, natural language, NLP.</span></p><p><span>Data science, stuff like that. And my early career was a bit of a pivot from there, but it all came back together when I worked at some low-code SaaS companies. I did a lot of what I learned was, wow, a lot of these processes are really painful and miserable. And the thought process was, okay, can we use AI to make understanding legacy systems and to make modernization a lot less painful?</span></p><p><span>And that&#8217;s what inspired the creation of the technology and the company and how I got to where I am currently.</span></p><h4><span>1. The Low-Code Mirage: legacy systems are business records</span></h4><ul><li><p><em><span>Low-code promised to eliminate developer dependency; in practice it reinvented programming complexity in proprietary form.</span></em></p></li><li><p><em><span>The hard part was never syntax &#8212; it was understanding the problem.</span></em></p></li></ul><p><strong><span>James:</span></strong><span> Many people were convinced that low-code, no-code was going to take over the world. It didn&#8217;t. What was the promise, and what caused the gap?</span></p><p><strong><span>Harrison:</span></strong><span> Low-code, no-code products &#8212; the promise was that business analysts could do the development. You wouldn&#8217;t need developers. And that never really manifested for two reasons.</span></p><p><span>One is a failure to actually be sufficiently no and low-code in the first place. And the other is that even if you were sufficiently such, you would still need developers anyway, because the hard part is understanding the problems. If you look at low-code products in particular, they end up reinventing the wheel. At first they&#8217;ll be like, oh, we have this really easy way to solve some problems.</span></p><div class="pullquote"><p><em>You</em> <em>want</em> <em>to</em> <em>do</em> <em>as</em> <em>much</em> <em>at</em> <em>build</em> <em>time</em> <em>as</em> <em>possible</em> <em>because</em> <em>it&#8217;s</em> <em>cheaper,</em> <em>it&#8217;s</em> <em>faster.</em> <em>Runtime</em> <em>is</em> <em>what</em> <em>you</em> <em>want</em> <em>to</em> <em>do</em> <em>the</em> <em>absolute</em> <em>bare</em> <em>minimum</em> <em>&#8212; exception</em> <em>cases,</em> <em>extremely</em> <em>fuzzy</em> <em>amounts</em> <em>of</em> <em>judgment.</em> <em>That&#8217;s</em> <em>the</em> <em>only</em> <em>time</em> <em>you&#8217;re</em> <em>going</em> <em>to</em> <em>want</em> <em>to</em> <em>really</em> <em>do</em> <em>runtime.</em></p></div><p><span>But then they&#8217;ll ask: what if I need to iterate that across an array of issues? And all of a sudden they&#8217;re rebuilding for loops in their own way of doing that. You end up sometimes in a worse situation where not only are you not low-code, you&#8217;re basically in some invented programming paradigm that only your staff knows. And that sometimes makes things even worse.</span></p><p><span>So what you end up seeing is for the easy use cases, you do get savings. And then for the complex use cases, sometimes you&#8217;re like, man, it would have been easier to just run a Python script for this. The other thing is that the idea that if development was easy, that you wouldn&#8217;t necessarily want people with a developer mindset is not really true. A lot of business problems are hard and complicated and require a lot of thinking to solve.</span></p><p><span>If you&#8217;re going through and doing really complex ERP implementations and the rules are really hard, you need someone who can sit down and logically think through things. And so you end up just having developers working with weird proprietary tools, and I think that probably hurt the adoption of low-code.</span></p><p><strong><span>James:</span></strong><span> It reminds me of the 1990s when people started coming out with visual development languages. I&#8217;m dating myself, and I remember people showing them to me and &#8212; great. So instead of typing three lines of code, I have to click and drag 40 things from a palette onto some sort of screen and then do a bunch more mouse clicks to connect those things with arrows and what have you. Why wouldn&#8217;t I just write the four lines of code or the 10 lines of code? Once you get past remembering some very simple syntax, it doesn&#8217;t buy you anything.</span></p><p><strong><span>Harrison:</span></strong><span> Especially when you start getting into complex arithmetic calculations &#8212; you&#8217;re calculating interest rates or something like that &#8212; you end up back having to enter Excel-like formulas and then you end up with a programming language anyway. That&#8217;s the worst part &#8212; you drag and drop the boxes, you draw the arrows, you map the variables in the dropdowns, and then you end up still running some monstrosity of an Excel-like expression to close it all together and you&#8217;re like, this could have just been five lines.</span></p><p><strong><span>James:</span></strong><span> Exactly. And in a programming language, you can just call up all the logic and look at it. Instead of having to click on 10 different things to see where the logic might be buried &#8212; which gets to an important underlying topic: the reason systems have been challenging is that there&#8217;s a lot of entropy, a lot of variation and uncertainty in business processes, and none of the low-code, no-code products either in the 1990s or more recently had any effective way of dealing with that.</span></p><p><strong><span>Harrison:</span></strong><span> The complexity &#8212; when you think about most businesses, there are absolutely use cases, like you buy an ITSM system for ticket management, and okay, this really does just out of the box solve a lot of my problems, but mostly because ticket management is fairly consistent across many companies.</span></p><p><span>And businesses very rarely are building greenfield new applications. Even when they think they are, they run today and therefore whatever problem they need to solve, they have some way of solving it today, even if it&#8217;s not good. And that problem is often constrained by regulations, by economic realities, by human processes that nobody&#8217;s even aware of.</span></p><p><span>Whenever you try to automate these things with code &#8212; entropy is a really good framework for thinking about it. These are very high entropy, confusing, often poorly thought out processes, often emergent. They&#8217;re not an artifact of design. They evolved in the wild and you have to be able to capture these and it can be just so complex. And then what you end up having to do is taking that ITSM or whatever CRM ERP software and smashing it into some sort of monstrosity workflow engine to handle really complex use cases. It doesn&#8217;t work out very well usually.</span></p><p><strong><span>James:</span></strong><span> And often the failure is in the understanding of the business. How does this actually work? Your point about emergent processes is a very good one &#8212; because we sit there and say, here, use the SaaS product and use the out-of-the-box workflow. That&#8217;s interesting because we don&#8217;t really know whether the emergent idiosyncrasy is accidental &#8212; just the way someone had to design it at some point &#8212; or, to use the example of </span><a href="https://en.wikipedia.org/wiki/Chesterton%27s_fence"><span>Chesterton&#8217;s fence</span></a><span>[5], did that idiosyncrasy evolve for an important business reason?</span></p><p><span>Was there some regulatory thing someplace or some set of customer requirements that nobody bothered to write down?</span></p><p><strong><span>Harrison:</span></strong><span> That is the hard part. When modernization projects fail &#8212; and this is something I learned early in my career &#8212; it&#8217;s very rarely due to developers not being fast or smart enough. It&#8217;s almost always due to everyone &#8212; the client, the developers, the project managers &#8212; it&#8217;s not a one-person thing or one-role thing. It&#8217;s everybody not really understanding how the business operates.</span></p><p><span>And it&#8217;s not their fault. The business is in some sense an emergent super intelligence &#8212; more information than any one human mind can hold. When the individual human tries to comprehend it all, they struggle.</span></p><p><span>A lot of the idiosyncrasies are created for very good reasons, but sometimes those reasons don&#8217;t even exist anymore. They&#8217;re like vestigial organs of the enterprise.</span></p><p><strong><span>James:</span></strong><span> But you don&#8217;t know which ones exist and which don&#8217;t.</span></p><p><strong><span>Harrison:</span></strong><span> You don&#8217;t know that out of the box. That&#8217;s the AI use case &#8212; and why, from a career perspective, I thought it was worth pursuing. Can we apply some degree of limited super intelligence to help augment that process?</span></p><p><span>Can we pull in as much information from as many people as possible &#8212; we&#8217;re not going to understand everything, but can we at least understand more than the average person on the project? And if we can even a little bit lower the failure rate of projects from that cause, that becomes very worth it.</span></p><h4><span>2. Interrogating legacy systems: ask how to use AI, not whether</span></h4><ul><li><p><em><span>Modernization projects fail not from slow developers but from everyone &#8212; client, dev, PM &#8212; not understanding how the business actually operates.</span></em></p></li><li><p><em><span>Systems are digital manifestations of business processes; what looks like a technical problem is almost always also a business problem.</span></em></p></li><li><p><em><span>Reconstructing process from code, config, logs, and documents is the triangulation problem at the heart of legacy modernization.</span></em></p></li></ul><p><strong><span>James:</span></strong><span> Okay. So tell us about the creation of Rhino AI and tell us how the technology works.</span></p><p><strong><span>Harrison:</span></strong><span> The creation was born out of the pain and suffering a lot of the other co-founders and original employees and myself had &#8212; modernization projects are miserable. They require so much specific information.</span></p><p><strong><span>James:</span></strong><span> And just one definition &#8212; when you say modernization project, can you just define that because that could mean a few different things? Just scope it for us.</span></p><p><strong><span>Harrison:</span></strong><span> So what we normally mean is the business has some existing capability, normally already implemented in some legacy tech stack. And legacy is in the eye of the beholder very often. Of course.</span></p><p><strong><span>James:</span></strong><span> Yeah. I knew I was in trouble when I started hearing about legacy cloud. And in a couple of years we&#8217;re probably about three months away from people starting to talk about legacy AI.</span></p><p><strong><span>Harrison:</span></strong><span> Oh, definitely. And part of that&#8217;s due to &#8212; the analysts have to make new buzzwords. I don&#8217;t know how many analysts are listening to this, so I&#8217;m going to maybe keep it there.</span></p><p><span>So that was the business problem &#8212; born out of the pain of those modernization projects, of taking these legacy software systems and having to rebuild them to reap modern benefits: modern security, more maintainable, easier to add new features, better UX, better performance, lower cost.</span></p><p><strong><span>James:</span></strong><span> And sometimes a modernization project can be largely technical in nature &#8212; we&#8217;re running on outdated code. Sometimes it can be business and technical in nature &#8212; it&#8217;s not integrated enough, it doesn&#8217;t have the type of capabilities that business users are demanding. Fair?</span></p><p><strong><span>Harrison:</span></strong><span> Yes, you&#8217;ll see both of those. And often when people think they have the former, it really is the latter. As you dig into these, the system is like a digital physical manifestation of the business&#8217;s job to be done and their processes. As you dig into these things, you&#8217;ll realize that people don&#8217;t actually like them and they don&#8217;t understand them.</span></p><p><span>You&#8217;ll often find &#8212; they&#8217;ll be like, hey wait, that&#8217;s how we do approval? I didn&#8217;t even know how approval logic worked. We should definitely change that now that we know how that works.</span></p><p><strong><span>James:</span></strong><span> Years ago, a wise old architect told me a system is just an automated process &#8212; which I think is almost true, but not quite true. A system is automated parts of a process, because often you&#8217;ll see pre-processing and post-processing. We&#8217;ve all seen the spreadsheet gymnastics required sometimes to enter data into a quarterly close, as well as the spreadsheet gymnastics on the far end of some sort of system output in order to put the data into a format that people can use or understand.</span></p><p><strong><span>Harrison:</span></strong><span> It&#8217;s going to depend on the system. Some systems really do capture &#8212; and people get into, what is a process? Sometimes a process is a purely technical or automated job.</span></p><p><span>But usually when people talk about processes, it&#8217;s with human actors. And therefore, almost by definition, the system is only part of the process because it is not the human actors &#8212; it might tell someone that an approval has to happen, but it is not the approver.</span></p><p><strong><span>James:</span></strong><span> In banking you have many processes that are truly &#8212; clearing and settlement, in financial services broadly, we now have many transactions that are truly no-touch.</span></p><p><strong><span>Harrison:</span></strong><span> I agree. And with AI agents, you&#8217;re seeing some processes that people traditionally thought couldn&#8217;t be done that way &#8212; people are starting to say, well, maybe some of these approvals really can just be handled by an agent. Where that goes is yet to be determined. But I do suspect we will see more and more people try to move processes to be like that.</span></p><p><span>And in many cases, they&#8217;ll succeed. In some cases, they&#8217;ll probably fail spectacularly.</span></p><p><strong><span>James:</span></strong><span> In banking, if you look at highly structured products like equities, those are incredibly automated. On the other hand, exotic derivatives, much less automated because you could argue there&#8217;s just a lot more entropy associated with the product.</span></p><p><strong><span>Harrison:</span></strong><span> It&#8217;s not just the entropy. It&#8217;s probably also how many people are doing it, because there&#8217;s always that cost tradeoff &#8212; is it even worth automating?</span></p><p><strong><span>James:</span></strong><span> Equities or credit card transactions are a great example of processes with a lot of clarity, not an unreasonable amount of variation and very, very high scale.</span></p><p><strong><span>Harrison:</span></strong><span> And what&#8217;s probably changed due to AI is that the ability to automate things that traditionally had a lot of unstructured data and lower frequency is going to go up &#8212; and it&#8217;s probably already gone up. So I think we&#8217;re going to see a lot of attempts and probably a lot of successes in automating those things.</span></p><div class="pullquote"><p>The structure is the interface, in a sense. It&#8217;s the method of communication between parties. Even humans need structure when they talk to each other &#8212; that&#8217;s why they make forms.</p></div><p><span>People often compare AI-based solutions to current processes as determinism versus stochastic processes. That&#8217;s probably not a good comparison. A piece of code might be very deterministic, but AI can write code. So the question really becomes who&#8217;s generating the code.</span></p><p><span>The humans who write the code are often stochastic &#8212; they&#8217;re messy. Code is filled with bugs. That&#8217;s why there are implementation budgets to go through and do all this maintenance, fix all these bugs. As you zoom out to the 20,000-foot view, everything&#8217;s a messy stochastic process.</span></p><p><span>It becomes which messy stochastic process is going to be cheaper and have a lower defect rate. There&#8217;s a nice chart I like where it&#8217;s the performance of the best chess engine and the win rate of humans over chess. The win rate of the human grandmasters at 100%. And then one day you get </span><a href="https://en.wikipedia.org/wiki/Deep_Blue_(chess_computer)"><span>Deep Blue</span></a><span> and all of a sudden the human rate is zero.[2] I think you&#8217;re going to start seeing that in more and more industries &#8212; sure, the AI might mess up, it might hallucinate, it might write bad code with a bug.</span></p><p><span>But the goal was never to write zero bugs. Human engineers can supply plenty of bugs. You only have to have less costly bugs on average than the human. And as we see the models improve, that world is going to come.</span></p><h4><span>3. Design time vs. runtime: where you process entropy matters</span></h4><ul><li><p><em><span>Processing entropy at design time beats runtime: you can apply 30 years of software QA to the output. Most organizations are currently doing it backwards.</span></em></p></li><li><p><em><span>LLMs are poor at saying &#8220;I don&#8217;t know&#8221; &#8212; the truly hard edge cases may be better handled by humans, at least until the models improve on calibration.</span></em></p></li><li><p><em><span>As code gets cheaper, exception cases shrink. The agent-vs-human decision for the residual tail matters less than it appears.</span></em></p></li></ul><p><strong><span>James:</span></strong><span> I think about it slightly differently, which is: where do you want to turn the stochastic world into something less stochastic? Where do you want to process the entropy? One of the big decisions will be, do we want to do it at design time or runtime?</span></p><p><span>If you have a whole messy set of rules that are not well documented, you could either build an agent to apply those rules at runtime, or you could develop software using agents to clarify those rules and apply them in a more deterministic manner. The advantage of addressing stochastic processes at design time rather than runtime is that then we can apply everything we&#8217;ve learned over the past 30 years about software quality assurance to the output.</span></p><p><strong><span>Harrison:</span></strong><span> That&#8217;s a very good point. It&#8217;s design time. And when people think about agents still, they&#8217;re thinking very much runtime agents &#8212; oh, we can have some agent do automatic approvals and stuff like that. But I think about &#8212; there&#8217;s an example of when the internet was getting big and people talked about the information superhighway.</span></p><p><span>If you remember that, I suspect I&#8217;m a little bit older than you are.</span></p><p><strong><span>James:</span></strong><span> Yes, I remember the information superhighway. In college, I wanted to take the </span><a href="https://www.browndailyherald.com/"><span>Brown Daily Herald</span></a><span> and put it on the internet. I found out I couldn&#8217;t because at that point, advertising was still not allowed on the internet. They would disconnect you.</span></p><p><strong><span>Harrison:</span></strong><span> Man. Wow.</span></p><p><strong><span>James:</span></strong><span> Yeah. So before 1995, there was no advertising because the US government agency that managed the internet did not allow you to advertise on the internet.[1]</span></p><p><strong><span>Harrison:</span></strong><span> I didn&#8217;t know. That&#8217;s why the internet took off in the late 1990s &#8212; because they allowed advertising on it. What I think about with the superhighway is everyone &#8212; there were people who were like, oh, we have the internet, but when are we getting the superhighway? And it&#8217;s like, well, you have the superhighway. It&#8217;s the internet, right?</span></p><p><span>And I think about that with agents now where you still have folks being like, how are we going to replace all these processes with agents? And it&#8217;s like, you did &#8212; it&#8217;s called Claude Code. If you built GPT-12 and GPT-12 is like Ultron and it can do anything &#8212; if you&#8217;re like, GPT-12, go solve ITSM &#8212; it&#8217;s not going to manually review a million tickets. It&#8217;s going to write code to do 99% of it.</span></p><p><span>You want to do as much at build time as possible because it&#8217;s cheaper, it&#8217;s faster, the AIs are probably better at coding than they are at anything else. Runtime is what you want to do the absolute bare minimum &#8212; exception cases, extremely fuzzy amounts of judgment, things that require a huge amount of natural language processing. That&#8217;s the only time you&#8217;re going to want to really do runtime. Then you might ask, if it&#8217;s that big an exception, it might be a small enough fraction that you may just want to give it to a human.</span></p><p><strong><span>Harrison:</span></strong><span> You could just give it to a human. And that&#8217;s going to come back to what I was saying earlier &#8212; will the human on average make fewer bad calls? How often will humans outperform the machines in judgment? As time goes on, I think you&#8217;re going to see the machine judgment just continue to improve.</span></p><p><strong><span>James:</span></strong><span> Let me offer a counter perspective. Large language models or GenAI is phenomenal at certain things &#8212; reading large amounts of text. It&#8217;s really bad at saying &#8220;I don&#8217;t know.&#8221;[3]</span></p><p><strong><span>Harrison:</span></strong><span> It is, yes.</span></p><p><strong><span>James:</span></strong><span> And the truly big edge cases, where there isn&#8217;t a dataset &#8212; we&#8217;ve never seen this edge case before. A lot of what you want from the human is less, oh, let me make a decision &#8212; can I even make this decision, or do I have to go ask these six other people?</span></p><p><strong><span>Harrison:</span></strong><span> That&#8217;s a very fair point. And historically the LLMs have really struggled with that. They&#8217;re trained to maximize some objective function during reinforcement learning, and that objective function is answering math problems correctly, so it&#8217;s almost always valuable to guess. I&#8217;ve seen some interesting research about penalizing guessing.</span></p><p><span>There are many possible futures &#8212; there&#8217;s a world where that stays the case for decades.</span></p><p><strong><span>James:</span></strong><span> From an efficiency standpoint, if you&#8217;re down to half a percent of all the transactions, whether you send those to an agent or send those to a human may not make that much of a difference.[4]</span></p><p><strong><span>Harrison:</span></strong><span> It might not matter. And it might not be a dramatic amount of judgment either way &#8212; especially because in practice you want to get as few of those exception cases as possible. And often a huge portion of exceptions are not due to the fact that this couldn&#8217;t be done deterministically at build time, but because code was just expensive. Now that code is...</span></p><p><strong><span>James:</span></strong><span> Code was expensive, yes. Code is now cheaper.</span></p><p><strong><span>Harrison:</span></strong><span> And so as code becomes cheaper and cheaper, the exception cases are going to start declining.</span></p><p><strong><span>James:</span></strong><span> The way I think about it is we&#8217;ve changed the operating leverage dynamics for automation.</span></p><h4><strong><span>4. What Becomes Scarce: When Code Is Cheap, Structure Is Scarce</span></strong></h4><ul><li><p><em><span>When code is cheap, the traditional SaaS moat &#8212; &#8220;we understand the problem and we&#8217;ve solved it&#8221; &#8212; erodes. </span></em></p></li><li><p><em><span>Domain knowledge commoditizes; proprietary structure doesn&#8217;t.</span></em></p></li><li><p><em><span>What remains scarce: hardware and compute, unique data nobody else can access, rare human judgment that outperforms machines, and the ontology of a vertical.</span></em></p></li><li><p><em><span>Pure developer-army businesses face structural disruption. In periods of rapid change, the answer is not to wait.</span></em></p></li></ul><p><strong><span>Harrison:</span></strong><span> Companies in the past, especially on the software side, their value proposition was the software itself and domain knowledge &#8212; those would be the two things, especially in the SaaS space. We understand how this problem is supposed to be solved and we&#8217;ve solved it.</span></p><p><span>The latter is going to be not that important. What becomes scarce in a world where I can just give a very fuzzy spec and it just gets perfectly coded by a system that&#8217;s worked with millions of people and can really infer intent quite well? In that world, what becomes scarce?</span></p><p><span>Obviously hardware, chips, data, electric power &#8212; all of those things are scarce. And there&#8217;s also data that nobody else has access to &#8212; information that nobody else can see. That&#8217;s where software companies and companies in general are probably going to have to start consolidating around. You&#8217;re either going to need to double down on whatever rare human skills remain &#8212; good judgment that perhaps exceeds the LLMs.</span></p><p><span>Or hardware, physical resources, or unique data access. But there&#8217;s a whole world of companies that are just pure labor &#8212; our value proposition is that we have an army of developers,  and we&#8217;ll go in for hire and fix your problems. That&#8217;s going to be dramatically disrupted.</span></p><p><strong><span>James:</span></strong><span> Two thoughts for you. One is to your point about the exceptions &#8212; there are two reasons I think exceptions don&#8217;t get processed in an automated fashion. The first, which you mentioned, is it&#8217;s just expensive to write all the business rules. The second is &#8212; and we have to remember that business rules need data to operate on &#8212; the data required may be in a spreadsheet, in an email someplace, unstructured data that we haven&#8217;t been able to transact on.</span></p><p><span>Now we can, because in addition to writing code agentically, we can ingest data agentically. And then which leads me to believe there&#8217;s maybe one additional source of competitive advantage: structure. Because I think evidence indicates that models are much less likely to hallucinate when given a structure &#8212; which is why they write code better, they&#8217;re very good at writing code because it&#8217;s a structured output. When you don&#8217;t give them that type of structure, they&#8217;re more likely to have problems.</span></p><p><span>And then if you create the structure via the process of compounding, you can over time generate proprietary data. So I think getting the ontology right will be incredibly important and will be a source of competition going forward.</span></p><p><strong><span>Harrison:</span></strong><span> I agree. The structure is the interface, in a sense. It&#8217;s the method of communication between parties. Even humans need structure when they talk to each other &#8212; that&#8217;s why they make forms.</span></p><p><strong><span>James:</span></strong><span> Forms as ontology, I would suggest.</span></p><p><strong><span>Harrison:</span></strong><span> And to me, when I think about ontology &#8212; I use that word a lot when we&#8217;re talking about our own software offering. It gets confusing sometimes because people mean different things. Some people mean the data ontology.</span></p><p><span>We often operate in a very process-centric world &#8212; what are the sequences of activities, business rules. But at a high level: what is the structure of your business? People call it use context now a lot.</span></p><p><strong><span>Harrison:</span></strong><span> Like context engines. Buzzwords. But that ability to say we have a way of working with structure around it &#8212; structure is the good word &#8212; which includes things like the ontology of your data, the understanding of your processes, the context through which decisions need to be made, rules can be done deterministically. It becomes a way of operating as an enterprise. And that becomes a model that can be monetized and a competitive edge.</span></p><div class="pullquote"><p><em>A lot of the idiosyncrasies are created for very good reasons, but sometimes those reasons don&#8217;t even exist anymore. They&#8217;re like vestigial organs of nopethe enterprise</em></p></div><p><strong><span>Harrison:</span></strong><span> I think also it ties very closely to just scarce state in general. Because if you think about it &#8212; and I think scarce state still becomes critical for that &#8212; the reason is: how do you know your ontology is good? The only way you know it is good is to be able to use some judgment, but you probably want to have some evidence and measure it. And therefore, if you&#8217;re in a specific vertical, you&#8217;re a company dealing with that vertical, and you have access to lots of metadata, metrics, and in some cases raw data, you can start to learn what interfaces work, what didn&#8217;t work, what processes work.</span></p><p><span>And then you can build &#8212; could turn that not just into aggregates, but into ways of working. And I think that&#8217;s what we&#8217;re going to see companies start moving more and more towards and away from. Some of them are going to move sooner, some slower, many will die. Companies always die.</span></p><p><span>But I do think that&#8217;s what we&#8217;ll see.</span></p><p><strong><span>Harrison:</span></strong><span> In the long term, even that activity is a job that I expect will eventually be automated. You will literally just have machines learning about how to build ways of working for machines to solve business problems, probably solving problems for other machines with their ways of working.</span></p><p><strong><span>James:</span></strong><span> I&#8217;ll avoid the obligatory Skynet joke here.</span></p><p><strong><span>Harrison:</span></strong><span> We already brought up Ultron.</span></p><p><strong><span>James:</span></strong><span> Different generations.</span></p><p><strong><span>Harrison:</span></strong><span> I was sitting with someone the other day and talking about AI, and they were like, the perception in society &#8212; not unjustifiably &#8212; people are, there&#8217;s some fear because even if there&#8217;s only a 25% chance it ends up like that, a 15% chance. That&#8217;s a big deal.</span></p><p><strong><span>James:</span></strong><span> So tell us &#8212; you guys ingest lots of code and other documents in order to identify a baseline and then identify and propose a future state business process? Is that correct?</span></p><p><strong><span>Harrison:</span></strong><span> We pull from a couple of sources &#8212; code, obviously, documents. We also focus a lot on SaaS and COTS, and that&#8217;s a big area for us. People largely ignore that because one, LLMs aren&#8217;t well trained on it, and two, a lot of people just don&#8217;t know about that space.</span></p><p><span>So we do a lot of SaaS and COTS configurations. And then also some runtime information as well &#8212; log analysis is supplemental &#8212; we&#8217;ll look into it but it&#8217;s not our focus. And the goal is to pull out data structure, business rules, process as the orchestrating engine of those things, and also what the current user experience looks like. And then to be able to work with the human users &#8212; if they have desired target end states, figure out to honor those or propose new end states, updated processes, areas of redundancy.</span></p><p><span>We&#8217;re working with companies where company A bought company B, and now we have two of everything. So where can we do process consolidation and use case consolidation? And because we&#8217;re focusing both at the technical level &#8212; mapping out every technical component, method, class, program, etc. &#8212; and then process, use case, actor, core data object, etc. &#8212; we can start to say, if you want to consolidate these processes, then that&#8217;s going to reach down through these three different systems and these different sub-components. And your roadmap to modernization is going to need to take these chunks and convert them into these chunks so that you can change this process.</span></p><p><strong><span>James:</span></strong><span> I like the fact that you&#8217;re pointing out you can derive the business actions from the tech &#8212; you can derive a set of business actions or business processes from the technical code.</span></p><p><strong><span>Harrison:</span></strong><span> Yes, absolutely. In fact, I think that&#8217;s one of the best places to get it.</span></p><p><strong><span>James:</span></strong><span> There are some companies out there seeking to derive information about business processes from code, which I think is great. There are other companies seeking to derive information about business processes by instrumenting user screens and seeing what users do. How do you think about that &#8212; there&#8217;s some part of me that says it has to be both, in the sense that there is always preprocessing and there are things that happen under the covers that you can&#8217;t see from the screen.</span></p><p><strong><span>Harrison:</span></strong><span> You can&#8217;t do it just through screen analysis. There are many lenses, and different viewpoints give you access to different data. If you really want to know exactly how a user is clicking and which screen they go to in which order, there is valuable process you can infer from that.</span></p><p><span>Likewise, if you&#8217;re looking at pure log files, there are things you can learn. But those are going to help you more if your goal is to automate the human. Think about the RPA world, really automating the system processes &#8212; they were trying to replace human swivel-chairing and human activities. This is a really important decision you have to make when you&#8217;re automating: are you trying to replace human labor hours that are using systems, or are you trying to replace systems themselves?</span></p><p><span>And if you want to replace a system, then you have to look at the parts of the process the system does. And those system processes are literally one-to-one defined by the code that executes.</span></p><p><strong><span>James:</span></strong><span> I&#8217;d come at it differently &#8212; I want a better process end to end.</span></p><p><strong><span>Harrison:</span></strong><span> Fair.</span></p><p><strong><span>James:</span></strong><span> I presume some of the processes are handled by Excel gymnasts who are pre-processing and post-processing data. So therefore, if I really wanted to understand the processes just today and get to hopefully a zero-touch process in the future, if appropriate &#8212; I&#8217;d need to both do exactly what you&#8217;re describing in terms of interrogating the code and other data sets and artifacts, and at the same time instrumenting the screen.</span></p><p><strong><span>Harrison:</span></strong><span> You can probably get away with skipping some of the screen instrumentation. But at a high level, some indication of user input or user activity is important. When we&#8217;re doing that type of analysis, we&#8217;ll take supplementary information &#8212; logs with information about who clicked what in what order, SOP documents, user forms. The companies we work with, we do ingest from their spreadsheets. And all of that can start to be correlated and consolidated together into that overall process. Usually as long as you get n minus one of the sources, you&#8217;ll be able to infer the last one &#8212; there are only so many possible sequences a user can click through these forms.</span></p><p><span>I see the log files, I see the spreadsheet they&#8217;re filling out, I see how the code&#8217;s working, I see the documentation they&#8217;ve written about it. You can start to infer a lot from there. Pure screen scraping also has its use &#8212; traditionally from our side, we&#8217;ll just look at the outputs of those. If they have some other screen scraping technology and they&#8217;re like, here&#8217;s the dump of that, we&#8217;ll just ingest the logs of it.</span></p><p><span>As opposed to trying to build our own &#8212; not worth it.</span></p><p><strong><span>James:</span></strong><span> You can ingest data from multiple sources, and it&#8217;s a game of triangulation.</span></p><p><strong><span>Harrison:</span></strong><span> Exactly.</span></p><p><strong><span>James:</span></strong><span> What are the markers of a process that you think are most ripe for reinvention? I&#8217;m running a bank, a consumer package company, a pharmaceutical company &#8212; how should I think about where to apply this first versus later?</span></p><p><strong><span>Harrison:</span></strong><span> It depends on your business problem. What&#8217;s the issue you&#8217;re having? Is it wanting things faster, costs lower?</span></p><p><span>Which of those really matter to you? If you have a company with a legacy SaaS license that&#8217;s enormously expensive and killing them, then the answer is: literally any important process in there that you care about, you should get out, because you&#8217;re paying licenses for those and you need to shed those licenses.</span></p><p><span>Now if it&#8217;s a company on a bunch of old mainframe stuff, where perhaps they&#8217;re not paying expensive SaaS licenses &#8212; then it becomes, what are you trying to get from modernizing here? Is it you want a more maintainable, updateable process? It&#8217;s often not performance, because those systems usually perform pretty well. It becomes more about process transformation.</span></p><p><span>If they&#8217;re on the mainframe, it&#8217;s very complex for them to maintain and modify those processes, and therefore as a business they&#8217;re held back from their competitors.</span></p><p><strong><span>James:</span></strong><span> It works great so long as you don&#8217;t need to change anything.</span></p><p><strong><span>Harrison:</span></strong><span> Exactly. So if your pain point is we need to change stuff, then it&#8217;s &#8212; which are the processes that you need to change? Is your goal more flexibility in process improvement, or is your goal cost cutting? And sometimes it&#8217;s both. That will dictate the processes.</span></p><p><span>When I work with clients, depending on your stakeholder, they&#8217;ll care about one versus the other &#8212; or depending on your industry or the situation they&#8217;re in. It&#8217;s going to be based off one of those two criteria normally.</span></p><p><strong><span>James:</span></strong><span> So what have I not asked about? What else should viewers or readers know?</span></p><p><strong><span>Harrison:</span></strong><span> Every business &#8212; if you&#8217;re running a software business, a consulting firm, anything like that, and your goal is not to just get out and sell immediately &#8212; you need to be running hopefully five, ten years. The world is changing very fast now. There are very different possible futures right now, and they have very different outcomes. It&#8217;s really worth thinking about the top futures you could see within the next few years and where you see your company going. And being a little almost extreme with that.</span></p><p><span>The possible deviation in futures is very extreme. If you go back 15 years, people were like, you have software, you have consulting, we&#8217;re going to bill, we&#8217;re going to charge licenses, and we&#8217;re going to just keep doing that forever. That was true till now. It might not be true anymore.</span></p><p><span>Ask yourself: what if our core value proposition at a global level evaporates in the next five years? And what does that mean for us as a company? Every company should do that.</span></p><p><strong><span>James:</span></strong><span> What do you do with that once you&#8217;ve done it?</span></p><p><strong><span>Harrison:</span></strong><span> You need to start changing your plans to capitalize on the main scarcity. If you&#8217;re a business, your goal is to monetize scarcity. If scarcity is changing at a global level, your business strategy needs to change at a global level.</span></p><p><span>Let&#8217;s say we are moving towards Ultron World. That means potentially everything will become difficult to monetize at some point, at least for a human. But not everything will become difficult to monetize at the same time.</span></p><p><span>You need to start thinking about what do you see evaporating and in what order? Your business roadmap and your product roadmap need to start reflecting your bet there. You might make the wrong call, but it&#8217;s probably better than just doing nothing and waiting to die a slow death. In periods of more rapid change, you need to take more risk.</span></p><div><hr></div><p><em><span>Legacy systems are not technical problems. They are high-entropy records of how a business actually evolved &#8212; carrying rules nobody wrote down, idiosyncrasies that exist for reasons nobody remembers, and constraints that may or may not still apply. The AI opportunity is not to manage that entropy in real time. It is to reconstruct it at design time, convert it into something deterministic, and apply thirty years of software QA to the output. As the cost of code falls, the exception cases shrink. What remains scarce is not development capacity. It is the structured understanding of a business that nobody else can see.  </span></em></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.prosaictimes.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading Prosaic Times &#8212; subscribe to get every issue!</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p></p><h4><span>Footnotes</span></h4><p><span>[1]: The NSFNet Acceptable Use Policy, administered by the National Science Foundation, prohibited commercial traffic on the internet backbone until it was retired in April 1995. The commercial internet effectively began with that transition. See: </span><a href="https://www.internetsociety.org/internet/history-internet/brief-history-internet/"><span>NSFNet AUP history</span></a><span>.</span></p><p><span>[2]: Deep Blue (IBM) defeated world champion Garry Kasparov in a six-game match in May 1997 &#8212; the first time a computer won a match against a reigning world champion under standard chess tournament conditions. The human win rate against top chess engines has been effectively zero at the professional level since roughly 2005&#8211;2006.</span></p><p><span>[3]: Research on LLM calibration confirms this. See Kadavath et al., &#8220;Language Models (Mostly) Know What They Know&#8221; (Anthropic, 2022), which found that while LLMs show some self-knowledge about their own uncertainty, they systematically overstate confidence. RLHF training compounds this: the objective function rewards confident correct answers, which penalizes hedging even when hedging is warranted.</span></p><p><span>[4]: The &#8220;half a percent&#8221; figure is illustrative, not empirical &#8212; Harrison and James are reasoning through the asymptotic case where AI handles the vast majority of transactions and only extreme edge cases remain. No benchmark is cited for the specific threshold.</span></p><p><span>[5]: G.K. Chesterton (1874&#8211;1936) was an English writer and social critic, best known for the Father Brown mysteries and for aphorisms that have outlasted his more topical arguments. The fence passage appears in </span><em><span>The Thing: Why I Am a Catholic</span></em><span> (1929): &#8220;There exists in such a case a certain institution or law; let us say, for the sake of simplicity, a fence or gate erected across a road. The more modern type of reformer goes gaily up to it and says, &#8216;I don&#8217;t see the use of this; let us clear it away.&#8217; To which the more intelligent type of reformer will do well to answer: &#8216;If you don&#8217;t see the use of it, I certainly won&#8217;t let you clear it away. Go away and think. Then, when you can come back and tell me that you do see the use of it, I may allow you to destroy it.&#8217;&#8221;</span></p><p><span>A classic formulation of epistemic humility: before removing something, understand why it was put there. The reason may have been silly. It may have become irrelevant as circumstances changed. But you must understand before you act. The principle maps cleanly onto legacy code &#8212; where the original intent of a module or business rule is often invisible to later teams.</span></p><p><span>See Tom Nijhof-Verhees, </span><a href="https://itnext.io/legacy-code-chesterton-fence-vs-%C3%B3lafurs-yellow-box-45f3cb040c05"><span>&#8220;Legacy code: Chesterton Fence vs. &#211;lafur&#8217;s yellow box&#8221;</span></a><span>, ITNEXT (November 2024); and Christos Galanopoulos, </span><a href="https://medium.com/@christosgalanop/chestertons-fence-8a56071cba27"><span>&#8220;Chesterton&#8217;s Fence&#8221;</span></a><span>, Medium (September 2025), which documents a digital transformation team that stripped out &#8220;redundant&#8221; validation rules from an inventory system &#8212; they turned out to be court-mandated procedures from a legal settlement.</span></p><p><span>A related mirror concept: &#8220;Chesterton&#8217;s gap&#8221; &#8212; the constraint you should have built but didn&#8217;t, because nobody understood the problem well enough to know it was needed. The empirical version of the fence is the Scream Test: announce you&#8217;re removing something and wait to see who objects. If nobody does, maybe the fence never mattered.</span></p><p><span>This reminds me of a storage re-tiering exercise from 2007. Developers swore their applications needed the highest class of Fibre Channel storage. The head of infrastructure quietly moved their storage anyway to a lower SAN tier. Nobody noticed. Except finance, which was happy.</span></p>]]></content:encoded></item><item><title><![CDATA[Every decision you make rests on a forecast]]></title><description><![CDATA[Adam Braff on how to make super-forecasts]]></description><link>https://www.prosaictimes.com/p/every-decision-you-make-rests-on</link><guid isPermaLink="false">https://www.prosaictimes.com/p/every-decision-you-make-rests-on</guid><dc:creator><![CDATA[James Kaplan]]></dc:creator><pubDate>Sun, 28 Jun 2026 21:01:03 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/203913714/feb6800e5d5260503225e4cb9461902c.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p><span>Every December the Brown Daily Herald used to hold a dinner at the old Omni Biltmore Hotel in Providence to celebrate the incoming board and say goodbye to the old one. It is a melancholy event for the outgoing editor-in-chief. At least it was for me.</span></p><p><span>I had outlined plans and aspirations at the previous year&#8217;s dinner. When I came to the podium at the end of 1991, I thought about everything the 126th board hadn&#8217;t accomplished &#8212; and all the political capital expended for mixed returns. Still: we published every day of the academic year despite two blackouts. We didn&#8217;t get sued. None of the corrections we had to run were catastrophic. We published at least a few good stories.</span></p><p><span>My successor called me to the stage. I received respectful applause &#8212; more due to the position than the man. I thanked each member of the board. The room exploded when I reached Adam&#8217;s name. The staff understood exactly the energy and creativity with which he had attacked the role of Opinions Editor. Despite our differences of, well, opinion, I remain grateful to Adam for his contributions to the paper, even decades later.</span></p><p><span>Adam and I ran into each other again at McKinsey. By then he had decided against litigation as a vocation and was already developing into one of the most rigorous thinkers I know on data and analytics. Senior roles at JPMorgan Chase, DirecTV, Zurich Insurance, and Point72 followed &#8212; teams as large as 170 people, enterprises with up to 60 million customer relationships. He now advises boards and senior leadership teams, teaches in Brown&#8217;s EMBA program, and runs an annual </span><a href="https://braff.co/"><span>forecasting contest</span></a><span>, which I fear to enter.</span></p><p><span>Everything we do &#8212; every business decision we make &#8212; implicitly rests on a forecast. Which is why I needed to get Adam&#8217;s view on what AI means for data, analytics, and the practice of forecasting itself.</span></p><p><span>Three things struck me as particularly worth your time.</span></p><p><span>First, the B2C-vs.-B2B gap in analytics is real &#8212; Adam puts it at twenty years &#8212; but the cause is not what most people assume. It is not that B2C data is cleaner. It is that B2C businesses have enough observations to find statistical regularities. A million customers generates surprises. Seventy-five institutional accounts does not. AI changes some of this at the margin, but domain expertise &#8212; knowing which variables to featurize, which hypotheses to form &#8212; remains the scarce resource.</span></p><p><span>Second, taking payoff curves into account as you thinking about your career and your job. Adam&#8217;s formative experience was as a litigator: limited upside, catastrophic downside, a profession structured for you to lose. He now teaches his kids to think about every career choice as a payoff curve before accepting it. Most technology managers are running the same analysis implicitly every time they commit to a timeline or decide whether to invest in redundancy. Making the curve explicit demystifies the decision.</span></p><p><span>Third, Adam&#8217;s argues that the manager who has actually formed a probability &#8212; even a rough one &#8212; about whether a project will come in on time is making a different kind of bet than the manager who just called it a plan. The first manager will be better calibrated over a portfolio of decisions. &#8220;It matters to be 53% right instead of 52% right&#8221; is not a hedge fund insight. It is a description of how operational advantage compounds.</span></p><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.prosaictimes.com/p/every-decision-you-make-rests-on?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading Prosaic Times &#8212; share it with a friend!</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.prosaictimes.com/p/every-decision-you-make-rests-on?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.prosaictimes.com/p/every-decision-you-make-rests-on?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><h3><span>Introduction: from College Hill, back to College Hill</span></h3><p><span>James Kaplan:** Welcome to another Prosaic Times video podcast. We have with us Adam Braff, who I&#8217;ve known since about 1990. I&#8217;ll let Adam introduce himself and talk a little bit about his journey, and then we&#8217;ll start to dive deep into forecasting and what AI means for forecasting.</span></p><p><strong><span>Adam Braff:</span></strong><span> Thanks for having me, James. I guess if I could describe what I do now, it is not strictly about forecasting. It&#8217;s helping corporates and investors figure out what to do with data and analytics, and increasingly AI. So some of that is descriptive analytics and trying to figure out how many widgets are we selling and why, and some of it is predictive, and how many widgets are we gonna sell next year and how do we make that number go up?</span></p><p><span>So predictive does come into the work that I do</span></p><p><strong><span>James:</span></strong><span> Yes, and we all want to hear about the Narcissist forecasting contest, which I am proud never to have taken part in &#8212; because I&#8217;m sure I would lose badly.</span></p><p><strong><span>Adam:</span></strong><span> Nobody loses in the contest. You gain knowledge, you get smarter. And even if you&#8217;re gunning for first place, which is fair to do, it actually influences your strategy. It&#8217;s like when you&#8217;re entering a March Madness bracket, do you pick a lot of weird long shots, or do you try to be as accurate as possible?</span></p><p><span>I try to persuade people to just get more accurate year over year and have the least error overall in their forecasting. So nobody loses in this contest. They get a score, they can get coaching and feedback from me for free, and then they try to get better every year</span></p><p><strong><span>James:</span></strong><span> Okay. So tell us a little bit about your journey</span></p><p><strong><span>Adam:</span></strong><span> We graduated into a recession, if you may recall.</span></p><p><strong><span>James:</span></strong><span> Was not fun</span></p><p><strong><span>Adam:</span></strong><span> That was the reason why my wife and I &#8212; then girlfriend &#8212; decided to go to law school. It was a good way to hide out from the economic storms of the early &#8217;90s, and that was kind of a mistake, I would say. It was a big detour in my career, but I ended up going to law school and then practicing as a litigator at a big firm in DC for three years, really not enjoying any of it, and trying to find a way out.</span></p><p><span>And as it happened, I had put myself into a bit of a corner because the world doesn&#8217;t really need litigators. There aren&#8217;t a lot of obvious ways for litigators to turn into some kind of beautiful butterfly. So I took advantage of the fact that it was the dot-com boom, the first dot-com boom happening at the end of the &#8217;90s, and ended up getting a job at McKinsey, and it was a fresh start for me.</span></p><p><span>I was 29 years old, and I just said, &#8220;Let&#8217;s, let&#8217;s start again at the bottom, and this time pretend I had gone to business school instead of law school,&#8221; I got my mini MBA from McKinsey, which consists of three weeks of getting bombarded with strategy ops, marketing, and org stuff, and then ended up staying at the firm for a lot longer than I thought I would be there.</span></p><p><span>I ended up doing work that was really what we would now call data analytics AI. At the time, I think we called it big data. It was how do companies use larger data sets than would fit in Excel and creative new kinds of data and A/B testing on their customers and calculations of customer lifetime value?</span></p><p><span>How do consumer businesses figure out how to do more of that stuff in order to attract and retain the most valuable customers? And that&#8217;s something you can do in a lot of different industries, as it turns out</span></p><p><strong><span>James:</span></strong><span> Did you go to Mini MBA in Kitzb&#252;hel or do you go someplace else?</span></p><p><strong><span>Adam:</span></strong><span> I went to Kellogg. I had a bunch of trainings in Kitzb&#252;hel, but I was in Kellogg freezing my ass off for three and a half weeks in January of that year</span></p><p><strong><span>James:</span></strong><span> I&#8217;m sure it was warmer than it was in Kitzb&#252;hel and easier to get to</span></p><p><strong><span>Adam:</span></strong><span> Exactly. It was nice.</span></p><p><span>So I stayed at the firm for 10 years. I was a generalist partner in the DC office. None of my clients were really government or particularly local to DC, so I was traveling a lot. Had three kids in that span of time, and at some point I said, &#8220;All right. It&#8217;s time for me to get a real job and figure out what I want to do in the real world.&#8221;</span></p><p><span>So I left in 2009 and had a few different offers &#8212; some in New York, one in Vegas, which my wife vetoed &#8212; and ended up going to JPMorgan Chase to become their head of customer data and analytics. That was for the Chase consumer businesses: figuring out what to do with information about customers who might have a Freedom credit card and a Chase mortgage and a Chase checking account.</span></p><p><span>What do we do to put all that information together and help the bank make better risk decisions, better anti-fraud decisions, better marketing decisions? I did that for a few years and then got recruited over to DirecTV to run business analytics there. That was different because there was an existing team of really good analytics people doing the same work but for pay television &#8212; a much simpler business, with some interesting lifetime value drivers.</span></p><p><strong><span>James:</span></strong><span> Interesting. And then you did an insurance company for a while, and you&#8217;ve also recently been teaching at Brown.</span></p><p><strong><span>Adam:</span></strong><span> DirecTV got bought by AT&amp;T, a bunch of us bailed out. I ended up going to Zurich Insurance and ran data and analytics there. I got a taste of the IT world by reporting into the chief operations and technology officer &#8212; which let me see what it&#8217;s like to actually build the stuff and not just give the requirements.</span></p><p><span>Then I spent three years at Steve Cohen&#8217;s hedge fund as head of data sourcing and strategy &#8212; data acquisition, essentially. I&#8217;ve been independent since 2019. Hung out a shingle that year and started teaching at the same time.</span></p><p><span>I began at NYU, created a class called Business Analytics and Data Visualization, taught different variations of it for a while. Then we moved to Providence, where I&#8217;m sitting now, and I&#8217;ve been teaching versions of that class at Brown.</span></p><h4><span>Is B2C 20 years ahead of B2B in customer analytics?</span></h4><ul><li><p><span>B2C is roughly 20 years ahead of B2B in customer analytics &#8212; not because the data is cleaner, but because there are simply more data points to work with.</span></p></li><li><p><span>The analytics opportunity in B2B looks fundamentally different: customer targeting and Salesforce effectiveness rather than churn modeling and cross-sell.</span></p></li><li><p><span>AI and agentic data ingestion could narrow the gap &#8212; converting unstructured B2B data into analyzable signals.</span></p></li><li><p><span>Domain expertise still matters: knowing </span><em><span>how</span></em><span> to featurize variables (competitor footprint, not just state) is what separates the old hands from the clever prompters.</span></p></li></ul><p><strong><span>James:</span></strong><span> Let me ask this question. You&#8217;ve done a ton of stuff in what I&#8217;d describe as the B2C world, and it&#8217;s been my observation that B2C is light years ahead of B2B on analytics &#8212; just because the data is cleaner. And I hypothesize one of the interesting things about gen AI is you can now clean up the data, correlate it, convert unstructured text into structured data you can analyze.</span></p><p><span>So I was wondering if you could comment on how far ahead the B2C world is compared to B2B on analytics, and to what extent might gen AI or agentic data ingestion and cleansing help the B2B world catch up?</span></p><p><strong><span>Adam:</span></strong><span> It&#8217;s like 20 years ahead[1], but probably for a different reason than the reason that you set out. It&#8217;s more that there are more data points to measure in the B2C world. And so if you&#8217;re gonna list all the use cases, if a private equity firm comes in and buys a consumer business or buys an industrial business, all the things you&#8217;re gonna go work on, there are gonna be analytical big data things to do over here that have to do with acquiring more customers and retaining your best customers and figuring out who those best customers are and cross-selling and stuff.</span></p><p><span>Over here, you&#8217;re like optimizing a factory or something, right? So to the extent that there&#8217;s data stuff, and very little of my career has been over here, right?</span></p><p><strong><span>James:</span></strong><span> Right</span></p><p><strong><span>Adam:</span></strong><span> You&#8217;re gonna be getting information from things &#8212; what was briefly called the Internet of Things &#8212; and getting instrumentation data from over there.</span></p><p><span>So big data definitely exists, and there are use cases for it, and I sit on councils with people who do this stuff. It just looks very different from the kinds of big data and analytical stuff that I did, and that my father did before me. He&#8217;s retired now, but he was doing data-based marketing back in the &#8216;70s and &#8216;80s.</span></p><p><span>Second-generation data and analytics &#8212; something that hadn&#8217;t existed before.</span></p><p><strong><span>James:</span></strong><span> I was thinking about this in the context of customer analytics. If you have a million households in a B2C business versus seventy-five or a couple hundred corporate institutions &#8212; which have complicated internal dynamics &#8212; the N question becomes obvious. You don&#8217;t typically have many decision-makers when someone decides to buy cable services. Maybe one, maybe two. Whereas in B2B procurement, there could be twenty decision-makers in the process, and they all interact with each other.</span></p><p><strong><span>Adam:</span></strong><span> The analysis you would do in B2B Salesforce effectiveness would have a lot more to do with customer targeting &#8212; going out and grabbing more information about your target, using some agentic tool to pull that and put it somewhere you can analyze it and make good decisions.</span></p><p><span>The reason the million-customer B2C business got ahead is that a lot of analytics is looking for patterns, for statistical regularities. If you can determine that customers in this region are stickier, or that customers who came through this channel spend more, there are just many more ways to do those analyses &#8212; with genuine comparative advantage over an executive doing everything by intuition.</span></p><p><span>There&#8217;s at least a fighting chance for the data to tell you a different story. You think the higher-priced product is better, but the customers don&#8217;t stick around as long once you control for everything &#8212; and therefore you shouldn&#8217;t be charging more or assume that&#8217;s the right answer.</span></p><p><span>You&#8217;ll come up with intuitions like that on the B2C side. You won&#8217;t on the B2B side because you don&#8217;t have enough N to surprise anyone with that kind of finding.</span></p><p><strong><span>James:</span></strong><span> Tell me if this is right. The more independent variables you&#8217;d have to take into account, the larger the N you need in order to get a relevant statistical sample.</span></p><p><strong><span>Adam:</span></strong><span> I think that&#8217;s right. And I don&#8217;t want to make too much of statistical significance here. A lot of what you&#8217;re doing in B2C consumer analytics is descriptive analytics &#8212; a BI dashboard, not a giant regression model with a lot of independent variables. You want to slice your data one or two dimensions at a time and just look at the graph. Which numbers are higher? Is it this product, this region, this group of call center agents? That&#8217;s what lets you drill in another level and understand what&#8217;s happening.</span></p><p><span>You can have lots of dimensions and measures that you think of as independent variables &#8212; you&#8217;re just going to be doing them a little at a time, flexibly drilling in to find the hotspots. The regression is just one part of that.</span></p><p><strong><span>James:</span></strong><span> What you&#8217;re saying is there&#8217;s a lot of power in just being able to do Pareto analysis &#8212; being able to look at your churn by segment, by size of spend, by region, by product mix.</span></p><p><strong><span>Adam:</span></strong><span> Yes, exactly.</span></p><p><strong><span>Adam:</span></strong><span> Right, exactly. So we were at DirecTV, churn was the number one thing. It was the era of cord cutting and cord nevers. probably a lot of your viewers have never thought to buy a monthly pay TV subscription &#8217;cause it&#8217;s all, they may get it through a streaming product, but not through, a cable</span></p><p><strong><span>James:</span></strong><span> every now and again, I will try to explain the concept of channels to my kids, and they&#8217;re just confused by it.</span></p><p><strong><span>Adam:</span></strong><span> Yes</span></p><p><strong><span>James:</span></strong><span> I try to explain that in New York in the 1970s you had channel 2, 4, 5, 7, 9, 11, and 13, and that was it. They accuse me of being old.</span></p><p><strong><span>Adam:</span></strong><span> The reason I bring up DirecTV is not to make you feel old. It&#8217;s that the main problem we were trying to solve was why churn was so bad and how to make it better. And if you think about the ways to slice churn, first you want the churn rate &#8212; within any given customer population, what percentage are canceling over a month or a year?</span></p><p><span>When you start slicing it, the intuitions you might have &#8212; is it by demographics, age and gender? &#8212; that&#8217;s not what matters. What matters is things like which customers are rolling off a $5-a-month promotion this month. Those turn out to be the vulnerable ones.</span></p><p><span>Or which customers are in the Fios footprint or the Comcast footprint &#8212; does that make a difference, and is it trending differently over time? You need the data to do that kind of work.</span></p><p><strong><span>James:</span></strong><span> So what I hear you saying is: the availability of the data, obviously, but also the person who can develop a hypothesis about what might be a relevant driver &#8212; competitor footprint, for example.</span></p><p><span>We needed that hypothesis generation in a world where analytics were expensive &#8212; someone had to go do the cuts in a spreadsheet or via SQL. In a world where analytics are cheaper, how much of it is &#8220;let&#8217;s just run all three hundred cuts and see what it tells you,&#8221; versus using a model to discern which cuts might actually have real differences?</span></p><p><span>Because I think both you and I have done an analytical cut a million times, said &#8220;region has no impact,&#8221; &#8220;size of spend has no impact,&#8221; and then &#8212; &#8220;overlap with competitive footprint, that has the impact.&#8221; You have to do nineteen analyses before you land on the twentieth that&#8217;s meaningful.</span></p><p><strong><span>Adam:</span></strong><span> Domain expertise and taste matter because you have to figure out how to featurize these variables. Region by itself, cut generically into US states or metropolitan areas, gives you a boring answer.</span></p><p><span>But if you join that data up with another data set &#8212; this is the Comcast footprint, this is the AT&amp;T pre-merger footprint &#8212; suddenly you&#8217;re testing something real. Knowing how to featurize the data to test hypotheses efficiently is still very valuable.</span></p><p><span>And AI tools, if you coach them correctly and bring enough taste and judgment to it, can let a sufficiently senior person test a much larger number of hypotheses. They&#8217;ll also surface a lot of spurious answers along the way.</span></p><p><span>A brand new data science graduate would have a hard time hitting the ground running in one of those businesses. Even a very clever prompter isn&#8217;t going to get to the right answer the way an old hand would.</span></p><p><strong><span>James:</span></strong><span> Creativity and context matter here. You make the point about competitor footprint. Who knows &#8212; state may be a weak signal, but population density may be a much stronger one. You get a weak signal from New Mexico and Wyoming being different from New Jersey and Rhode Island, but when you really dig in, it&#8217;s the Providence metro versus less densely populated parts of Rhode Island that&#8217;s driving it.</span></p><p><strong><span>Adam:</span></strong><span> And you&#8217;re keeping track of the time dimension. Things change over time. Everything changed in COVID. You might decide to cut off your analysis at the post-COVID era, or account for two competitors merging. This happened constantly with banking analyses.</span></p><p><span>One of the analyses I used to do at the firm was on customer experience. We ran a big annual panel surveying people about their banks &#8212; and it was always difficult because the banks kept changing. The American Customer Satisfaction Index, which tracks these things longitudinally, has the names of ancient banks nobody&#8217;s heard of &#8212; Chemical Bank &#8212; that we now know as Chase.</span></p><p><span>There is genuine value in domain expertise that AI cannot yet replicate.</span></p><p><strong><span>James:</span></strong><span> What I should do one of these days is a quiz &#8212; Chemical Bank, Manufacturers Hanover, First USA &#8212; and you have to guess which bank they&#8217;re part of now.</span></p><p><strong><span>Adam:</span></strong><span> The world&#8217;s most exciting quiz. I agree.</span></p><h4><span>The debate on virtual panels</span></h4><ul><li><p><span>Synthetic data is valuable for prototyping and pedagogy &#8212; stuffing a dashboard mockup with plausible fake data is now standard practice.</span></p></li><li><p><span>Where it breaks down: using synthetic panels as a substitute for real market research, especially for purchase-intent questions. There is no signal like that in the model.</span></p></li><li><p><span>The motte-and-bailey risk: vendors pitch synthetic panels as research-grade but deliver something closer to a prototype illustration.</span></p></li><li><p><span>James&#8217;s CIO/CTO panel is more useful for testing message clarity and resonance than for predicting buying behavior &#8212; a meaningful distinction.</span></p></li></ul><p><strong><span>James:</span></strong><span> Never said I was cool. What do you think about virtual panels? Particularly in the B2B space, I&#8217;ve started playing with using agents to simulate the decision-making of certain people. Valid? Less than valid? Intriguing?</span></p><p><strong><span>Adam:</span></strong><span> I remain skeptical of the whole field of synthetic creation. On the one hand, I use it for pedagogical purposes where I&#8217;m creating a data set to illustrate a point to my students. It&#8217;s great for that, especially if you&#8217;re gonna sprinkle in personally identifiable information, which you don&#8217;t wanna do with actual humans.</span></p><p><span>I use it to make, prototype dashboards. This is something that has become very common now, not just me, but many people since the Claude Code stuff really got going in earnest back in January. I&#8217;m sure you&#8217;ve done this and you&#8217;ve seen it, but many people are mocking up prototypes very quickly, and stuffing them with synthetic data is a pretty good idea, right?</span></p><p><span>To give people a sense of the art of the possible there.</span></p><p><strong><span>James:</span></strong><span> A couple of weeks ago I created the data for a change management program at a major financial institution &#8212; all dummy data, but realistic enough to demonstrate something. That would have taken weeks to do manually.</span></p><p><strong><span>Adam:</span></strong><span> Incorporating randomness and signal to make it feel like real data is genuinely hard. Agreed.</span></p><p><span>Now, on panels: I&#8217;m doing a lot of consumer insights work these days, back on the B2C side. You want to survey 500 Americans about something &#8212; and it&#8217;s getting harder and harder to find real people who aren&#8217;t robots or speeders or cheaters. So people are pitching synthetic panels: 500 simulated respondents. Why not?</span></p><p><span>Here&#8217;s why not. The whole point of a real panel is the signal &#8212; what actual people in the world want, the clusters that form, the principal components that emerge. It&#8217;s not just big spenders versus quick deciders; there&#8217;s a third dimension that actually explains the variance.</span></p><p><span>Trying to derive all that from synthetic data seems crazy to me. I&#8217;ve had a couple of conversations with these vendors, and I worry that what they&#8217;re pitching sits somewhere between the prototype mockup work we were just celebrating and the actual market research my clients need to make real decisions.</span></p><p><span>It&#8217;s a motte-and-bailey: they pitch it as research-grade but it&#8217;s really only as good as a prototype illustration. I&#8217;d love someone to steel-man what synthetic data is genuinely good for beyond that.</span></p><p><strong><span>James:</span></strong><span> For the blog, I created a panel of five hundred CIOs and CTOs. I gave each member of the panel a persona &#8212; this person is the CIO of a pharma company with five hundred million dollars in IT spend, this person is the CIO of an asset manager with a billion dollars in IT spend. Then I used the OCEAN framework to create psychological profiles.</span></p><p><strong><span>Adam:</span></strong><span> Mm-hmm.</span></p><p><strong><span>James:</span></strong><span> Each individual has a job, a title, a company, and a personality profile. I run each draft through them. I wouldn&#8217;t bet the farm on the scores, but the quotes I get back are really useful, and I&#8217;ll go through about seven iterations. Part of me thinks it may be less helpful for predicting buying intent and more helpful for testing marketing messages &#8212; because that&#8217;s where large language models are genuinely good.</span></p><p><span>It&#8217;s hard for them to predict whether somebody will buy, but they may be better at understanding whether a message is more or less understandable, more or less compelling. Does that make sense?[5]</span></p><p><strong><span>Adam:</span></strong><span> A little bit. You used the words &#8220;testing marketing messages.&#8221; I think it&#8217;s more like &#8212; in this case you&#8217;re testing your blog. Generating responses that would go outside of what you and I would naturally brainstorm on, how people are thinking about things.</span></p><p><strong><span>James:</span></strong><span> It&#8217;s pretty good for that. I don&#8217;t workshop my blog posts with people who might be more emotionally invested than I am.</span></p><p><strong><span>Adam:</span></strong><span> We&#8217;ll have to look at your Ocean scores later. We&#8217;ll compare them offline.</span></p><p><span>I like the idea of computers generating things. It&#8217;s a large corpus of material &#8212; you sift through it, see what&#8217;s interesting, throw away what&#8217;s not. You and I have been around long enough to tell the difference. You generated it cheaply, so the discount rate on discarding it is low.</span></p><p><span>But that&#8217;s not really what market research is. Qualitative research is different: a focus group has real human beings who can say unexpected things. Small N, unpredictable. But once in a while someone says &#8220;I never knew you could use the product this way&#8221; &#8212; and maybe only 1% of people use it that way, but knowing that might spark a brand campaign.</span></p><p><span>So I&#8217;m in favor of the tools for idea generation and checking your work. What I&#8217;m skeptical of is using synthetic panels for commercial due diligence. You&#8217;re deciding whether to acquire a BI tool or a security product, and you&#8217;re going to rely on numbers saying 20% of synthetic CIOs might spend more than USD 10MM on it.</span></p><p><span>That doesn&#8217;t seem right to me. I don&#8217;t think there&#8217;s signal like that in there.</span></p><p><strong><span>James:</span></strong><span> My take is it&#8217;s more a part of the chain. It doesn&#8217;t preclude or replace going and doing the interviews. But you can&#8217;t test and re-test and re-test with a live interview set. You can workshop messages or hypotheses and then go confirm with actual human beings.</span></p><p><strong><span>Adam:</span></strong><span> This is a good segue into forecasting.</span></p><h4><span>All business is forecasting</span></h4><ul><li><p><span>Every business decision is implicitly a forecast &#8212; a bet that one management action will outperform another.</span></p></li><li><p><span>The distinction is sharpest for investors: a binary buy/short decision forces the forecast into the open. Operational managers face the same bets but rarely frame them that way.</span></p></li><li><p><span>Tetlock&#8217;s superforecasting research showed that structured generalists &#8212; triage tractable problems, decompose, work as a team, ensemble independently &#8212; beat CIA analysts with classified intel.</span></p></li><li><p><span>The Brier score disciplines probability estimates: being 52% right vs. 53% right sounds trivial, but at sufficient scale and leverage it is everything.</span></p></li></ul><p><strong><span>James:</span></strong><span> Go there</span></p><p><strong><span>Adam:</span></strong><span> Due diligence is a form of forecasting. You&#8217;re trying to predict what the financials of this business are going to look like at current course and speed &#8212; and what they&#8217;ll look like if we apply our private equity magic on top of it.</span></p><p><span>All business decision-making is implicitly a forecast: a bet that this management action will produce better results than that one. The point is sharpest when you&#8217;re an investor at the margin &#8212; do I buy because it&#8217;s going up, or short because it&#8217;s going down?</span></p><p><strong><span>James:</span></strong><span> Very binary &#8212; buy or do not buy &#8212; as opposed to operational decisions, which are more continuous in nature.</span></p><p><strong><span>Adam:</span></strong><span> Exactly. When you&#8217;re thinking about numbers and where they&#8217;re going in the future, it probably helps to be good at forecasting more generally. And this is what Tetlock demonstrated, decades ago with IARPA and these defense intelligence agencies.</span></p><p><span>For podcast viewers and listeners who aren&#8217;t familiar: Tetlock is a professor at Penn who has been studying forecasting for a long time, and came out with a very influential book called </span><em><a href="https://www.penguinrandomhouse.com/books/227815/superforecasting-by-philip-e-tetlock-and-dan-gardner/"><span>Superforecasting</span></a></em><span>, where he packaged the lessons of groups of generalists who &#8212; the legend has it, and I think I&#8217;m giving a fairly accurate version &#8212;</span></p><p><span>were able to forecast world events &#8212; will this world leader be deposed or die &#8212; better than CIA operatives on the inside who had all the intel collected expensively by our intelligence apparatus.</span></p><p><span>And so these generalists &#8212;</span></p><p><strong><span>James:</span></strong><span> Did the generalists forecast the Knicks were gonna win the championship this year?</span></p><p><strong><span>Adam:</span></strong><span> Nobody predicted that except my sons, who believed in it. And so it happened.</span></p><p><span>Tetlock codified the rules of what it means to be a superforecaster. These people were really good at triaging problems by tractability. Some things are impossible to forecast &#8212; the Knicks. Some are too easy &#8212; my soccer team, Tottenham Hotspur, doing badly. The Jets are a better example of the tractable middle ground: will they make the playoffs, will a company beat earnings, will this entity win a major award?</span></p><p><span>Allocate your time to the tractable problems. Decompose them into constituent parts. Work as a team, but have people develop independent points of view first, then bring the theories together and fight about who has the better argument. Ensemble different independently-made forecasts where possible.</span></p><p><span>Those are the </span><a href="https://www.lesswrong.com/posts/dvYeSKDRd68GcrWoe/ten-commandments-for-aspiring-superforecasters"><span>Ten Commandments of superforecasting</span></a><span> that Tetlock codified in 2015.[2] I started my forecasting contest that same year.</span></p><p><span>I read the book and launched the first Narcissist forecasting contest in 2016 &#8212; The Narcissist being a long-running annual newsletter I&#8217;ve produced since 1992. Twenty-five binary propositions about the world, each either going to happen or not.</span></p><p><span>Everyone predicted the likelihood of each from zero to 100%, including, at the time, whether Trump would get elected &#8212; which everyone gave very low numbers to.</span></p><p><span>The scoring mechanism is a Brier score. If I predict 40% for Trump getting elected and he&#8217;s not elected, the truth is zero: 0.4 minus 0 is 0.4, squared to exaggerate the impact of being far off, giving me a 0.16 Brier. If Trump is elected, my error is 0.6, and the square is 0.36. A high number is bad. It&#8217;s like a golf score.</span></p><p><strong><span>James:</span></strong><span> Here&#8217;s a business question. Can you predict a probability, or do you only state one? You can predict whether a candidate is elected or not &#8212; but we&#8217;ll never know the true likelihood of that election at any given moment. You can estimate a likelihood, or you can predict an outcome. But can you actually predict a likelihood?</span></p><p><strong><span>Adam:</span></strong><span> It is a bit of a metaphysical question. In a sense, all these predictions are wrong &#8212; everything goes to zero or one. There are people who look at the whole enterprise and say it&#8217;s stupid. There&#8217;s no difference between .4 likely and .6 likely. Just make the call. I&#8217;d call those people extremists.</span></p><p><span>The other camp &#8212; generally called Bayesians &#8212; believes that we don&#8217;t know ex ante whether a thing will happen, and that there is genuine utility in knowing whether something is 60% or 40% likely. The value is in the repetition. You make predictions over and over again.</span></p><p><span>The clearest illustration is betting markets. In 2016, Trump was trading at under 20% on the eve of the election. Nate Silver had him at 28% &#8212; out of consensus to the high side. If you&#8217;d looked at the pot odds and said &#8220;I can buy Trump contracts at 20 cents because Nate says 28,&#8221; you would have done well. Even though you thought it was less than 50% likely, you thought it was more likely than the market priced it.</span></p><p><span>I&#8217;m a Bayesian. Being able to tell a 52% from a 48% likelihood is useful because we make a lot of bets. You&#8217;re making them every day when you&#8217;re running a business. Being slightly more right and less wrong compounds.</span></p><p><strong><span>James:</span></strong><span> Everybody I&#8217;ve known who&#8217;s managed money for a hedge fund is a fanatical Bayesian. There&#8217;ll be traffic, but it depends on three things that might drive more or less of it &#8212; let me think through the prior and posterior. Which is interesting, though it gets a bit exhausting.</span></p><p><strong><span>Adam:</span></strong><span> One of the most common approaches in a long-short public equity fund is calling the quarter &#8212; is this stock going to beat or miss earnings? More precisely: beat or miss the whisper number on whatever KPIs matter.</span></p><p><span>The hit rate is 52%, 53%. It&#8217;s much better to be right 53% of the time than 52% &#8212; that&#8217;s how they make their money. They&#8217;re repeated gamblers doing it at a very high level, trying to maintain that little bit of edge in a zero-sum world where everyone else is trying to do the same.</span></p><p><span>It&#8217;s hard. But it matters to be 53% right instead of 52% right.[4]</span></p><p><strong><span>James:</span></strong><span> Because a hedge fund portfolio manager who&#8217;s right 53% of the time with sufficient leverage is enormously value accretive. Fortunes can be made with a fifty-three/forty-seven split, plus leverage. Operational managers who are right 53% of the time tend to get fired. And in the technology world there&#8217;s the expression &#8220;all day, every day&#8221; &#8212; you can&#8217;t be wrong in one direction.</span></p><p><span>Actually, one of the interesting things here is that in some cases the hedge fund payoffs are symmetric. On the other hand, in an operational world, the payoffs are often highly asymmetric. Could you reflect on that &#8212; applying the insights from superforecasting to an operational environment for people who have to make decisions every day with sometimes highly asymmetric payoffs?</span></p><h3><span>Asymmetric payoffs and career risk</span></h3><ul><li><p><span>Hedge fund payoffs are roughly symmetric: being 53% right vs. 52% right is the whole game. Operational payoffs often aren&#8217;t &#8212; a missed security filing, a waived privilege, a breached system can be terminal.</span></p></li><li><p><span>Adam&#8217;s formative lesson came from a malpractice case: the concave payoff curve of law (bounded upside, catastrophic downside) drove him out of litigation and eventually into analytics.</span></p></li><li><p><span>He vibe-coded a career payoff visualizer to make this intuition concrete &#8212; the same tool every technology manager implicitly needs when committing to timelines, availability zones, or budget targets.</span></p></li><li><p><span>Agile is a structural hedge against the same asymmetry: shorten the cycle, reduce the blast radius of being wrong.</span></p></li></ul><p><strong><span>Adam:</span></strong><span> I would focus on cybersecurity &#8212; an area you&#8217;ve spent more time in than I have. Risk management in cyber is an area with that extreme concave payoff curve[8], where being wrong in a certain direction is extremely career-limiting.</span></p><p><span>One of the formative experiences in that professional journey I sketched out earlier was a malpractice case I tried as a lawyer. Very few cases go to trial &#8212; almost everything is writing briefs and pleadings. But this one did. My client was a lawyer being sued because he had failed to supervise a young associate who was supposed to file in a telecom case and simply didn&#8217;t get it done on time.</span></p><p><span>Once they realized the deadline was approaching, they scrambled, missed the filings, and the telecom project couldn&#8217;t go forward. The client sued. We did good work at trial and settled before it went to the jury.</span></p><p><span>What that case made me realize was that litigation &#8212; and being a lawyer generally &#8212; has that extremely concave payoff curve. If you accidentally produce a document with attorney-client privileged information, when you&#8217;re going through warehouses of material &#8212;</span></p><p><span>It used to be physical warehouses &#8212; for lawyers today it&#8217;s all on a computer, it&#8217;s a cyber problem. But if you accidentally produce a privileged document, you&#8217;ve waived privilege and you&#8217;re in serious trouble. Being a lawyer felt like limited upside &#8212; a nice house if you make partner versus getting fired and never finding work again.</span></p><p><span>So I thought more carefully about these payoff curves. The first conversation I had with my kids when they were old enough was: don&#8217;t choose a profession with that kind of payoff. Do you want a venture capital payoff &#8212; an extreme tournament where the upside is a million times the median, if you&#8217;re genuinely confident in your skills? Maybe. But you&#8217;re probably overconfident. Most people want something with reasonable upside and limited catastrophic downside.</span></p><p><span>I actually vibe-coded a tool to visualize this &#8212; it lets you look at payoff curves for different employers and say: if I get a top-percentile outcome, here&#8217;s how I shake out; if I get the bottom outcome, here&#8217;s how I shake out. You can vary economic conditions and other factors. I stuffed it with synthetic data grounded in actual information. It&#8217;s more of a toy model and theoretical exercise &#8212; an intuition pump to make visible the thing you were saying. Do I really want the job where 10% of the time it&#8217;s utterly fatal?</span></p><p><strong><span>James:</span></strong><span> It&#8217;s directly relevant. People make decisions like this every day. Do I launch this project? Do I use high availability for this application? Do I run it across multiple availability zones? Do I commit to two months versus three? Those are technology examples, but every business manager is asking: what target will I commit to, in revenue or in cost? Thinking through your own payoff matrix &#8212; and the payoff matrices of the people around you &#8212; changes the analysis.</span></p><p><span>Payoff matrices differ enormously by corporate culture. In some organizations, blowing a budget a little is &#8220;try to do better next quarter.&#8221; In others, exceeding a budget in a single quarter is career-limiting.</span></p><p><strong><span>Adam:</span></strong><span> That&#8217;s right. The types of IT projects I mostly see and lead are business intelligence projects &#8212; building out and deploying predictive models. These, especially the dashboards, are generally developed in an agile environment, where agile is kind of a hedge against the asymmetry you&#8217;re talking about.</span></p><p><span>I&#8217;m not building a whole stack waterfall-style with a perfect delivery date. I&#8217;m making it good enough to get adoption, then making it better &#8212; two-week sprints, continuous improvement.</span></p><p><span>So I would argue that agile is a way of coping with an uncertain world. Do you agree?</span></p><p><strong><span>James:</span></strong><span> It&#8217;s more emergent strategy than deliberative strategy. There are people who believe that whoever wrote the Agile Manifesto had some connection to John Boyd &#8212; I haven&#8217;t been able to find as much documentation for that, but the idea is the same: increase the number of cycles, shorten the duration between action and feedback, and revise your strategy accordingly.</span></p><p><strong><span>Adam:</span></strong><span> Exactly. Agile development and hypothesis-driven problem-solving are both hedges against disaster. One of the first things you learn at a consulting firm &#8212; I taught the intro to consulting class several times &#8212; is that you have a day-one hypothesis about the answer.</span></p><p><span>Part of what&#8217;s good about that: when someone stops you in the hall and asks what you think the answer is, you have something. &#8220;I&#8217;m going to test it and refine it and make it better.&#8221; That&#8217;s much better than a long list of ideas with no organizing principle.</span></p><p><span>The risk otherwise is getting caught out with no answer at all. The OODA loop, hypothesis-driven problem-solving, agile &#8212; these are all hedges against uncertainty and against the weird events that shock you.[7]</span></p><p><strong><span>James:</span></strong><span> The interesting thing is that the nature of the bad thing varies by the nature of the system. In an analytics system, the bad thing is bad information &#8212; you make a bad business decision. In an operational system, like an order capture system, the bad thing is different: downtime, a cybersecurity event, a transaction failure.</span></p><p><span>We deal with those types of negative payoffs differently, using different mechanisms. It&#8217;s probably worth thinking about that more rigorously. Let me pivot just a little bit.</span></p><h4><span>What do we tell early career professionals about AI?</span></h4><ul><li><p><span>Get a job in a for-profit company and help it make money with data. That is still good advice. Those jobs are not disappearing as fast as the pessimists predict.</span></p></li><li><p><span>The supply of problems is highly elastic: better, cheaper analytics generates more questions, not fewer analysts.</span></p></li><li><p><span>Proof-of-work has decayed &#8212; anyone can generate a slop deck. What has not decayed: domain knowledge, taste, and the ability to have a real conversation about a business.</span></p></li><li><p><span>Adam&#8217;s standing advice: pick the domain you care about, grab the public data, do the analysis. Show up to the interview having already thought about how to help the company make money.</span></p></li></ul><p><strong><span>James:</span></strong><span> In my teaching, I&#8217;ve seen a lot of anxiety from people early in their careers about what they&#8217;re going to do with their lives in the age of AI. A number of college seniors asked me, and I said they should learn data structures and data science &#8212; because no matter what happens, that will be valuable. Did I give them good advice or bad advice? And what are you taking away from your interactions with college students?</span></p><p><strong><span>Adam:</span></strong><span> Getting some kind of job and getting out into the real world to develop domain knowledge &#8212; for all the reasons we talked about &#8212; is important. Getting that job is a separate question; that&#8217;s tactics, informational interviewing, picking your spots.</span></p><p><span>But as advice for how to spend the next one to three years: get into a for-profit company and help it make money by analyzing data against real problems. Those jobs are not going away as fast as the most pessimistic people are predicting.</span></p><p><span>The supply of problems is highly elastic.[3] Having people ask good questions &#8212; and the return to a business from asking more good questions and getting quality answers back quickly &#8212; is positive. I&#8217;ve bet my whole career on the idea that most companies would benefit from having one more data scientist, or in this case one incremental unit of data science capability.</span></p><p><span>Which is not the same as replacing all the humans with AI. I&#8217;m on the optimistic side of this.</span></p><p><strong><span>James:</span></strong><span> There&#8217;s more data, available publicly. There&#8217;s more tools that you can use for free. And my inclination, for example, if someone were to ask me, &#8220;Gee, I want a job doing analytics,&#8221; I would say, &#8220;Well, pick the domain you&#8217;re interested in and start doing the analytics.&#8221; Right? Because what&#8217;s gonna be more compelling in a first-round interview? It&#8217;s &#8220;Oh, gee, I&#8217;m, I&#8217;m really interested in the telecom industry, and I grabbed all this from the FCC and I did this analysis, and here&#8217;s what I found.&#8221;</span></p><p><strong><span>Adam:</span></strong><span> I&#8217;ve given a talk on this subject probably every year for the last five years, including the pre-generative-AI era. The advice holds: </span><a href="https://braff.co/jobs"><span>do actual work, show that you know something about the business, demonstrate that you care about it</span></a><span>.</span></p><p><span>I will say that that coming in with a deck, the proof of work aspect of it has gone to kinda zero, right? &#8216;Cause anyone can generate a slop deck. People like you and me might be exquisitely sensitive to seeing a deck and understanding immediately that it was written by AI and the, and the tells in the stylistic, that come out of a Claude, PowerPoint deck.</span></p><p><span>The concept is still correct: get in there, do the work, iterate, think about it. You&#8217;ll be able to have a real conversation about the business because you&#8217;ve learned something along the way &#8212; &#8220;I think 80% of the value is in this part of the product, and here&#8217;s why.&#8221;</span></p><p><span>You&#8217;re not reading off a slide. You&#8217;re engaging a person. There&#8217;s a lot of value in that. And people still show up at interviews without having thought seriously about the business and how they would help it make money. There&#8217;s still a lot of alpha in that.[6]</span></p><p><strong><span>James:</span></strong><span> Terrific. Anything else to add before we wrap up?</span></p><p><strong><span>Adam:</span></strong><span> The forecasting contest runs every year. Free to enter. You get a bowl of pho if you win, and a book &#8212; this year it&#8217;s George Orwell&#8217;s essays. All the information is at braff.co/advice: the current contest, how to enter next year, and other thoughts about food and analytics.</span></p><p><strong><span>James:</span></strong><span> Terrific. Two great topics to discuss. Adam, thank you so much</span></p><p><strong><span>Adam:</span></strong><span> Thanks for having me.</span></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.prosaictimes.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading Prosaic Times &#8212; subscribe to get every issue!</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h3><span>Notes</span></h3><p><span>[1] Obviously twenty years is an estimate -- that doesn&#8217;t make it wrong. </span><a href="https://prosaictimes.substack.com/p/the-world-is-entropic-and-deterministic"><span>The world is entropic, and deterministic systems are not</span></a><span> talked about how organized complexity is much tougher to understand than disorganized complexity.</span></p><p><span>A B2C business with a million customers faces disorganized complexity.  Idiosyncratic individual behavior averages out into stable statistical regularities &#8212; churn rates, cross-sell lift, tenure effects.</span></p><p><span>A B2B software company with sixty enterprise accounts faces </span><a href="https://bsahely.com/2019/11/20/science-and-complexity-the-imperfections-of-science-the-emerging-unity-of-science-warren-weaver/"><span>organized complexity</span></a><span>. One decision-maker changing jobs, or having a bad quarter, creates a measurable swing in the entire dataset. The N is too small to smooth anything, especially since many of the data points are connected to each other. That is why domain expertise is required in B2B analytics in a way it is not in mature B2C analytics &#8212; the data cannot naturally control for the variables that large samples would otherwise absorb.</span></p><p><span>[2] All IT commitments are forecasts based on implicit probability estimates. When a CIO says &#8220;We&#8217;ll deliver in two months&#8221; she estimates the probability of coming in at two months is high enough to avoid the political cost of articulating a more conservative estimate.</span></p><p><span>[3] Adam describes here the </span><a href="https://prosaictimes.substack.com/p/why-genai-wont-kill-white-collar"><span>applicability of the Jevons Paradox to knowledge work</span></a><span>. When the churn data got good enough to slice, the analytics team didn&#8217;t shrink. It grew. Each answer generated three new questions &#8212; why are customers in this region stickier? What&#8217;s driving the gap between acquisition channels?</span></p><p><span>[4] You&#8217;ll never know whether the 60% probability you assigned to a project coming in on budget was the right number. It either did or it didn&#8217;t. But across a portfolio of similar decisions, the manager who has actually formed a probability &#8212; rather than suppressed the uncertainty &#8212; will be better calibrated over time. That&#8217;s what &#8220;it matters to be 53% right instead of 52% right&#8221; means outside a hedge fund. You&#8217;re not making one bet. You&#8217;re making hundreds.</span></p><p><span>[5] There is no perfect data set for the organized complexity of B2B commercial due diligence. Direct customer interviews and focus groups are great, but you only can do so many of them. On-line surveys? Decision-makers responsible for large technology bets at Fortune 100 companies lack the time to respond to them.</span></p><p><span>Adam is correct. No virtual panel can, well, forecast purchase intent. But they should provide </span><a href="https://prosaictimes.substack.com/p/getting-the-message-across-from-fax"><span>invaluable feedback on value propositions and messaging</span></a><span>. And they are both patient and indulgent. You test many variations of a value proposition for example to see which one best resonates.</span></p><p><span>[6] We&#8217;ve heard people confidently predict that early tenure technology jobs will disappear. We&#8217;ve all fielded anxious questions from candidates who should probably believe less of what they read on social media. We have all tried to figure out what to say. As Adam points out learning is the most important thing at the start of your career. And it is </span><a href="https://prosaictimes.substack.com/p/advice-for-this-years-grads-dont"><span>easier to learn useful things</span></a><span> than it has ever been before.</span></p><p><span>[7] Colonel John Boyd&#8217;s </span><a href="https://prosaictimes.substack.com/p/you-need-both-business-technology"><span>Observe-Orient-Decide-Act (OODA) loop</span></a><span> is a model of how people and institutions make better decisions through recursive learning in competitive games. It provides a mechanism for balancing deliberate and emergent strategies, which emerge from the bottom up. It appears to have </span><a href="https://lithespeed.com/agile-caravanserai-jeff-sutherland/"><span>influenced</span></a><span> the agile manifesto.</span></p><p><span>[8] A </span><a href="https://www.youtube.com/watch?v=-aJka_CIxL4"><span>concave payoff curve</span></a><span>: bounded upside, catastrophic downside. Law. Cybersecurity. Most operational IT. A convex payoff curve: bounded downside, extreme upside. Venture capital. Early-stage software equity. CIOs and CTOs often face concave payoff curves. Flawless uptime is invisible. A database corruption is not. When you put together a major incident response plan, you are trying to truncate the ugly end of a concave payoff curve.</span></p>]]></content:encoded></item><item><title><![CDATA[Not 2007 anymore — what VCs have to say about AI and enterprise tech]]></title><description><![CDATA[We so much fun at the TLF panel, we decided to meet again on video!]]></description><link>https://www.prosaictimes.com/p/not-2007-anymore-what-vcs-have-to</link><guid isPermaLink="false">https://www.prosaictimes.com/p/not-2007-anymore-what-vcs-have-to</guid><dc:creator><![CDATA[James Kaplan]]></dc:creator><pubDate>Sun, 21 Jun 2026 20:48:09 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/202999529/856d9ed9a53739a53f20ea06909ff7e5.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>Do you remember 2007? It was boring, if not depressing when it comes to enterprise technology environments. You had a choice between x86 and RISC servers, with three viable providers in each segment. Most infrastructure domains look this way &#8212; two or three storage options, network hardware options, end user device options, DBMS options. CIOs and CTOs often faced even fewer choices in application software segments. I never heard about CIOs spending time with venture capitalists in that era. What would they even talk about? VCs in that era often focused on consumer, rather than enterprise tech. </p><p>Cloud infrastructure, SaaS applications, a revolution in cybersecurity and now AI have upended that unhappy equilibrium of oligopolies. Large enterprises less exclusively act as &#8220;takers&#8221; of offerings from giant technology providers. They <a href="https://www.gartner.com/en/documents/6306415">integrate a wider array of technologies from a wider array of providers</a> &#8212; some of whom are venture-backed attackers.</p><p>Acknowledging this, we did something new at May&#8217;s Technology Leadership Forum session. We convened a panel of venture capitalists to discuss and debate how they see the enterprise technology market. Ed Sim from Boldstart, Daniel Frankenstein from Joule Ventures and Will Summerlin from Autopilot engaged with the group on how enterprises can best work with VC-funded companies and how AI will change B2B software markets</p><p>Here&#8217;s <a href="https://prosaictimes.substack.com/p/trading-bad-inefficiency-for-good">what I wrote</a> about it after the event:</p><blockquote><p>Wow, there is some frustration out there! What do TLF members see from their incumbent software vendors? Slower innovation, degraded quality and more aggressive negotiation. They think some providers see their products as &#8220;falling knives&#8221; and have resolved to extract as much cash as they can from the portfolio before it declines into irrelevance. Others simply don&#8217;t get AI &#8212; they want extortionate rates for unimpressive capabilities that only reinforce silos between different parts of the environment.</p></blockquote><p>TLF members found the discussion so valuable and VCs had so much fun that we decided to reconvene (after much scheduling gymnastics) for a Prosaic Times video discussion.</p><p>The conversation covers five things.</p><ol><li><p>Whether vibe coding and agentic software engineering are the same activity &#8212; they aren&#8217;t, and the distinction matters for how you staff and govern AI work</p></li><li><p>Where the moat lives as the cost of producing code approaches zero &#8212; my answer involves latent information, and it&#8217;s more interesting than the conclusion.</p></li><li><p>Which sectors are most exposed to disruption &#8212; legal and accounting are the easy answers; I have a less obvious one.</p></li><li><p>How enterprise technology leaders should actually engage with the startup ecosystem &#8212; the VC-as-intermediary model turns out to be more consequential than most enterprises realize.</p></li><li><p>And whether you should leave a corporate job to found a company. Ed has a checklist for that last one.</p></li></ol><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.prosaictimes.com/p/not-2007-anymore-what-vcs-have-to?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading Prosaic Times &#8212; share it with a friend!</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.prosaictimes.com/p/not-2007-anymore-what-vcs-have-to?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.prosaictimes.com/p/not-2007-anymore-what-vcs-have-to?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><h3>Introductions</h3><p><strong>James Kaplan:</strong> Welcome to a special Prosaic Times podcast. Back in May, we did something different &#8212; we always get together about 50 or 60 enterprise CIOs, CTOs, and CISOs, and this time we invited a few of my favorite venture capitalists to share their perspective on the enterprise technology market.</p><p>All of our VCs had a blast and found the session both enjoyable and informative. All the members of the Technology Leadership Forum told us they appreciated the session and found perspectives they hadn&#8217;t heard before.</p><p>So I said, we have to get this group together again for a podcast &#8212; so let me start out with some brief introductions. Will, do you want to start?</p><p><strong>Will Summerlin:</strong> My name is Will Summerlin. I&#8217;m a co-founder and general partner at Autopilot. We&#8217;re a growth stage venture capital firm, typically investing from Series B onward</p><p><strong>Daniel Frankenstein:</strong> A co-founder and partner at a firm called Joule Ventures. Seed and pre-seed investor doing B2B software investments, coming out of the Israeli ecosystem.</p><p><strong>Ed Sim:</strong> Boldstart Ventures. We partner at inception with technical founders when they&#8217;re in the idea maze &#8212; companies automating the autonomous enterprise, physical AI.</p><p><strong>James:</strong> Daniel, when we were chatting before, you said that the interaction with the members of TLF was very eye-opening for you. Could speak to that a little bit</p><p><strong>Daniel:</strong> One of the challenges we face in commercializing companies that aren&#8217;t from the United States is building that connection to corporate decision-makers and technology integrators. What we got from the TLF session was direct feedback on specific technologies &#8212; candid views on where enterprises are struggling to integrate AI solutions, and where their long-standing incumbents are trying to introduce AI but not yet meeting the mark.</p><p>It was a fascinating conversation, and it clarified where the real opportunities are for new technology businesses to carve out space.</p><p><strong>James:</strong> We&#8217;ll say incumbent rather than legacy.</p><p>Ed, what was your takeaway? What did you learn from the day?</p><p><strong>Ed:</strong> Everyone is truly, truly interested in deploying agents, and two, it&#8217;s really, really early, and I think that everything we think and know today may be irrelevant tomorrow.</p><p>People are talking about RAG and all these other things &#8212; like, hey, that was gone yesterday. And in fact, everything that we talked about almost since the last TLF, what was that? Six weeks ago? Is almost irrelevant again. The speed at which things are moving is staggering.</p><p><strong>Will:</strong> We&#8217;re extraordinarily early on the adoption curve in terms of enterprise AI adoption. And I think it&#8217;s interesting in that there seems to be a disconnect from the myopic Silicon Valley view and the reality of enterprises. If you talk to a lot of founders or early stage investors or even growth stage investors in Silicon Valley, there&#8217;s this view that adoption&#8217;s happening very, very quickly, and we&#8217;re farther along on that adoption curve.</p><p><strong>James:</strong> But what we heard from members of the forum is that we&#8217;re still very early. It&#8217;s still very much in the experimentation phase, moving to the broad-based adoption phase. And so I think that presents an incredible amount of opportunity ahead, but I also think it reflects this disconnect with the Silicon Valley view. You hear a lot in the ecosystem around token costs, and news stories about companies struggling with token costs. But the enterprises I know are spending trivially on tokens in the context of, say, a USD 1B or USD 2B or USD 500MM IT budget.</p><p>And that is a measure of quite how early we are from an adoption standpoint.</p><p><strong>Ed:</strong> Some of the companies that were the more advanced ones were the ones beholden to one large language model provider.</p><p>The events of the last six weeks &#8212; particularly some where providers said, &#8220;Hey, we&#8217;re gonna interfere in some of these things&#8221; &#8212; have shown that not only do token costs matter, but also which model you&#8217;re beholden to matters.</p><p>So no one&#8217;s gonna want to be beholden to one model. Multi-model architectures have to be built, I think, because of that.</p><p><strong>James:</strong> It reminds me of the era when some people believed you should standardize on a single provider.</p><p><strong>Will:</strong> I think another interesting data point related to token costs is compute resources. We&#8217;re already in an environment where compute is radically supply constrained, and if you look at the growth rates of demand for compute versus supply for compute, demand is growing at a much faster rate than supply possibly could. [2]</p><p>Demand is growing because we see more broad-based adoption. It&#8217;s growing because agentic models use a lot more compute than legacy LLMs from a year or two ago. And on the supply side, we&#8217;re hitting all these constraints and bottlenecks related to supply chain in the semi space.</p><p>We&#8217;re entering a world where that gap is gonna continue to grow. And that&#8217;s all in this backdrop of what you said a minute ago, which is, the single digit millions of spend. And so I think we&#8217;re in this interesting environment where part of the world, is super early on that adoption curve, but at the same time we&#8217;re already hitting these constraints around compute.</p><p>If you want any semblance of an SLA from one of these model providers, you&#8217;re going to have to start committing to more meaningful spend. There&#8217;s this conflict and tension in betting your entire AI strategy on a single model provider.</p><p><strong>James:</strong> The enterprise is maybe the shoe that hasn&#8217;t dropped yet in terms of token demand, and my God, what happens once the, spenders start using, scale?</p><p>The flip side is that you&#8217;ll probably see a lot more efficiency in token consumption. You don&#8217;t need to do all your non-deterministic processing at runtime. More of it shifts to build time &#8212; software engineering, data ingestion &#8212; with deterministic execution at runtime. And we may see a meaningful share of inference move to edge hardware entirely.</p><p><strong>Ed:</strong> Think about models like OpenRouter. Companies now are about to sell a box &#8212; or a virtual box &#8212; that has a router for any frontier model on top, and then adds your own open source model on the box itself with H200s bundled in.</p><p>The idea is to make it very, very easy for people to build an agentic workflow, deploy it, and then actually maximize... I think we&#8217;re gonna move to a world of ROI per outcome. It&#8217;s no longer gonna be, are you automating me? But what is my ROI per outcome?</p><p>How does that look? And then there&#8217;s lots of other things involved in measuring success.</p><p><strong>Daniel:</strong> Obviously folks have concerns about costs and limiting those costs. But right now, those costs are the actual real costs businesses face when they start using this at scale.</p><p>So the demand curve is absolutely outstripping the supply curve when it comes to compute. Enterprise adoption is going to be more of an increase on a dimmer light switch.</p><p><strong>James:</strong> Enterprise adoption is always an increase on a dimmer &#8212; not a flip of a switch &#8212; which is why claims about AI impact on the bottom line feel like an attempt to be cute.</p><p>How could you expect otherwise? We&#8217;re what? Maybe a couple of years into the use of gen AI. How could you possibly expect that to have impacted enterprise operating income statements at this point?</p><p>The only impact on the income statement has been for some of those tech companies who are spending. I&#8217;m thinking about banks and pharma companies at the moment.</p><p><strong>Ed:</strong> As far as the ROI on that spend &#8212; questionable.</p><p><strong>Will:</strong> I do think we have small case studies where we&#8217;re starting to see it.</p><p>As one indicator: we have a portfolio company called Replit, which is an AI-native software creation platform. They allow anybody to create software using natural language. And what we&#8217;ve seen is in some cases the replacement of incumbent software providers where a non-technical user is able to create their own custom CRM system for a USD 100,000-a-year software license. The ROI on that is extraordinary. That&#8217;s like nothing you&#8217;ve seen from traditional software.</p><p><strong>Ed:</strong> I still think the super complex stuff &#8212; Workdays &#8212; when people say, &#8220;Hey, we can vibe code that stuff away,&#8221; I think people have moved on from that really.</p><p>Whether or not those companies are gonna be massively successful, who knows? But I do think the whole idea of vibe coding things, the maintenance becomes absolutely incredible for some of these people as well.</p><p><strong>Will:</strong> On one end, you have the bottom of the market that has simple use cases where they can vibe code their own CRM and displace incumbents. So I think that&#8217;s one end of the market.</p><p>The other end of the market in regards to enterprise adoption is just building more &#8212; where now you can use tools like Replit to build agents on top. And so it&#8217;s not that you&#8217;re gonna get rid of your incumbent provider, it&#8217;s just that you&#8217;re gonna build more agents on top of what you already have.</p><p>We see this primarily around internal tools, where to build a custom internal tool for your sales operations team or for your legal team, you had to either go work with a third-party software development agency to build that, and it would cost you hundreds of thousands or millions of dollars, or you had your internal software engineering resources, which would be expensive and you&#8217;re competing for internal resources.</p><p>Now, a non-technical person could go into a tool like Replit and build those agents or build those custom pieces of software on top of the existing architecture that you already have. And so I don&#8217;t think it&#8217;s a replacement for the incumbents in this case. I think rather it&#8217;s just gonna enable more software to be developed on top.</p><p><strong>Daniel:</strong> When we got together initially, there was a real fear-of-replacement moment for incumbents.</p><p>We&#8217;re more in an all-of-the-above moment now, where a lot of incumbents have the customers, they have the data they own &#8212; which, by the way, is one of the key things to be competitive in this moment.</p><p>And that&#8217;s actually what makes this really exciting from a venture perspective: these incumbents are your customers, and also your acquirers.</p><p>You also have this entire new world to go after as well.</p><p><strong>Ed:</strong> The most impressive thing was the idea that unicorn SaaS companies are all dead. This founder went all in on AI three months after ChatGPT came out, and today Salesforce announced it was buying it for &#8212; I don&#8217;t know &#8212; three and a half billion or something, which is above their ZIRP-era financing round. [1]</p><p>It takes very special companies, but maybe there&#8217;s a five percent chance that some of the very forward-thinking ones can create that kind of value. And combined with some of what Will said about Replit, there&#8217;ll be net new &#8212; more things banging on the system.</p><h3>Vibe coding vs. agentic software engineering</h3><ul><li><p>Vibe coding and agentic software engineering are distinct activities: one is a non-technical user building something simple; the other is a professional engineer with 2&#8211;10x leverage.</p></li><li><p>The non-technical user persona is larger than the professional developer pool &#8212; and that&#8217;s where the near-term adoption surge is coming from.</p></li><li><p>In enterprise, the term &#8220;vibe coding&#8221; doesn&#8217;t travel well; the equivalent is building skills and automations on top of existing platforms.</p></li><li><p>The abstraction layer keeps rising &#8212; but semantics still matters. Syntax can be generated; data models and business logic still require human understanding.</p></li></ul><p><strong>James:</strong> What&#8217;s the difference between vibe coding and agentic software engineering? When I say vibe coding, I mean someone who&#8217;s not particularly sophisticated building something &#8212; maybe it&#8217;s a reporting tool or analysis. Versus a software engineer using a set of 2x, 5x, 10x tools.</p><p><strong>Will:</strong> There&#8217;s a completely different user persona between the professional software developer that now has these agentic tools and the non-technical user who&#8217;s now empowered to create software. We&#8217;re seeing the adoption of the non-technical user &#8212; people in sales operations, people in legal, people in finance who have never written a single line of code, who don&#8217;t understand any JavaScript syntax &#8212; who are now empowered to create their own software in a way that is easy, simple, secure, compliant.</p><p>That&#8217;s where we&#8217;re really starting to see this adoption. The other important nuance here is that the pool of users who are non-technical is larger than the pool of users who are professional software developers. And so if you look at even a technology company, you might have fifty, sixty, seventy percent of the employees falling in a category that&#8217;s non-technical, and they are now empowered to go create software.</p><p><strong>James:</strong> I wonder if we&#8217;re gonna see the rise of strats. In banking we have the strats who were either former traders who learned how to code, or former coders who learned about markets &#8212; very fuzzy. I was wondering if that might happen in more sectors and more domains.</p><p><strong>Daniel:</strong> I agree that non-technical users are increasingly empowered to vibe code solutions. The problem is the influx of people who are vibe coding something, white-labeling it, and pitching it as a venture-fundable startup &#8212; and it&#8217;s not. Across sales enablement, marketing, the CFO stack, I can tell within five minutes of a pitch that there&#8217;s no defensible moat, nothing that takes particular expertise or meaningful compute to maintain. Buyer beware.</p><p>To use your strats analogy: to be a great trader takes years of domain expertise and longevity in the space. The same applies here. The people who can build something special are the ones with that depth. A vibe-coded sales stack with no moat is not that.</p><p><strong>James:</strong> what do you think of non-technical founders?</p><p><strong>Ed:</strong> I agree that more people building things is continuing to get more abstracted. I think the word &#8220;vibe code&#8221; and enterprise just does not really mix together &#8212; I don&#8217;t think you&#8217;re gonna walk into a CIO and say, &#8220;Let&#8217;s vibe code stuff.&#8221;</p><p>But it&#8217;s the same thing. It&#8217;s the same thing as what Will said &#8212; skills. The enterprises we talk to are using skills platforms, where you can type something into your AI of choice and say, &#8220;Hey, I want to build this, add this in, and then create a skill or automation.&#8221;</p><p>That is happening, and there&#8217;s gonna be hundreds of thousands of skills out there, and you&#8217;re gonna need to manage that and package it like software. You&#8217;re gonna need a version control system where there&#8217;s a skills repo for company XYZ, where these are the approved skills, and these are security vulnerabilities that can pop up, so let&#8217;s scan those skills.</p><p>What happens when Daniel changes something that Ed made? Is that better or worse? So how do you do an eval around that? So I, I think, I think we&#8217;re gonna be moving towards a world where skills become software,</p><p><strong>James:</strong> If you remember the late &#8216;80s, we went from assembler to C &#8212; people said software engineers would go away. The engineering continued.</p><p>And I wonder if two things are true here. Abstraction matters, but you still need to understand the data model, even if you&#8217;re programming in a very abstracted way.</p><p><strong>Ed:</strong> I think what you&#8217;re talking about is that you need specialized humans. Back to your earlier point &#8212; everyone wants to get automated, but they don&#8217;t know where to start.</p><p>Those specialists can help people understand what their workflows are so they can automate them. So you need specialized skill for that. And then two, you need specialized skill for evaluating whether a workflow is actually doing what it&#8217;s supposed to do. And then what happens, for example, when a model changes &#8212; is it actually gonna do better or worse?</p><p>People are gonna be needed, and even more specialized to understand those things. And I think people are finally understanding that right now.</p><p><strong>James:</strong> Sometimes I draw a distinction between syntax and semantics, and in an AI software engineering world, we can worry a lot less about syntax, but semantics still matters. So Will, let me ask you, are we being overly negative on vibe coding? Give us the other end of the case here.</p><p><strong>Will:</strong> First off, I know of several examples, including one where a company, built entirely on Replit is doing well over 100 million ARR, mostly enterprise revenue.</p><p>And so you, you can build real businesses, and I think we&#8217;ve gotten to a point in the technical maturity of the platforms like Replit where you have, implicit security, you can host on a private cloud instance. You hit all the enterprise check boxes, and a lot of the code that&#8217;s now hosted on tools like Replit specifically is as good as what you would get from a junior engineer. And so I disagree with the premise that you can&#8217;t build a venture-backable company on platforms like Replit.</p><p><strong>Ed:</strong> I&#8217;m getting my popcorn. This is fun</p><p><strong>Will:</strong> I agree that we as investors should operate with this premise that the cost to develop software is approaching zero over the next three, five, seven, ten years &#8212; just like the premium for having more software engineers is eroding. As that skill barrier is eliminated and the cost to build approaches zero.</p><p><strong>Daniel:</strong> Of course there&#8217;s going to be vibe coded businesses built on companies like Replit that are gonna be absolutely venture fundable and extraordinarily successful.</p><p>The barrier to entry to put a product in the market has gone to zero, which means there&#8217;s so much stuff that isn&#8217;t defensible and isn&#8217;t venture-backable. It&#8217;s a huge increase in the denominator without a proportional increase in the numerator.</p><p><strong>James:</strong> The percentage of effort associated with the core logic, relative to the effort required to fit into a broader enterprise environment, is decreasing. The pain is now in the integration: connecting to identity and access management, compliance, the whole stack.</p><p>So Ed, how do you think about this challenge of integration? Because in many places that will be the long pole in the tent.</p><p><strong>Ed:</strong> The last mile in the enterprise is the longest, and it&#8217;s probably getting longer. It&#8217;s not easy for a large bank or a healthcare firm or a large CIO to bet their reputation on deploying your agentic technology.</p><p>There&#8217;s a lot of stuff you&#8217;ve gotta pass &#8212; all the SOC compliance and everything else. What you&#8217;re seeing is the idea of these forward-deployed engineers showing up and just getting it to work. Part of that is a response to how hard the last mile is.</p><p>The model is: build product, then finish the last mile with people. And the learnings you get from it are invaluable. The key question is whether the most important data to own is not just the data you have to run the AI on top of, but the private evaluation of whether the outcome looked really good &#8212; because that is really the knowledge of your business. That&#8217;s what separates a P&amp;G from another marketing company.</p><p>Are these forward-deployed engineers going in there and helping you get those outcomes? And who owns the data? Are they giving it to you? Or are the forward-deployed engineers from the model providers themselves taking that data and using it to build vertical solutions?</p><p>That&#8217;s going to be the big battle. It&#8217;s what Satya calls hill climbing &#8212; reinforcement learning feedback. The question is: if you give that to a model provider and they&#8217;re helping you improve, is that the right trade-off to make?</p><p>I think we&#8217;re moving toward a world where people want to control their own evals &#8212; which means infrastructure on the edge, private models. We need a lot better open source coming down the line. It&#8217;s still not anywhere close to what the labs are providing, but that&#8217;s where we&#8217;re gonna move towards.</p><h3>Where the moat lives when code is free</h3><ul><li><p>If code approaches zero cost, the competitive advantage shifts to ontology, data models, and latent institutional knowledge &#8212; the things that can&#8217;t be scraped.</p></li><li><p>The right model for the right task matters more than any single model: orchestration layer bets are more durable than frontier-model bets.</p></li><li><p>Enterprises that hand their outcome data to model providers for convenience may be signing their own death certificate &#8212; private evals are the new proprietary asset.</p></li><li><p>Architecture commoditization is coming but isn&#8217;t here yet; scaling laws are still working and a step-change in model capability is 12&#8211;18 months out.</p></li></ul><p><strong>James:</strong> sometimes I wonder if code becomes free or close to free, but the ontology and the data model becomes the source of competition.</p><p><strong>Will:</strong> It&#8217;s very possible. This goes back to a point that we were talking about earlier, you probably don&#8217;t want to bet on a single model. It&#8217;s not just about cost, it&#8217;s also about, performance in different domains. And so I think that- that&#8217;s benefit of betting on something more at the orchestration layer, where, if you&#8217;re trying to do a task, we&#8217;re using software engineering as the example here, you might be writing, some more complex code, you might need a frontier model from one of the labs.</p><p>You&#8217;re writing simple front-end code, you could use an open source model. You&#8217;re doing a design task, maybe, Gemini or another model, from a, a different provider is better at that specific design task. So I think you&#8217;re seeing mixture of experts, to, solve these</p><p>As software code itself becomes a commodity, what matters is matching the right model to the right task &#8212; and everything else that isn&#8217;t captured by coding benchmarks: platform depth, integrations with Databricks or Snowflake, security scans, the full enterprise stack.</p><p><strong>Daniel:</strong> think having specialized humans that really have domain expertise combined with owning your data and your moat, somewhat model agnostic and having that&#8217;s what the future it&#8217;s a mixture of really great humans, different models, and, owning your data. I, companies that choose to allow their outcomes and their data to be out there for the LLMs to scrape, because they&#8217;re, they&#8217;re prioritizing speed, ultimately are, are signing their own death certificate.</p><p><strong>James:</strong> And does architecture get commoditized?</p><p><strong>Ed:</strong> Not anytime soon. So the answer is not today, but I wouldn&#8217;t be surprised, like in 18 months if we kinda get there, because this stuff is changing so quickly.</p><p><strong>Will:</strong> I don&#8217;t know, but if I were to place a bet, yes. Just look at the improvement in performance over the last three years. It doesn&#8217;t appear that we&#8217;re plateauing &#8212; in certain skills or certain domains it&#8217;s actually accelerating. It&#8217;s really hard to extrapolate out the next two, three, five years. But I think if the curve continues to look like it has the last three years, it&#8217;s very possible that architecture gets commoditized.</p><p><strong>Ed:</strong> In other words, scaling laws are actually working, and if you have the compute, it&#8217;s improving. Everyone I&#8217;ve talked to on the models they&#8217;re training now says it&#8217;s still moving in the same direction. Hasn&#8217;t been proven false yet.</p><p><strong>James:</strong> I&#8217;ll answer my own question and say my question was invalid. Any model requires context, so it depends on explicit information rather than latent information. Models will only get good at architecture to the extent that people using them figure out how to extract or capture the latent information they need.</p><p><strong>Ed:</strong> How much will they be willing to hand over of how their system is architected and actually operates to a model provider? That&#8217;s the question.</p><p><strong>James:</strong> Do they even understand enough to be able to write it down in such a way that it can be consumed? Taking latent information and turning it into explicit information is not a trivially easy task.</p><p><strong>Ed:</strong> It&#8217;s the last place that hasn&#8217;t been automated yet. If you&#8217;re thinking about most of the automations &#8212; it&#8217;s on the edges. IT ops themselves have not really been automated. Partly because people are afraid of AI just shutting things down. But I do believe we&#8217;re gonna move toward a world where there&#8217;s more trust with AI around automation of IT.</p><p><strong>James:</strong> Let me ask a related question, maybe one that&#8217;ll be controversial. So I, I, I got myself told I was up a tree because I offered the thought that we&#8217;re gonna see more strats in the future, more, convergence the line between, business optimization and technology execution.</p><p>But then I offered the hypothesis that it may be easier to teach software engineers about the business domain than it will be to teach people in the business domain enough about data models, for example, to, sufficiently engage. I don&#8217;t know whether you call it vibe coding or agentic software engineering.</p><p><strong>Daniel:</strong> I spend almost all of my train technical people on the business side of things. so, so I probably over-allocate to frustration in that department. So, maybe that skews my answer, that maybe it&#8217;s a little easier to teach business people, the software side, but I could go either way.</p><p><strong>James:</strong> Ed, what do you think?</p><p>Is it easier to teach a bus- a business analyst software engineering, or easier to teach software engineers about how to think about a business problem?</p><p><strong>Ed:</strong> I think the underlying models can be so good that what matters is the expert who knows what to prompt and ask. If you actually look at how to use LLMs today, it&#8217;s all about how you prompt &#8212; two of us could sit next to the same thing and get vastly different outputs if we&#8217;re trying to achieve the same goal.</p><p><strong>Will:</strong> I completely agree with Ed. There are so many nuances to different problem sets or workflows. The people who intimately understand them will have access to tools that can manage all the technical complexity.</p><p>One case study from us: we vibe coded our own custom LP portal, and my co-founder, who&#8217;s not technical but who&#8217;s been running all of our operations, built this in probably 12 hours. And it&#8217;s better than anything we could find from third parties. Daniel and Ed probably lament the challenges of fund admin more than anyone else.</p><p><strong>James:</strong> Nothing&#8217;s more fun than fund administration</p><p><strong>Will:</strong> it&#8217;s the great joy of life. there are so many little nuances to it that I think y- you just wouldn&#8217;t understand unless you&#8217;ve spent months or years in the trenches</p><p><strong>Ed:</strong> by the way, that goes back to my other point, is that your person that built it and you are the experts, and , you&#8217;re the ones that are gonna actually evaluate it as well. You&#8217;re the only ones that can keep evaluating everything else, right? So that&#8217;s kind of your workflow, that&#8217;s your model.</p><p>And, and your same model could be deployed at Daniel&#8217;s place and my place, but how we evaluate it and what successes might be different, right? And that&#8217;s kind of what I mean by the institutional knowledge and workflow that, that I think those private evals is so valuable to capture that</p><p><strong>Daniel:</strong> One of your great moats is domain expertise. domain expertise can be found on the business side, and it can also be found on the technical side. It depends on what problem you&#8217;re solving and who&#8217;s your constituency.</p><p><strong>James:</strong> I had a discussion with a bunch of 22-year-olds a couple months ago, and they were, you know, having the typical 22-year-old, &#8221;Oh my God, any job I might consider is going to be replaced by, by AI.&#8220; They asked what I thought would be a good thing to learn, and I said data modeling.</p><p>I don&#8217;t know whether that&#8217;s business domain or technology domain expertise, you both need to understand all the nuances of the business process, but there&#8217;s that, process of abstraction, that I think becomes incredibly important, which people who are only deep in the business domain don&#8217;t always get.</p><h3>Which sectors face the most disruption</h3><ul><li><p>Legal and accounting are the obvious targets &#8212; high information volume, largely objective outputs, limited customization requirements.</p></li><li><p>James&#8217;s less obvious answer: B2B interactions broadly. They haven&#8217;t changed in 15 years while B2C was transformed. Gen AI&#8217;s ability to ingest unstructured data makes this the next frontier.</p></li><li><p>Ed invokes Jevons: freed capacity can be absorbed by new demand. Companies that cut headcount fastest are already adding back &#8212; different kinds of people, more senior engineers, specialists.</p></li><li><p>Robotics is the adjacent disruption no one is talking about enough. Ed&#8217;s portfolio company has 500,000 hours of manipulation data and is deployed at four large manufacturers &#8212; the ChatGPT moment for physical AI is close.</p></li></ul><p>Okay, Daniel, predictions about which domain, technology domains do you think will be disrupted the most?</p><p><strong>Daniel:</strong> I&#8217;d say I&#8217;m still a big believer in places where there are largely objective answers to questions that require sifting through a lot of information. I think legal and accounting are two of the low-hanging fruits.</p><p><strong>Ed:</strong> I think, James, that everything is up for absolutely massive disruption right now. But I&#8217;m also a believer in Jevons paradox &#8212; because if things are cheaper and you can use AI more, you&#8217;re gonna be able to do more. And I do believe in a world of more productivity. The tech companies I&#8217;ve seen that have automated the fastest may have cut headcount and used AI as an excuse, but now they&#8217;re adding. They&#8217;re just adding different kinds of headcount &#8212; more senior engineers, different kinds of people. Perhaps the specialists you&#8217;re talking about.</p><p>So I think it&#8217;s gonna disrupt everything short term. The next two or three years will take a while to absorb the hit. But I believe in the longer term that we will actually be more productive as a society and generate more output with less cost. And hopefully you see those GDP growth numbers increasing.</p><p><strong>James:</strong> Will, what do you think?</p><p><strong>Will:</strong> I completely agree. If you look at any technology cycle throughout history, for the most part it&#8217;s led to wage increases, job creation, new goods &#8212; and I think the same thing will happen here over a ten to fifty to a hundred year time horizon. What we see in the next five years: the most disruption today is in two categories. Where incumbents have low-quality software products and have not innovated, you can now build that version yourself &#8212; and often it&#8217;s better, cheaper, and higher quality.</p><p>That&#8217;s our case with this fund: we built it ourselves because the incumbent alternatives were not high quality, they were very expensive, and there was a lot of low-hanging fruit.</p><p>I think the other area where we&#8217;re starting to see more disruption is in domains where software is highly customized &#8212; back to the point both Ed and Daniel made, which is that it&#8217;s really important to have deep domain knowledge specific to your workflows.</p><p>The way we build an LP portal might be different than the way Ed wants to build one, because he has nuances in his business and portfolio that we don&#8217;t. Where you have a high level of customization required to make software work for your business, there&#8217;s a lot of opportunity for disruption &#8212; both disrupting third-party software and disrupting the incumbents who have mediocre products that work okay for everyone but not great for anyone.</p><p><strong>James:</strong> it&#8217;s what I call the one size fits none challenge.</p><p>Ed, you said in the session that you looked to fund companies that were problem-obsessed rather than solution-obsessed because, you, you iterate through different solutions, but problems are eternal.</p><p>Messiest part of, the advanced economies is B2B interactions, and that&#8217;s not just CRM, but the broad scope of all the large, complicated businesses. , Over the past fifteen years, maybe twenty years, we&#8217;ve seen an utter transformation in B2C interactions.</p><p>But many B2B interactions look a hell of a lot like they did ten or fifteen years ago, and I think that, the, the ability of, gen AI to, to ingest complicated, unstructured data to transform those domains.</p><p><strong>Ed:</strong> I, I love that. And by the way, can I add one thing</p><p><strong>James:</strong> Please</p><p><strong>Ed:</strong> we didn&#8217;t talk about software and robotics,</p><p>I have a company. We&#8217;ve built our own LLM for robotics, with our own data, and we&#8217;ve proved that scaling laws actually work in robotics as well.</p><p>So I feel like we&#8217;re almost at that ChatGPT moment in robotics where a generalized robotic software model will be able to do a lot. So in other words, once upon a time where you would have to have 100 different robots or 100 different kind of brains operating and, and doing 100 different tasks, you can now have one.</p><p>And I can tell you this, that the market is moving so fast in that space, so manufacturing, pick, pack, and ship, auto manufacturing, all of those kinds of things are getting transformed. In the next three to five years, you&#8217;re gonna see a massive, massive dislocation in those markets as well</p><p><strong>James:</strong> Is that an LLM for robotics or is that a type of world model, right? I mean, are we moving from language to physics when we talk about that?</p><p><strong>Ed:</strong> there&#8217;s three different kinds. So the one that we have is a basically a foundational model for robotics. Other people are trying the world model approach, and what my company is doing is they&#8217;re getting their own data, right? There&#8217;s no Reddit for data.</p><p>They , ship these 3D-printed devices that goes on people&#8217;s hands that are very, cheap. we take video of people manipulating these things as if they had these grippers, and we&#8217;ve got 500,000 hours of data.</p><p>And now we&#8217;re deployed at four very large companies doing very complex manufacturing tasks all within two years. This is massively moving so fast. [3]</p><p>It&#8217;s basically building off the shoulders of giants? Because it&#8217;s already been done before, and now you&#8217;re applying it to a different realm,</p><p><strong>James:</strong> Daniel, how bullish are you breaking the, breaking the barriers between the physical worlds when we come to,</p><p><strong>Daniel:</strong> How can you not be bullish on it, right?</p><p><strong>James:</strong> What&#8217;s the pace, do you think?</p><p><strong>Daniel:</strong> One of the common themes we&#8217;ve discussed throughout this conversation &#8212; which, again, was part of the reason why I so enjoyed our in-person discussion &#8212; is the pace of innovation. It&#8217;s at a lightning speed.</p><p>Literally every week things are changing. Every day things are changing. That&#8217;s moving at a breakneck pace. But the integration of those changes &#8212; the integration of products that encapsulate some of this innovation into large businesses &#8212; is very slow.</p><p>And so I, we&#8217;re, we&#8217;re, we&#8217;re it&#8217;s, it&#8217;s one of those where you&#8217;re like in an F1 race where innovation is just lapping, the jogger, which is the, the, the enterprise integrator.</p><p>And, and so the question is how do you lean out the window and throw something that the jogger can actually digest? That&#8217;s, where the rubber hits the road, not to take the, this too far. But, that&#8217;s, where the bottleneck is.</p><p><strong>Will:</strong> Agree with, with, everything said here and that there&#8217;s an incredible amount of opportunity for AI in the physical world. you look at some domains in manufacturing where AI is now used to inspect batteries coming off an assembly line, and it can do it, ten times faster and, fifty times better than a human inspector can.</p><p>And that&#8217;s a job that humans don&#8217;t like doing. You wouldn&#8217;t want to sit under bright, bright fluorescent lights all day and look at batteries. So I think there are incredible amount of opportunities we&#8217;re already seeing implementation, the ROI is there. But I will say, I think that humanoids broadly is probably in bubble territory.</p><p>And I say that for two reasons. I think number one, we&#8217;re very early on the S-curve and that, the, the technology is not quite there. when you start to do things in the physical world and chain together different skills and make that work successfully in an enterprise environment, the, the, the success rate has to be very high in each skill.</p><p>You know, if your success rate is ninety-eight percent in one skill, ninety-eight percent in another, ninety-eight percent a third, you&#8217;re gonna fail a lot of the time because you multiply the probabilities together.</p><p>You really need to get to like ninety-nine point nine nine percent accuracy in each skill set or each domain in order for this to work reliably over time. The second problem I think we have in the humanoid space is people underestimate how hard it&#8217;s gonna be to scale up manufacturing.</p><p>Like you go talk to the team that, that scaled up manufacturing for the Model 3 at Tesla, like it&#8217;s a really hard thing to do to go from, you know, zero to scaled production of, of complex hardware products.</p><p>And I think the sort of view that we&#8217;re gonna be shipping millions of these in two years or three years is, is probably a bit shortsighted.</p><p><strong>Ed:</strong> One comment though. I, I agree with you on humanoids, but my company&#8217;s actually going after, robotic arms, So when you control the variables with just this and a gripper, you don&#8217;t need five joints on it to do things. that actually allows you to deploy much faster.</p><p>On the humanoid side, there&#8217;s so many more issues. Battery life is another one. Safety, what happens when the battery runs out? Does it fall on somebody? there&#8217;s so many issues there to, to your point.</p><p>The, more you constrain all the, variables and focus the processing power on the task at hand, the better off, you are in terms of deploying these things with real accuracy.</p><h1><strong>How enterprises should engage the startup ecosystem</strong></h1><ul><li><p>Routing startups through innovation teams is a trap &#8212; those teams are typically disconnected from the business owners who actually have the problem.</p></li><li><p>VCs are intermediaries in two directions: LP &#8594; founder, and founder &#8594; enterprise. The second role is underappreciated. They filter signal from noise, translate languages, and set expectations on both sides.</p></li><li><p>Enterprises build reputations too. Kick the tires on three companies and do nothing and VCs stop bringing deals.</p></li><li><p>The right frame for CIOs: decide where you want to sit on the adoption curve, then match the VC tier accordingly &#8212; seed investors for early bets, growth investors for proven businesses.</p></li></ul><p><strong>James:</strong> Let me pivot a little bit. I&#8217;d love to discuss a bit how enterprises, CIOs, CTOs, CSOs, others, should interact, with venture funds and venture-backed companies.</p><p>So Daniel, let me start with you. Advice would you have, for, technology executives or IT executives at big traditional enterprises as they engage with venture-backed companies and potentially as they engage</p><p><strong>Daniel:</strong> Absolutely. First and foremost, large businesses are structurally challenged when it comes to engaging with younger, earlier stage businesses. Some organizations have tried to address that through innovation departments or groups built to test technology. We tell our portfolio companies to avoid those like the plague, because they are typically disconnected from the business owners themselves &#8212; the folks who actually need solutions to solve problems. We as a fund try to serve as a bit of a filter there, because it&#8217;s really hard as a startup to knock on the door of a Fortune 1000 business and get any attention. Our hope is that when we help knock on those early doors with our portfolio companies, that comes with a vetting process, and an understanding that we&#8217;re gonna ask for that time only when there&#8217;s good ROI going both directions. We tell our portfolio companies to go directly to the person who has the problem &#8212; try to engage directly with the business unit.</p><p><strong>James:</strong> Will, what are the mistakes that large companies make when they interact with venture-backed, companies?</p><p><strong>Will:</strong> Trying to push companies through an innovation team that doesn&#8217;t really own the problem is often ineffective and wastes everyone&#8217;s time.</p><p>As an enterprise customer, you have to decide where you want to sit on the adoption curve. If you&#8217;re willing to be an early adopter and really partner with a company, I think that can be incredibly fruitful early in their life cycle &#8212; you&#8217;re gonna get a lot more attention and probably more customization specific to you.</p><p>If you&#8217;re not willing to put in that effort, if you&#8217;re not willing to view this as a partnership, you&#8217;re probably better off waiting until, other early adopters have embraced the startup and it&#8217;s gotten to this inflection point where it&#8217;s now a more mature company, with a fully baked product.</p><p>And then third, you know, a lot of, a lot of larger companies now have venture programs where they&#8217;re investing in startups, especially investing in startups that they&#8217;re customers of.</p><p>If you&#8217;re gonna have a venture program, connect that directly to the business unit that&#8217;s actually buying the software and, and understand why you&#8217;re making venture investments. Don&#8217;t just do it because you think it&#8217;s cool</p><p><strong>James:</strong> Okay, Ed, why is it so tough for, for large enterprises to engage with venture-backed companies?</p><p><strong>Ed:</strong> Filtering. There are just thousands and thousands of startups, and our job is to filter through all those and invest in the ones that make sense. When you partner with venture firms, you should partner with all different kinds &#8212; because there are folks that go super early, at inception. There are folks that go a click later. There are folks that invest after the company has USD 30MM of revenue.</p><p>You need to understand where you are on the innovation curve and figure out which venture capitalists you&#8217;re willing to engage with to see what they have.</p><p>And we as VCs have to be very careful as well. We&#8217;re not gonna throw something at an enterprise knowing full well that it&#8217;s gonna be an 18-month sales process &#8212; because that could also kill the startup, but also we don&#8217;t want to waste your time.</p><p>It&#8217;s all about trust and reputation. On both sides, you have to figure out what you&#8217;re willing to show an enterprise to say that it&#8217;s ready for deployment. Maybe the company and team have actually built something new, and they&#8217;ve done it 30 times before &#8212; so therefore there&#8217;s trust.</p><p>And on the enterprise side too, they build reputations as well. Because if you kick the tires for 18 months and do nothing with three companies, VCs will say, &#8220;Don&#8217;t ever go to them again.&#8221; And therefore that enterprise might miss out on innovation.</p><p>It&#8217;s a two-way street where you actually have to trust each other.</p><p><strong>James:</strong> How do you think about the filter? How do you think about who to speak to versus not to speak to?</p><p><strong>Ed:</strong> Well, it just comes down to people though, right? It&#8217;s all about the people, right? You want people that move very fast that actually can solve a problem today, but also presents a kind of vision to solve your problem 18 months from now.</p><p>And that&#8217;s what we look for, and hopefully you come to us and we can present the founders that actually do the same</p><p><strong>Will:</strong> The bar for speaking to somebody is very low. I&#8217;ll try to speak to as many people as possible. But for us, us to actually make an investment, we&#8217;re, we&#8217;re investing at a different stage, and so typically the companies that we&#8217;re investing in already have tens or even hundreds of millions in revenue. It&#8217;s a real business at that point, and the question is not will this succeed? Do they have product market fit?</p><p>The question is, what is the sort of revenue scale gonna look like five years from now? And what are the unit economics gonna look like five years from now?</p><p>We&#8217;re asking a fundamentally different question , than Ed or Daniel are when they&#8217;re making investments. We have a set of criteria that we filter to. We look for technologies that are inevitable, . There&#8217;s adoption, but we&#8217;re early on the S-curve. We look for markets that are default dominant, where an outcome is gonna be an oligopoly or a monopoly.</p><p>To Daniel&#8217;s point earlier, we don&#8217;t like markets that are commoditized, where you have hundreds of companies without any real moats. And then finally, we look for what we call dynastic DNA. It&#8217;s really about the people. Is this founder pursuing their life&#8217;s mission? Do they have the wherewithal and the fortitude to push through over the next ten, fifteen, twenty years to build a large, enduring business? Can they attract amazing people around them? Do they move at a high velocity?</p><p><strong>James:</strong> So it&#8217;s your job, Will, to, speak to people, but if you&#8217;re a CIO or a CTO, it&#8217;s like, well, it&#8217;s my job to keep the business up and running, and I got, some number of hours per week to go speak to people, and an infinite amount of demand to be spoken to. So what&#8217;s your advice for someone who in an enterprise, role</p><p><strong>Daniel:</strong> very nature of the venture business and the very nature of us having a funnel that ultimately results in a set of investments means when we are, making intros and trying to have conversations with corporate decision-makers,</p><p>if you ask for a busy person&#8217;s time and you do not use it effectively, you will not get it again. it is my, desire to be able to go back to the same folks time and time again when there&#8217;s an opportunity that&#8217;s relevant.</p><p>And so by the time I&#8217;m asking for the time of an enterprise CIO or an enterprise CISO, I&#8217;ve done my homework. I have done the work to know that even if it doesn&#8217;t result in an investment for us, it&#8217;s going to be a good use of both of their times.</p><p><strong>Ed:</strong> It&#8217;s always not us pitching them. I find the most value is when I talk to CIOs or CSOs and say, &#8221;Hey, what&#8217;s top of mind for you?&#8220; Maybe once a quarter I have, like, a dozen folks I&#8217;ll catch up. &#8221;What&#8217;s top of mind for you? What are the biggest problems you&#8217;re seeing? What are the existing, incumbent vendors not providing for you? What do you wish you had? What are you thinking about building?&#8220; Right?</p><p>Because a lot of the things that startups end up creating are things that companies want to build themselves, right? So I think that&#8217;s part one. So once we understand that, we can say, &#8221;Hey, I&#8217;ve got this one or that one.</p><p>We funded a company, um, you know, like a year and a half ago in the agent identity space. I, I walked into a very large bank and we just said, &#8220;Hey, look, I would love your feedback.&#8221; And, and they had eight people in the room. We spent an hour together. We, we mapped out what our architecture would look like, what problems we&#8217;d solve.</p><p>And then guess what? We went away, built stuff, raised rounds of funding, came back a year later &#8212; not only did we show that company that we had built everything, but we also showed them what the forward roadmap was.</p><p>And I remember as I was leaving the room, three of them were huddling in the corner and saying, &#8220;Holy shit, did you see what they built in the last, you know, year?&#8221; We built it really fast, and then we had a future vision that kind of aligned with theirs. Another thing: we&#8217;re not expecting a sale. We want feedback. Why wouldn&#8217;t you provide feedback and spend the time? And then if we come back and make the mark, great.</p><p><strong>James:</strong> You assume that VC funds serve as an intermediary between limited partners and founders. They channel investment to companies. But what I&#8217;m hearing here, and have heard in previous discussions, is you&#8217;re just as much an intermediary between startup companies and the enterprise &#8212; helping founders understand the enterprise, and helping the enterprise understand how to engage with startups.</p><p>Is that, is that a fair way of thinking about it?</p><p><strong>Daniel:</strong> Absolutely. I have two track records. I have the track record to my LPs, and I have the track record to the entrepreneurs we back. And the track record that is for the entrepreneurs we back is: how many customers did I help you get?</p><p>How many versions of your product did I help you think about? how many key hires did I help you with? those are all critical things that are on the company support side of things. and it really involves being an intermediary with the enterprise, and understanding how to translate different languages.</p><p>A startup speaks a different language than a large enterprise. You gotta have somebody in the middle ideally making that translation</p><p><strong>Ed:</strong> Look, I&#8217;ll toot our own horn here for the three of us &#8212; I&#8217;ve been doing this for 30 years, and not every venture firm does this. So if you&#8217;re a founder building in this space, come to guys like us who actually do this every single day, because we learn a lot during the process.</p><p>But all I&#8217;d like to say is our job is to help it, help you make it an unfair fight against your competitors so that, so that when you get funding from us, that we&#8217;ll , accelerate your path to your next round of funding and kind of product market fit or post-product market fit, depending on the stage.</p><p>One or two influential customers at the beginning of a company&#8217;s journey, like, of their first five customers, can actually reap tremendous dividends, create so much value, multipliers of value based on the contract size.</p><p>By the way, the contract size does not have to be massive. perhaps, James, that enterprise gets a massive discount in year one. The point is those referenceable customers are so massive for the success of the business because what you really want that CIO or CTO doing is talking to the next four or five large customers coming down the pike.</p><p><strong>James:</strong> Will you invest in s- companies a little bit further on in the journey? How is your experience or your model similar or different?</p><p><strong>Will:</strong> For a company that&#8217;s just starting out, having an Ed or a Daniel on your cap table is really important. It&#8217;s almost like they&#8217;re an extension of your founding team, to the extent that they can broker these relationships and help you navigate the enterprise. For us, the set of problems that a founder is facing is different.</p><p>They have often overwhelming market pull. The problem is not finding customers, the problem is scaling up the organization to meet the demands that you have. And so we try to help out a different way. It&#8217;s always great to bring customers. We try to do that where it makes sense. But I think often it&#8217;s more about talent.</p><p>It&#8217;s bringing in people who can scale, help you scale from 100 million in revenue to a billion in revenue. It&#8217;s more sort of strategic finance, and so how do you think about bringing in some of the larger crossover funds that will be shareholders, through an IPO and into the public markets?</p><p>It&#8217;s thinking about the next act. You have one product line that&#8217;s extraordinarily successful. You know, how do you start introducing a second product line in parallel, your second act? And so often we&#8217;re helping founders, navigate a different set of challenges than, than Daniel or Ed are.</p><h1><strong>Should you leave to found a company?</strong></h1><ul><li><p>The most compelling founding stories come from insiders who experienced a gap, built a workaround, and realized others had the same problem. Coralogix is the archetype.</p></li><li><p>Ed&#8217;s checklist: Is this a market of one, or a market of many? Have you talked to peers at other companies? Who owns the technology? Who are you bringing with you?</p></li><li><p>Domain expertise is necessary but not sufficient. The ability to abstract &#8212; to see that what solved your company&#8217;s problem could solve a category &#8212; is what separates a founder from someone who built a useful internal tool.</p></li><li><p>Will&#8217;s criteria at the growth stage: problem obsession, grit, and &#8220;dynastic DNA&#8221; &#8212; the willingness to push past a billion-dollar exit toward a hundred-billion-dollar company.</p></li></ul><p><strong>James:</strong> So not infrequently, I have people working in enterprise technology organizations come to me and say, &#8220;Hey, I&#8217;ve done something really cool. I think maybe I should build a company out of this.&#8221; Maybe the grass is greener outside. Daniel, how do, how should someone think about that,</p><p><strong>Daniel:</strong> Some of our most successful investments have come from that exact process where somebody is, at a business, they are experiencing a gap or a problem, and given their knowledge of the problem, their knowledge of the domain, decide, &#8220;Hey, I&#8217;m actually going to leave the company, and I&#8217;m going to build the solution I was looking for,.&#8221;</p><p>And, one of the, a, a really exciting company where we were involved from day one in the observability space called Coralogix is literally exactly that story, where , the founding team there was literally a product team at another business that built a solution they couldn&#8217;t find to buy. That&#8217;s a , very compelling, thesis. the challenge is a lot of times that thesis isn&#8217;t always right. The best thing to do is talk to guys like us, right? , Have a conversation while you&#8217;re still, ideating. Ed gets involved a little earlier than we do, we regularly meet with and advise founders that, aren&#8217;t yet founders.</p><p>They haven&#8217;t yet left their job. They don&#8217;t exactly know what they&#8217;re doing, but they&#8217;re really smart. They know their domain. They want to stay in the domain, and we want to stay close to them.so you gotta test the thesis, but you gotta test it with a toe in the water, not, jumping in the whole way, y-before that.</p><p>I, I, I always, when, when founders come to me and they say that they&#8217;re onto something big, I always say, &#8220;Show me your work. what validation did you do to, to achieve that conviction?&#8221; and to the degree we can be helpful in building that case with the founder that leads into an investment, great. but you gotta do the work to validate.</p><p><strong>James:</strong> Ed, what do you think? And in particular, how should someone, what questions should someone ask themselves or him or herself,</p><p><strong>Ed:</strong> There are a few lenses. You should have conversations with folks who do this. two is I think you should think about, is my solution a market of one, a market of a few, or a market of a many, ? Because I, I&#8217;ve talked to lots of folks building stuff, and they think they&#8217;re on their aha moment, but really their organizat- organization is so special that, I, I think it&#8217;s a snowflake, right?.</p><p><strong>James:</strong> Abstraction is important</p><p><strong>Ed:</strong> Do your homework, right? Also understand what&#8217;s in the market, &#8216;cause a lot of times also when you&#8217;re internal, you don&#8217;t understand what the other startup vendors are doing or what the other large incumbents are doing.</p><p>Like, why? Why is this built? Why&#8217;d you have to build this internally, doing a startup is really effing hard. You have to be absolutely stupid, insane, and crazy to go do a startup right now, and so I&#8217;m just warning you right now, it&#8217;s not all glory. It&#8217;s actually mostly 99% pain and 1% glory, right?</p><p>And, and so, so you better be pretty, pretty sure about that when you go out. And so let&#8217;s just have this conversation. A few things I&#8217;ll ask, will be understanding how&#8217;d you come to the conclusion that there&#8217;s just more than you. Have you talked to other people at other companies, your peers, for example, at other companies that might want to buy this solution? Two is who owns the technology? Are you gonna actually go leave and rebuild it yourself, or are you gonna spin this out of a larger org, and then perhaps maybe give them some equity, which also opens this a whole, a whole new ball of wax. I&#8217;ve tried that before, and that ends up becoming a very long legal nightmare.</p><p>I&#8217;m not advocating for that. You might be better off just going out and creating your own thing. If you&#8217;ve been locked in a corporate, corporate environment for, for 10, 15 years, man, I, I don&#8217;t know if you can... if you have even the stomach, that you can be a founder. so prove it to me, man. your, your salary&#8217;s gonna be 1/10th and 1/15th what you had before. It&#8217;s all gonna be about the equity. Who are you bringing with you? i-i-if you tell me, &#8220;I got five or six people I&#8217;m bringing with me&#8221; , I&#8217;m gonna know that you can recruit people, right?</p><p>I mean, those are the things you&#8217;re gonna have to think about once you get past even the does this make sense.</p><p><strong>James:</strong> Will, what are, what are, what&#8217;s your observations about people who make for successful founders?</p><p><strong>Will:</strong> I think first off, you have to be obsessed with a problem that you&#8217;re solving. I think that&#8217;s, that&#8217;s table stakes. And I think second, you&#8217;ve gotta have the grit and the fortitude to push through all the pain, all the moments of near death, all the suffering, and keep going and going. And for us at least, in the stage we&#8217;re investing at, we&#8217;re investing not because we think this could be a billion-dollar company.</p><p>Often it already is a billion-dollar company. It&#8217;s because we think it could be a $100 billion company. And any rational founder that got a billion-dollar offer , would sell their company and make tens or hundreds of millions of dollars and go retire.</p><p>It&#8217;s the people that, that have that fortitude, that grit, that drive to keep pushing farther and farther. And I think, it, it can happen. You look at one example is Daniel Dines, the founder of UiPath. he worked at a big corporate before, and, he decided to leave and, and start UiPath, and it took him, I think it took him, if I&#8217;m not mistaken, like six years to go from, zero to a million in ARR.</p><p>It was just this brutal slog. And so, you know, you look at that, and then obviously they went from, one to 100 million very quickly and, and now it&#8217;s a, it&#8217;s a large public company. And that&#8217;s the journey you have to expect going into this.</p><p><strong>Daniel:</strong> Well, and also someone who can win, right? I, one, we talked about problem-obsessed. Absolutely. We talked about grit. Absolutely. we define it internally as like, do we think someone can win in their market? because it&#8217;s not enough to just have a good product.</p><p>It&#8217;s not enough just to, you know, have one of these pieces. You have to have all of the pieces, and you have to be resilient the entire way.</p><p>It&#8217;s actually one of the reasons why we focus on the Israeli ecosystem. , Really resilient founders, that have to persevere and go through a lot, that deal with real-world problems at a much younger age, that do their national service, that deal in real-world environments. and it creates a, a bit of a different type-built entrepreneur, someone that can, get up when they&#8217;ve been, you know, pushed over and, you know, when the market punches you in the face, you gotta get up. and that is , critical to being a successful founder.</p><p><strong>James:</strong> All right. Let me ask for final words.</p><p><strong>Will:</strong> I would say if you are a CIO or CTO trying to figure out where to spend your time, look inward. A lot of the most successful AI companies we&#8217;re seeing, at least at the application layer, are seeing incredible pull from the bottom up rather than being pushed top down. Go to your functional leaders, figure out where their problems are, figure out where they have pull, and focus your time and energy there rather than filtering all the people banging on your door trying to sell solutions top down.</p><p><strong>Ed:</strong> Um, I would say that the time is now, right? Just don&#8217;t wait. Start small, start somewhere, just get rolling right now, and then don&#8217;t be afraid to throw things away. because I can promise you that by the time this podcast probably comes out, I know you&#8217;re fast, James, but the world may turn again one more time or two more times, right?</p><p>So whatever we say might be 90% irrelevant and 10% relevant right now. So I think the world&#8217;s just moving so fast. If I were a CEO or CIO, I would just build my own stuff on the weekend just to really understand the power of it.</p><p>That&#8217;s the only way you get to know these things</p><p><strong>Daniel:</strong> We&#8217;re entering a really interesting moment where there&#8217;s not such a stigma anymore to try new things.</p><p>Companies need to look inward &#8212; to Will&#8217;s point &#8212; to really build the capabilities to integrate. And I think there&#8217;s openness now to try new stuff.</p><p>You&#8217;re not gonna get fired anymore for giving something a try. And I think that makes it a really exciting time to be an enterprise executive who can, to Ed&#8217;s earlier point, really put your foot on the gas on productivity.</p><p><strong>James:</strong> Thank you all. This has been terrific.</p><h3>Implications for CIOs and CTOs</h3><p>Three things you probably expected going in: VCs are optimistic; enterprise AI adoption is early; legal and accounting are the obvious targets. One thing you probably didn&#8217;t: enterprises build reputations with venture funds too. Bring three companies through your procurement process, commit to nothing, and the introductions stop. The world is far enough from 2007 that waiting is no longer neutral. It has a cost now.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.prosaictimes.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading Prosaic Times &#8212; subscribe to receive every issue!</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p></p><h3>Footnotes</h3><p>[1] Ed is referring to Fin, the AI customer service company formerly part of Intercom. Salesforce <a href="https://investor.salesforce.com/news/news-details/2026/Salesforce-Signs-Definitive-Agreement-to-Acquire-Fin/default.aspx">announced the acquisition</a> for USD 3.6B &#8212; above Fin&#8217;s ZIRP-era financing round, as Ed notes.</p><p>[2] The imbalance is structural, not cyclical, and the data supports Will&#8217;s claim. On the demand side, <a href="https://epoch.ai/data">Epoch AI data</a> shows frontier model training compute has been expanding at roughly 5&#215; per year since 2020. On the supply side, the global stock of AI chips is growing at approximately 3.4&#215; per year &#8212; aggressive, but mathematically insufficient to close the gap.</p><p>The constraint is no longer primarily silicon: transformer lead times have stretched from one year to five years (<a href="https://www.bvp.com/atlas/roadmap-the-ai-data-center-stack">Bessemer Venture Partners</a>), and <a href="https://www.rand.org/pubs/research_reports/RRA3572-1.html">RAND Corporation projections</a> show single training runs scaling toward 1 GW of power per site by 2028 &#8212; approximately the output of a nuclear reactor.</p><p>Broadcom&#8217;s Q2 disclosures illustrate the production gap directly: bookings for AI accelerators surpassed USD 30B against USD 10.8B in actual shipments. The one credible counter is algorithmic efficiency improvement (~3&#215; per year), which could flatten demand before infrastructure matures &#8212; but that remains a scenario, not a trend. For the physical infrastructure constraints in more detail, see <a href="https://prosaictimes.substack.com/p/the-largest-deployment-of-capital">my conversation with Harqs Singh of InfraPartners</a>.</p><p>[3] Ed is referring to <a href="https://boldstart.vc/news/generalistai-when-robots-start-to-improvise-welcome-to-boldstart/">GeneralistAI</a>, a foundation model company for robotics &#8212; Boldstart Ventures portfolio. Ed is an investor.</p>]]></content:encoded></item><item><title><![CDATA[Is Mythos the Sputnik moment for AI in enterprise technology?]]></title><description><![CDATA[The imperative for spec-driven, immutable engineering, verified by adversarial automation rather than manual bottlenecks]]></description><link>https://www.prosaictimes.com/p/is-mythos-the-sputnik-moment-for-b8a</link><guid isPermaLink="false">https://www.prosaictimes.com/p/is-mythos-the-sputnik-moment-for-b8a</guid><dc:creator><![CDATA[James Kaplan]]></dc:creator><pubDate>Sat, 20 Jun 2026 11:10:55 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/202829526/c9912ead18bacc03819396934924b22f.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p><span>On October 4, 1957 the Soviet Union launched Sputnik 1, the first man-made object to achieve Earth orbit. In the </span><a href="https://airandspace.si.edu/stories/editorial/remembering-tom-wolfe-and-right-stuff">Right Stuff</a><span> [1], Tom Wolfe described the shock and dislocation felt by American elites. They had built the arsenal of democracy and exploded the atomic bomb. And now a backward former supplicant, one that required American trucks to hold off the Wehrmacht, had beaten them into space. What did the United States have? An underfunded, shambolic collection of civilian and military programs designed to satisfy bureaucratic and diplomatic imperatives rather than for speed and effectiveness.</span></p><p><span>They responded. Then Senate Majority Leader Lyndon Johnson said Americans would not </span><a href="https://www.youtube.com/watch?v=1dSkX9VySOI">go to sleep by the light of a Communist Moon</a><span>. The </span><a href="https://www.nasa.gov/history/65-years-ago-the-national-aeronautics-and-space-act-of-1958-creates-nasa/">National Aeronautics and Space Act of 1958</a><span> created the National Aeronautics and Space Administration (NASA) with responsibility for the American space program. The </span><a href="https://www.britannica.com/topic/National-Defense-Education-Act">National Defense Education Act of 1958</a><span> sought to dismantle John Dewey&#8217;s legacy in American education, pushing schools to replace &#8220;life adjustment skills&#8221; with set theory and symbolic logic. Less than 12 years after Sputnik, Neil Armstrong and Buzz Aldrin </span><a href="https://www.youtube.com/watch?v=cwZb2mqId0A">walked on the surface of the Moon</a><span>.</span></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://prosaictimes.substack.com/p/is-mythos-the-sputnik-moment-for?utm_source=substack&amp;utm_medium=email&amp;utm_content=share&amp;action=share&amp;token=eyJ1c2VyX2lkIjoxNjI2Njg1NSwicG9zdF9pZCI6MTk0NzA5MjUwLCJpYXQiOjE3ODE5NTM1NjksImV4cCI6MTc4NDU0NTU2OSwiaXNzIjoicHViLTcwNDE4NjEiLCJzdWIiOiJwb3N0LXJlYWN0aW9uIn0.BHKwEp_SwOrUp9KxTCnDAdKPcIch2WbYycUAYrFhLPY&quot;,&quot;text&quot;:&quot;Share&quot;,&quot;action&quot;:null,&quot;class&quot;:&quot;button-wrapper&quot;}" data-component-name="ButtonCreateButton"><a class="button primary button-wrapper" href="https://prosaictimes.substack.com/p/is-mythos-the-sputnik-moment-for?utm_source=substack&amp;utm_medium=email&amp;utm_content=share&amp;action=share&amp;token=eyJ1c2VyX2lkIjoxNjI2Njg1NSwicG9zdF9pZCI6MTk0NzA5MjUwLCJpYXQiOjE3ODE5NTM1NjksImV4cCI6MTc4NDU0NTU2OSwiaXNzIjoicHViLTcwNDE4NjEiLCJzdWIiOiJwb3N0LXJlYWN0aW9uIn0.BHKwEp_SwOrUp9KxTCnDAdKPcIch2WbYycUAYrFhLPY"><span>Share</span></a></p><p>Could Anthropic&#8217;s recent announcement of how Mythos can identify and exploit cybersecurity vulnerabilities create the Sputnik moment that will spur companies to use AI to change the way they operate enterprise technology?</p><p>The risks are real, and companies will need to move beyond buying tools and to build an agentic governance loop that uses a living graph of the environment to provide the context for spec-driven, immutable engineering, verified by adversarial automation rather than manual bottlenecks -- and then sustain and expand this change over time.</p><ul><li><p>Despite early indicators of transformative improvements, AI adoption in running enterprise technology has been shallow.</p></li><li><p>Despite some fear-mongering, the impact of AI on the cybersecurity balance of power between attackers and defenders has been muted to date -- Mythos and subsequent models could change that.</p></li><li><p>Mythos and subsequent models could dramatically improve companies&#8217; cybersecurity posture in the medium term -- but they will need to use AI to accelerate their enterprise technology metabolism dramatically.</p></li><li><p>Of course, the idea of a Sputnik moment is as much a warning as a call to action -- one-time programs are a lot easier than sustained cultural change.</p></li></ul><h4><strong>AI adoption in running enterprise technology has been disappointingly shallow</strong></h4><p><span>Technology engineering and operations is one of the most exciting applications of AI for large companies. Large language models excel at interpreting and generating the structured content used in software engineering or technology configuration. AI can replace </span><a href="https://prosaictimes.substack.com/p/vibe-coding-doesnt-eliminate-the">procedural programming with declarative programming</a><span> [3], via spec-driven development. Agentic processes can better accommodate the edge cases and exceptions that have historically bedeviled efforts to automate technology operations. The early results have been exciting. My McKinsey colleagues have found that using AI to reinvent engineering processes can </span><a href="https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/unlocking-the-value-of-ai-in-software-development">double team throughput.</a><span> AWS has started to use </span><a href="https://aws.amazon.com/blogs/devops/leverage-agentic-ai-for-autonomous-incident-response-with-aws-devops-agent/">agentic processes to reduce incident resolution</a><span> time by three-quarters in some cases. Applied ruthlessly, AI could </span><a href="https://prosaictimes.substack.com/p/lessons-from-design-in-maximizing">transform the economics of enterprise technology</a><span>.</span></p><p><span>Yet adoption has been shallow. In last year&#8217;s </span><a href="https://dora.dev/research/2025/dora-report/">DORA State of DevOps report</a><span>, 90 percent of software practitioners said they use AI in some way, but most never used it in agent or autonomous mode and only 17 percent used it every day. The situation is no better with the cybersecurity team. According to a </span><a href="https://www.sans.org/blog/how-integrate-ai-modern-soc">SANS report</a><span>, Security Operations Centers use AI/ML tools, but don&#8217;t integrate them into their processes:</span></p><blockquote><p>AI is present inside the SOC but not operationalized. Analysts use it informally, often with mixed reliability, while leadership has not yet established a consistent model for where AI belongs, how its output should be validated, or which workflows are mature enough to benefit from augmentation.</p></blockquote><p><span>All this accords with my own observations: technology teams use AI as a tool to generate a code snippet or research an issue, rather than a lever to rip toil out of the way they do business. Why is this? The technology is still relatively new. Teams may be cautious or may not have the mental bandwidth required for change. Vendors have promised just installing a tool will solve their problems. And CIOs have </span><a href="https://prosaictimes.substack.com/p/just-like-parents-cios-must-be-demon">not built the institutional support</a><span> required to fund and prosecute the required change.</span></p><h4><strong>Mythos could change the cybersecurity balance of power between attackers and defenders</strong></h4><p><span>Since OpenAI released ChatGPT 4.0 in 2023 the great and the good have warned us about AI-enabled cyberattacks. The World Economic Forum said that </span><a href="https://www.weforum.org/stories/2024/02/what-does-2024-have-in-store-for-the-world-of-cybersecurity/">specialized language models would allow hackers to get around endpoint security devices</a><span>. The FBI said that AI would allow criminals to </span><a href="https://www.ic3.gov/PSA/2024/PSA241203">scale fraud schemes</a><span> in a way that would swamp law enforcement. The UK&#8217;s National Cyber Security Centre said that GenAI </span><a href="https://www.ncsc.gov.uk/news/global-ransomware-threat-expected-to-rise-with-ai">lowers the barrier to entry for novice hackers</a><span> allowing them to use vectors previously only available to experts. Some predictions approached fear-mongering -- sentient malware and HackerGPTs collapsing cybersecurity defenses. [4]</span></p><p><span>The worst...has not happened. I checked this morning, and the digital world continues to function. Only </span><a href="https://www.ibm.com/downloads/documents/us-en/131cf87b20b31c91">16 percent of companies suffering breaches</a><span> said they saw evidence of AI in prosecuting the attack. According to the </span><a href="https://www.verizon.com/business/resources/T16f/reports/2025-dbir-data-breach-investigations-report.pdf">Verizon Data Breach Investigations Report</a><span> attackers have been just as dilatory as enterprises in using AI to reinvent their business processes:</span></p><blockquote><p>It turns out the state-sponsored actors are just like legitimate organizations in their GenAI implementation life cycles. Attempts are being made, maybe some improvements are being found, but no one is revolutionizing anything yet.</p></blockquote><p><span>At least as of 2024, GenAI tools could potentially assist attackers, but could not execute sophisticated attacks for them. One analysis found that GPT-4 only achieved a </span><a href="https://arxiv.org/abs/2404.08144">7 percent success rate in exploiting vulnerabilities</a><span> without clear human guidance.</span></p><p>Even before Mythos, the potential and the direction of travel have been worrisome. The structural factors that make LLMs effective in building and running systems also apply in compromising them.</p><ul><li><p><span>Intel matters in undertaking a cyberattack. LLMs have breadth of vulnerability knowledge no human analyst can read or retain -- </span><a href="https://www.gov.uk/government/publications/international-scientific-report-on-the-safety-of-advanced-ai">LLM training data spans public CVEs, security research, disclosed exploits, and documented attack strategies.</a></p></li><li><p>Success requires patience. Agents will cycle through potential vectors without boredom or fatigue.</p></li><li><p><span>System compromise provides agents with a </span><a href="https://arxiv.org/html/2603.16969v1#:~:text=These%20systems%20typically%20model%20network,automate%20incident%20response%20%5B15%5D%20.">clear objective function</a><span> they can optimize against.</span><br><br><span>As a result, researchers have started to demonstrate that </span><a href="https://arxiv.org/abs/2406.01637">teams of LLM agents can cooperate to exploit zero-day vulnerabilities</a></p></li></ul><p><span>Then came Mythos. Obviously we should be restrained in thinking about the implications of any software that isn&#8217;t generally available yet. And we&#8217;ve heard the </span><a href="https://openai.com/index/better-language-models/">too dangerous to release warning</a><span> before. In its public statements, Anthropic said that Mythos had identified thousands of high-severity vulnerabilities across major operating systems and browsers&#8212;including legacy flaws like a </span><a href="https://www.google.com/search?q=https://www.anthropic.com/news/claude-mythos-cyber-assessment">27-year-old bug in OpenBSD</a><span> that evaded decades of manual audits. The model further demonstrated the ability to build </span><a href="https://www.anthropic.com/claude-mythos-preview-system-card">complete, working exploits</a><span>. Mythos can independently &#8220;chain&#8221; multiple vulnerabilities to gain a foothold, escalate privileges, and move laterally through a network, effectively allowing users with no formal security training to execute professional-grade, multi-stage cyberattacks at machine speed. Finding zero-days may get the headlines, but the ability to scale and operate autonomously </span><a href="https://insights.integrity360.com/360-view-anthropic-mythos-ai-hype-or-the-future-of-cybersecurity#:~:text=%E2%80%9CThe%20reported%20evaluations%20of%20Mythos,organisations%20with%20weak%20security%20postures.%E2%80%9D">may create the real risk</a><span>.</span></p><p><span>This probably won&#8217;t realize the most dire predictions of 2024. [5] Several commentators have observed that a model&#8217;s ability to identify vulnerabilities and form plans doesn&#8217;t mean it will succeed in the face of </span><a href="https://www.redhat.com/en/blog/navigating-mythos-haunted-world-platform-security">sophisticated defenses</a><span> (including the ones they have developed). But how many companies have sophisticated defenses like </span><a href="https://www.threatlocker.com/blog/the-claude-mythos-preview-proves-now-is-the-time-for-zero-trust">zero-trust in place comprehensively</a><span>? And one compromise in the software supply chain could disable hundreds or thousands of institutions. Naturally, Anthropic and other frontier labs will seek to implement </span><a href="https://www.tanium.com/blog/claude-mythos-security-risks/">guardrails</a><span> that limit attackers&#8217; ability to exploit their models. The guardrails will not be perfect. And they will not apply to many of the open-weight models that will likely have </span><a href="https://www.tanium.com/blog/claude-mythos-security-risks/">Mythos-level capability</a><span> within, maybe, a year.</span></p><h4><strong>Mythos and subsequent models could dramatically improve companies&#8217; cybersecurity posture in the medium term. Could, not will.</strong></h4><p><span>After the Mythos announcement, American business and governmental elites acted. Anthropic delayed general availability of Mythos and launched </span><a href="https://www.anthropic.com/glasswing">Glasswing</a><span>, giving early Mythos access to leading technology institutions so they could use it to identify vulnerabilities. Treasury Secretary and Federal Reserve Chair Jerome Powell </span><a href="https://www.sullcrom.com/insights/memo/2026/April/Treasury-Secretary-Federal-Reserve-Chair-Warn-Bank-CEOs-About-Cybersecurity-Risks-Posed-Anthropics-New-AI-Model">called banking CEOs to Washington DC</a><span> so they could urge them to take the risk seriously -- I expect they were </span><a href="https://www.constellationr.com/insights/news/jpmorgan-chase-goldman-sachs-anthropics-mythos-ai-cyber-risks#:~:text=With%20the%20help%20of%20the,are%20accelerating%20our%20investment%20in.%22">pushing on an open door</a><span>. Technology companies like </span><a href="https://aws.amazon.com/blogs/security/building-ai-defenses-at-scale-before-the-threats-emerge/">AWS</a><span>, </span><a href="https://www.microsoft.com/en-us/security/blog/2026/03/20/cti-realm-a-new-benchmark-for-end-to-end-detection-rule-generation-with-ai-agents/">MSFT</a><span>, </span><a href="https://www.crowdstrike.com/en-us/blog/crowdstrike-founding-member-anthropic-mythos-frontier-model-to-secure-ai/">CRWD</a><span> and </span><a href="https://blogs.cisco.com/news/rising-to-the-era-of-ai-powered-cyber-defense">CSCO</a><span> reported that they were using Mythos to harden their products.</span></p><p><span>In the medium term, Mythos (and subsequent models) could provide a dramatic uplift in cybersecurity defenses. Companies spend fortunes each year scanning their code for vulnerabilities [6] -- Mythos-type capabilities will provide a level of transparency into vulnerabilities that we never could have imagined before. Most companies of any size do penetration testing, [7] but only the biggest tech spenders have dedicated </span><a href="https://www.bankofengland.co.uk/financial-stability/operational-resilience-of-the-financial-sector/cbest-threat-intelligence-led-assessments-implementation-guide">red-team operations</a><span> that figure out how a sophisticated attacker might compromise their environment. Mythos-type models should make this capability available to a much broader range of companies.</span></p><p><span>They may also revolutionize cybersecurity risk management and cyber insurance. Cyber-risk valuation frameworks like FAIR have </span><a href="https://www.kovrr.com/blog-post/cyber-risk-quantification-crq-models-how-to-choose-the-right-one">foundered on the problem of likelihood assessment</a><span>. Practitioners should be able to use a model like Mythos to simulate attack paths, determine the probability of success and make more fact-based remediation decisions. It could also revolutionize cyber-insurance, a segment historically </span><a href="https://pmc.ncbi.nlm.nih.gov/articles/PMC10024527/">held back</a><span> by underwriting challenges.</span></p><p>And yet -- speed matters, and manual remediation is too slow. Mythos can help companies identify vulnerabilities. But identification protects nothing unless companies apply security patches from vendors and install fixes to code they have developed internally. That is the remediation gap the governance loop above is meant to close; in practice it breaks down into three concrete moves:</p><p><strong>1. Create a living graph of your technology environment.</strong><span> You will very quickly face an overwhelming pipeline of vulnerabilities to remediate and vendor patches to apply. Not every one will be equally important, and the most critical nodes in your environment may not be immediately apparent given all the dependencies among business processes, systems, data and technology infrastructure.</span></p><p>Modeling your environment as a graph will allow you to identify the most critical nodes and prioritize what to remediate first. Ultimately every node in the graph should anchor in a non-human identity -- don&#8217;t connect IP addresses; connect non-human identities. Building the graph will also be an important step in moving to a zero-trust architecture.</p><p><strong>2. Use spec-driven engineering to get to policy-driven systems.</strong><span> If you have bespoke software you will need to fix it. Autocomplete (or even asking models to write discrete code blocks) will not allow you to move quickly enough.</span></p><p>You need to retrain your engineering teams on how to use agents to diagnose root causes, build PRDs and execute on them autonomously. And you may need to do this on a timescale of months, not years.</p><p>As you develop strong capabilities in spec-driven development, you can accelerate efforts to retire technical debt, resulting in a more resilient environment. And you will want to define architecture, configuration and behavior in terms of policy-as-code so you can repave systems that demonstrate drift.</p><p><strong>3. Move change control from human analysis to proof of safety.</strong><span> In many companies, the change approval board acts as a brake and a bottleneck on evolving the environment. It doesn&#8217;t have to be this way, and it cannot continue to be this way if companies seek to remediate the vulnerabilities Mythos identifies before attackers can exploit them. </span><a href="https://dora.dev/capabilities/streamlining-change-approval/">Heavyweight change approval processes</a><span> are often ineffective. Teams of agents may collaborate to form an </span><a href="https://arxiv.org/abs/2601.17762">automated patch management pipeline</a><span>.</span></p><p><span>Before you deploy a change, it must prove itself in a sandbox, both in terms of whether it breaks something and whether an adversary agent can compromise it, replacing the bottleneck of human analysis with the proof of safety. And you should deploy changes in stages, testing impact as you go. For years companies like Netflix have reconciled speed and safety by using </span><a href="https://netflixtechblog.com/automated-canary-analysis-at-netflix-with-kayenta-3260bc7acc69">canary analysis for staged change deployment</a><span>.</span></p><p><span>None of these interventions are simple. [9] All will take attention, effort and time. But what is the alternative? Outsourcing might help, but it doesn&#8217;t remove the remediation burden at a stroke. Waiting for regulatory guidance (across dozens of jurisdictions and agencies) is uncertain and will likely take too much time. The age of </span><a href="https://www.schneier.com/blog/archives/2026/04/mythos-and-cybersecurity.html">security by obscurity</a><span> is over. The cost of stasis may exceed the cost of change.</span></p><h4><strong>One-time programs are a lot easier than sustained cultural and organizational change</strong></h4><p><span>Less than a dozen years after Sputnik, Neil Armstrong and Buzz Aldrin explored the Sea of Tranquility. Ten more astronauts walked on the Moon in the next three years. Then, nothing. What poverty of the human spirit, what richness of bureaucratic incompetence caused us to tread on the moon and then retreat, without returning? Only this month has any human again </span><a href="https://www.nasa.gov/blogs/missions/2026/04/06/artemis-ii-flight-day-6-lunar-flyby-updates/">transcended low Earth orbit</a><span>?</span></p><p><span>Sputnik was a shock to the American educational system. By the 1980s, the National Science Foundation warned that Americans were in danger of </span><a href="https://www.edweek.org/education/sputnik-at-25/1982/10#:~:text=Since%201980%2C%20when%20a%20study,%2C%20mathematics%2C%20and%20foreign%20languages.">scientific illiteracy</a><span>. Shortly afterwards, the famous </span><a href="https://eric.ed.gov/?id=ED226006">Nation at Risk</a><span> report warned that post-Sputnik gains had wasted away. Not all the news is bad! American students have made </span><a href="https://www.educationnext.org/half-century-of-student-progress-nationwide-first-comprehensive-analysis-finds-gains-test-scores/#:~:text=Contrary%20to%20what%20you%20may,four%20years'%20worth%20of%20learning.">large gains in fluid reasoning</a><span> in recent decades -- and the dire standing of American students in global league tables may have more to do with </span><a href="https://ed.stanford.edu/news/poor-ranking-international-tests-misleading-about-us-performance-new-report-finds">compositional effects</a><span> than school performance. But some of the news is really bad -- </span><a href="https://www.nationsreportcard.gov/highlights/ltt/2023/">math scores have collapsed</a><span> in the wake of Covid.</span></p><p>Just like a space program, the exploitation of AI in the enterprise is a generational project. Just like education reform, the ability of enterprise technology to use AI to build, run and protect systems is a foundational capability. Will your company move quickly enough to respond to the immediate challenge posed by AI-enabled cyberattacks? Will it sustain focus and attention over time to foster the capabilities to use AI not only to protect existing systems but to also make transformative leaps in business innovation, efficiency and resiliency?</p><h3><strong>Footnotes</strong></h3><p><span>[1] A great book. I read it every year in high school. The </span><a href="https://www.rogerebert.com/reviews/great-movie-the-right-stuff-1983">movie</a><span> is pretty good too.</span></p><p><span>[2] Might I be evoking Arnold Toynbee&#8217;s theory of </span><a href="https://assets.cambridge.org/97805216/53053/excerpt/9780521653053_excerpt.pdf">civilizational challenge and response</a><span> here? Maybe.</span></p><p><span>[3] SQL is overwhelmingly the world&#8217;s most used declarative programming language. Perhaps its </span><a href="https://www.ibm.com/history/relational-database">adoption</a><span> provides the best historical parallel for spec-driven development. Replacing all the technical minutiae required for a query with a few SQL statements turned weeks&#8217; worth of work into minutes.</span></p><p>[4] References not provided in order to protect the guilty.</p><p><span>[5] At first glance, you might ask: &#8220;How much does this matter for the enterprise? Once you get past the national security domain, how many attacks rely on zero-days?&#8221; More than you might think: a Mandiant analysis found that </span><a href="https://cloud.google.com/blog/topics/threat-intelligence/time-to-exploit-trends-2023">70 percent of serious breaches they tracked involved a zero-day exploit</a><span>. And of course a capable agentic attacker could assemble a sophisticated campaign out of a series of n-day exploits.</span></p><p><span>[6] The global security and vulnerability management market will shortly grow to the </span><a href="https://market.us/report/security-vulnerability-management-market/#:~:text=The%20Global%20Security%20%26%20Vulnerability%20Management,10%25%20throughout%20the%20forecast%20span.">USD 20 billion</a><span>.</span></p><p><span>[7] Itself a </span><a href="https://www.researchnester.com/reports/penetration-testing-market/717">billion-dollar</a><span> market.</span></p><p><span>[8] Special thanks to my colleagues </span><a href="https://prosaictimes.substack.com/p/cisos-help-business-leaders-take">Rich Isenberg</a><span> and </span><a href="https://prosaictimes.substack.com/p/when-binaries-break-and-what-that">Charlie Lewis</a><span> on these topics.</span></p><p>[9] These changes will require coordination across the technology organization. The infrastructure team will likely have to build the living graph of the environment, with input from each application team. Your core architecture or engineering team will lead the transition to spec-driven development, but much of the work will fall on application teams&#8212;and on infrastructure teams as they move from configuring systems to automating services. Transforming change control and patch management will require collaboration across the developer toolchain, infrastructure, and cybersecurity teams.</p>]]></content:encoded></item><item><title><![CDATA[The world is entropic and deterministic systems are not]]></title><description><![CDATA[What could we do if we can process entropy programmatically>]]></description><link>https://www.prosaictimes.com/p/the-world-is-entropic-and-deterministic-060</link><guid isPermaLink="false">https://www.prosaictimes.com/p/the-world-is-entropic-and-deterministic-060</guid><dc:creator><![CDATA[James Kaplan]]></dc:creator><pubDate>Tue, 16 Jun 2026 12:25:52 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/202274978/9840336a1eb104ac2ceb05a753344f11.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>Every business system processes entropy somehow &#8212; by product managers who formalize ambiguous workflows, by account managers who fill in endless CRM fields, in the free-text notes nobody reads. Agentic capabilities give you five new places to put that work: software engineering, user interface, data ingestion, run-time decisions, and graph or vector storage. Where you put that work will shape your cost structure, your risk posture, and your users&#8217; frustration for years.</p><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://prosaictimes.substack.com/p/the-world-is-entropic-and-deterministic?utm_source=substack&amp;utm_medium=email&amp;utm_content=share&amp;action=share&amp;token=eyJ1c2VyX2lkIjoxNjI2Njg1NSwicG9zdF9pZCI6MTk5MjIxNzE1LCJpYXQiOjE3ODE2MTI2MTksImV4cCI6MTc4NDIwNDYxOSwiaXNzIjoicHViLTcwNDE4NjEiLCJzdWIiOiJwb3N0LXJlYWN0aW9uIn0.KhWNqHjl55i3x1XNYE2E0nw0RaUpus-7MfJjG4ds20s&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption"></p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.prosaictimes.com/p/the-world-is-entropic-and-deterministic-060?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.prosaictimes.com/p/the-world-is-entropic-and-deterministic-060?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><p>Thanks for reading Prosaic Times &#8212; share the entropy with a friend!</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://prosaictimes.substack.com/p/the-world-is-entropic-and-deterministic?utm_source=substack&amp;utm_medium=email&amp;utm_content=share&amp;action=share&amp;token=eyJ1c2VyX2lkIjoxNjI2Njg1NSwicG9zdF9pZCI6MTk5MjIxNzE1LCJpYXQiOjE3ODE2MTI2MTksImV4cCI6MTc4NDIwNDYxOSwiaXNzIjoicHViLTcwNDE4NjEiLCJzdWIiOiJwb3N0LXJlYWN0aW9uIn0.KhWNqHjl55i3x1XNYE2E0nw0RaUpus-7MfJjG4ds20s&quot;,&quot;text&quot;:&quot;Share&quot;,&quot;action&quot;:null,&quot;class&quot;:&quot;button-wrapper&quot;}" data-component-name="ButtonCreateButton"><a class="button primary button-wrapper" href="https://prosaictimes.substack.com/p/the-world-is-entropic-and-deterministic?utm_source=substack&amp;utm_medium=email&amp;utm_content=share&amp;action=share&amp;token=eyJ1c2VyX2lkIjoxNjI2Njg1NSwicG9zdF9pZCI6MTk5MjIxNzE1LCJpYXQiOjE3ODE2MTI2MTksImV4cCI6MTc4NDIwNDYxOSwiaXNzIjoicHViLTcwNDE4NjEiLCJzdWIiOiJwb3N0LXJlYWN0aW9uIn0.KhWNqHjl55i3x1XNYE2E0nw0RaUpus-7MfJjG4ds20s"><span>Share</span></a></p><h4><strong>1. Every computer system we build is an imperfect representation of reality</strong></h4><p>&#8220;No, I didn&#8217;t go to Catholic school. Why do you ask?&#8221;</p><p>An eminent partner at a previous consultancy looked at me across an empty conference room and explained: &#8220;You have an instinct for mapping data onto a grid -- you have a Cartesian mindset, which many good consultants learn from a Jesuit education.&#8221;</p><p>Grids distort as much as they reveal. We&#8217;ve all seen (or built) grids for evaluating outsourcing vendors: 20 points for stability, 30 for service quality, 30 for cost, 10 for innovation. These never produce the right answer -- they ignore non-linearity. You won&#8217;t select a vendor below your financial stability threshold no matter how cheap; once a bidder clears it, you care about cost and service, not financial stability.</p><p>Every slide, every analysis, every system is an imperfect representation of reality. CRM systems are a simplified model of how your business interacts with customers. Operational systems are a simplified model of your factory. I learned this crawling around telecom carriers in the 1990s, where you had to ask the service techs which USOC &#8220;1FR&#8221; lines had bridge taps that had to be removed before upgrading to DSL.</p><h4><strong>2. The world is entropic</strong></h4><p>Do you know whether that deal will close next week and at what price? Whether your flight to Chicago will land on time? Or whether a new employee will turn out to be a hero or a goat? I do not.</p><p>As a recovering history major, I believe the past provides counsel on the future. On June 21, 1948, the <a href="https://curation.cs.manchester.ac.uk/computer50/www.computer50.org/mark1/new.baby.html">Small-Scale Experimental Machine</a> became the first computer to run a program stored in its own electronic memory -- 128 bytes of it. Weeks later, Weaver and Shannon published articles foreshadowing many of the problems we struggle with today: automating Byzantine business processes, capturing latent or ambiguous data.</p><p>Shannon defined entropy as <a href="https://monoskop.org/images/a/ae/Shannon_Claude_E_A_Mathematical_Theory_of_Communication_1957.pdf">average amount of uncertainty in a probability distribution.</a> [1] Maybe that&#8217;s okay -- in a world without entropy no business could exceed the risk-free rate of return. The more entropic a domain, the more information required, and the more expensive the computer system to automate it.</p><p>Weaver laid out a <a href="https://fernandonogueiracosta.wordpress.com/wp-content/uploads/2015/08/warren-weaver-science-and-complexity-1948.pdf">relationship between complexity and uncertainty</a>. Some problems are simple: hold all variables constant except the dependent and independent ones, and you get the steam engine, the automobile, the telephone. A payroll system is the modern analogue -- fixed variables, describable rules, few feedback loops.</p><p>Starting in the late nineteenth century, scientists attacked problems of disorganized complexity. Statistics could predict the frequency of calls in a telephone exchange or the claims paid by a life insurance company, even when individual causes remained opaque -- provided each data point was atomic. Fair Isaac <a href="https://escholarship.org/uc/item/7n1369x2">developed the FICO score on this basis</a> in the late 1950s.</p><p>Then Weaver addressed problems of organized complexity -- macroeconomic management, ecology -- where many inter-related factors multiply uncertainty because each may influence the others in non-obvious ways. Neither nineteenth-century analytics nor twentieth-century statistics could handle them. He hoped new computing devices might, and pointed to the operations research developed in the Battle of the Atlantic as a way forward.</p><p>Problems of organized complexity abound in modern business -- order-to-cash, pharmaceutical manufacturing. Given enough contracts, <a href="https://prosaictimes.substack.com/p/why-enterprise-technology-is-so-bloody">even payroll can turn into one</a>. [2] How much time do knowledge workers spend massaging data into or out of enterprise systems because the system couldn&#8217;t capture every exception the domain implied?</p><p>We should forgive Weaver for not foreseeing the organized complexity required to address organized complexity -- ERP programs suffer their own, and enterprise technology functions <a href="https://prosaictimes.substack.com/p/prosaic-times-what-looks-like-fiscal">suffer from it themselves</a>.</p><p>Writing with Shannon, Weaver named another contributor: latent meaning. Ask an account executive the status of a potential sale and she might say &#8220;We&#8217;re in final price negotiations with the CHRO and he would like to get a deal signed within the month, but the general counsel is hacked off about a couple of legal terms we require and the CHRO heard he is going to call the CEO and ask that they reopen discussions with another bidder.&#8221; What is she supposed to select among the four CRM choices for &#8220;status&#8221; -- RFP open, RFP submitted, financial negotiations or closed?</p><p>Weaver and Shannon identified one more problem -- whether a system creates the desired behavior in the people who interact with it. Think about computer systems the way the military thinks about weapons systems: as inclusive of both the technology and the user. Design choices affect user behavior in unpredictable ways. Complicated interfaces cause users to resist entering data, or to prejudice what they enter to make themselves look good.</p><p>Calendaring is deceptively entropic. If Suzy, my assistant, asks me about a conflict at 10 am on a Tuesday, I might say: &#8220;I&#8217;ll go to the meeting with client 1, because I think that colleague A can cover me in the meeting at client 2. And don&#8217;t decline or mark me tentative for anything, because I don&#8217;t want anyone giving away the time slot because I might not be there.&#8221; I don&#8217;t verbalize dozens of assessments about people and situations that shape my decisions. You have entropic communication about organized complexity, latent information and adaptive behavior all in a couple of sentences!</p><h4><strong>3. Entropy creates cost and frustration when we build systems to represent it</strong></h4><p>How much time do we all spend in conference rooms debating how much granularity the data model should have -- and how we balance fidelity to the business process versus the cost of maintaining data? How frequently do you find the correct state for a transaction not in the fields designed to contain it, but in the free-text notes or the accompanying email? And how much user anger derives either from the endless fields (specified to capture the subtleties of state) or the disconnect between what the system says and the reality they observe?</p><p>Put another way: how much time do we devote to designing around entropy when we build systems? And how much frustration do we create because of the choices we make in doing so?</p><p>Operational systems work best when the world can be reduced to stable categories, deterministic workflows, and enumerable exceptions -- all these make a domain easy to formalize. Nobody complains much about most payroll systems because they apply a bounded number of explicit rules to available data.</p><p>Analytic systems work best with huge sample sizes and a few relevant independent variables -- making the entropy here tractable to statistical analysis. Machine learning systems for pricing consumer products work because massive amounts of structured data allow probabilistic inference where humans might have struggled to discern patterns.</p><p>Other domains and use cases have more intractable entropy. Systems to support treasury management for large enterprises? Modeling a thousand-page contract, involving hundreds of legal entities, dozens of jurisdictions and a thousand different exceptions you can have for a transaction -- all of which generate entropy. Which messiness must you model and which can you simplify away? CIOs have exceeded budget, blown deadlines and angered users in seeking to answer that question.</p><p>Yes, machine learning has blunted the impact of entropy in some cases by sniffing out the relationships among variables, but often the sample size is too small and the data too messy for traditional machine learning to be effective. Years ago, someone said collections managers could offer definitive recommendations about how to reduce losses -- why couldn&#8217;t CISOs do the same when talking about how to protect the business against cyberattack?</p><p>I tried to explain that each demographic segment included millions of households. You could experiment with a new script and quickly determine whether it increased or decreased promises-to-pay. Any large company&#8217;s technology environment is a snowflake -- even two companies of similar size and in the same sector may have radically different technology environments. Vulnerability depends not on individual decisions, but on how you connect all the pieces in your environment. And you might not know whether you had been breached for years, if ever. [3]</p><h4><strong>4. GenAI-based agentic systems process entropy</strong></h4><p>Deterministic systems cannot process entropy. They can rely on humans to pre-process it for them -- as happens when product managers and engineers sit in a conference room debating how to capture the data required to automate an ambiguous process. They push it on to users like account managers who must fill in endless fields about their pipeline -- and still wonder which option they should select to describe deal status. Or they can store it inertly, like the free-text notes that exist in some customer service platforms. All of these imply some combination of low efficiency and lower effectiveness.</p><p>When large language models process text, they <a href="https://arxiv.org/abs/1706.03762">convert tokens into vectors, points in a high-dimensional space</a>. This encodes meaning through proximity -- similar meanings cluster together. Large language models can do things deterministic systems cannot do or do poorly:</p><ul><li><p>Allow inference across stored entropy: Written and spoken language are entropic. Vector embeddings allow LLM-based systems to query and analyze free-text notes, email threads and meeting transcripts.</p></li><li><p>Identify implicit relationships: Vector geometry represents connections between concepts, such as the general counsel wanting to block the deal for group health insurance because he disliked the contract terms.</p></li><li><p>Understand gradations rather than discrete states: A deterministic system requires the account executive to choose whether the deal has advanced to final negotiations or not. A vector representation of the same situation can sit between two states.</p></li></ul><p>GenAI-based agentic [4] systems give us new ways to process entropy.</p><ul><li><p>At design time, by using <a href="https://prosaictimes.substack.com/p/vibe-coding-doesnt-eliminate-the">software engineering agents to create business logic</a> that reflects all the organized complexity that Weaver described.</p></li><li><p>As part of the user interface, to mediate between the entropy of written language and a deterministic system, rather than forcing the user to do the work.</p></li><li><p>Via data ingestion, to derive insights from the massive stores of entropic, unstructured data every enterprise has sitting on its servers.</p></li><li><p>At run-time (either with or without a human in the loop), to make decisions and execute transactions non-deterministically.</p></li></ul><p>We can also store data used and produced by agentic systems in different ways. Traditional relational databases excel at storing and retrieving massive amounts of transactional data at speed and with near-perfect reliability. They struggle with more ambiguous data, with dense relationships among all the elements. [5] We can choose to store this data either in vector databases or in <a href="https://prosaictimes.substack.com/p/prosaic-times-elevating-ai-from-tactics">knowledge graphs.</a></p><h4><strong>5. You have choices about how and where you use agents to process entropy</strong></h4><p>So much of the agentic discourse we see mirrors the flat Cartesian mindset captured in the grid used to evaluate bidders for outsourcing deals. Agents are risky! Or: everything will be an agent!</p><p>But entropy is, well, entropic. It varies in scale and shape from business domain to business domain. Sometimes it takes the form of a dense web of interconnections among idiosyncratic products, contracts, processes or customer relationships. Sometimes it takes the form of latent data that doesn&#8217;t fit into any data structure you might define. Not a few business domains suffer from multiple forms of entropy.</p><p>GenAI-based agents also have disadvantages compared to deterministic systems. GPU-based inferencing is <a href="https://www.spheron.network/blog/ai-inference-cost-economics-2026/">slower and more expensive</a> than CPU-based processing -- a single agentic transaction often costs cents and adds hundreds of milliseconds, where the equivalent deterministic transaction costs fractions of a cent and resolves in single-digit milliseconds. Non-deterministic systems are only as good as the context they receive. An agentic system can process the free-text notes in a CRM platform. It won&#8217;t know anything about the discussion two account executives had in the car on the drive back from the customer site. [6]</p><p>Abjure the false binaries -- you have real choices about how and where in the value chain you process entropy.</p><ul><li><p><strong>Agentic software engineering:</strong> This will be relevant for almost any systems effort. It will allow you to automate all the business logic required to reflect organized complexity with more speed and reliability and less cost. And after agents help you develop the code, you can still apply all the quality assurance mechanisms you have developed over decades, just as you would code developed by hand.</p></li><li><p><strong>User interface:</strong> Retain traditional interfaces for situations where users have to enter small volumes of easily understood data. Develop agentic- or chat-based interfaces for order entry, CRM, or transaction processing systems where users complain about having to fill in screen after screen of data. You can always use a combination of deterministic rules and user validation to ensure the agent correctly captures user intent.</p></li><li><p><strong>Data ingestion:</strong> This is one of the most powerful and most underestimated capabilities. All companies receive and store vast amounts of valuable but entropic data -- <a href="https://venturebeat.com/data-infrastructure/report-80-of-global-datasphere-will-be-unstructured-by-2025">eighty percent of corporate data is unstructured</a> and even structured data can be fragmented and hard to correlate. Customer requests for quotation? Customer service notes? Legal contracts. Agentic capabilities can ingest all of this either to support operational processing or to generate new business insights, even if many companies <a href="https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai">have not focused here yet</a>. [7]</p></li><li><p><strong>Run-time:</strong> This is complicated and has the highest stakes. Use agentic patterns for low-volume heterogeneous decisions. I am helping technology organizations use agents to compare project designs with technology standards. The agent will compare two artifacts (a project design and a standards document) that describe organized complexity in natural language (which is inherently entropic) and determine whether one conforms to the other. Hybrid patterns will probably become increasingly common, with deterministic cores and agents to handle edge cases.</p></li><li><p><strong>Data storage:</strong> Naturally, relational databases will continue to store structured and transactional information. Knowledge graphs excel in modeling product portfolios, customer relationships, process maps and other domains where relationship structure carries meaning. Vector search enables retrieval by meaning from notes, documents and transcripts.</p></li></ul><h4><strong>6. Precision matters because entropy is, well, entropic</strong></h4><p>I have always hated the formulation &#8220;The technology is easy. The governance is hard. The organization is hard. The line at the cafeteria is hard.&#8221; Here, design choices will shape cost structure, risk posture and user experience for years.</p><p>With a capability to process entropy at scale, you have to think about where the entropy sits in your business system -- even a simple one.</p><p>Managing invites for the Technology Leadership Forum is lower-entropy than a hundred-million-dollar group insurance deal, but there is plenty of &#8220;Joe really wants to attend, but can&#8217;t, depending on when a personal conflict lands -- and wants to know if Sally can possibly attend in her place.&#8221; I put invitees and members into a knowledge graph and built <a href="https://prosaictimes.substack.com/p/agent-serena-stopped-the-yak-shaving?utm_source=substack&amp;utm_medium=email&amp;utm_content=share">Agent Serena</a> to translate the entropy in my email into the organized complexity of that graph. [8]</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!XNlO!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd93e11c-2339-4c13-8ce0-aeadca18a126_2880x2720.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!XNlO!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd93e11c-2339-4c13-8ce0-aeadca18a126_2880x2720.png 424w, https://substackcdn.com/image/fetch/$s_!XNlO!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd93e11c-2339-4c13-8ce0-aeadca18a126_2880x2720.png 848w, https://substackcdn.com/image/fetch/$s_!XNlO!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd93e11c-2339-4c13-8ce0-aeadca18a126_2880x2720.png 1272w, https://substackcdn.com/image/fetch/$s_!XNlO!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd93e11c-2339-4c13-8ce0-aeadca18a126_2880x2720.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!XNlO!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd93e11c-2339-4c13-8ce0-aeadca18a126_2880x2720.png" width="1456" height="1375" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/bd93e11c-2339-4c13-8ce0-aeadca18a126_2880x2720.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1375,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:663845,&quot;alt&quot;:&quot;&quot;,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://prosaictimes.substack.com/i/199221715?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd93e11c-2339-4c13-8ce0-aeadca18a126_2880x2720.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" title="" srcset="https://substackcdn.com/image/fetch/$s_!XNlO!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd93e11c-2339-4c13-8ce0-aeadca18a126_2880x2720.png 424w, https://substackcdn.com/image/fetch/$s_!XNlO!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd93e11c-2339-4c13-8ce0-aeadca18a126_2880x2720.png 848w, https://substackcdn.com/image/fetch/$s_!XNlO!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd93e11c-2339-4c13-8ce0-aeadca18a126_2880x2720.png 1272w, https://substackcdn.com/image/fetch/$s_!XNlO!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fbd93e11c-2339-4c13-8ce0-aeadca18a126_2880x2720.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Taking a more highly-scaled domain: entropy pervades enterprise change management in banking. Dozens of interconnected process steps and artifacts; latent information about why a milestone might be at risk of slipping and under what circumstances. Traditionally, banks managed it with managerial talent copying data among word processing, spreadsheet and presentation files. And many, many emails. The result: frustration, expense, and less insight into major programs than anyone would like.</p><p>Banks can use agentic software engineering to build a system whose agents ingest program documents, extract the relevant risks, issues, decisions and action items, and store them in a knowledge graph with the relationships among them. Which risks affect which business lines? Which work-stream lead owns which decision? Further agents interrogate emails and videoconference transcripts to enrich the graph. Vector descriptions let program managers search by meaning, not keywords. Still more agents read the graph to assess risks and surface opportunities to improve the program.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!sDBe!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F72606ced-f563-44cd-9446-f2058fd3daa6_2880x2480.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!sDBe!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F72606ced-f563-44cd-9446-f2058fd3daa6_2880x2480.png 424w, https://substackcdn.com/image/fetch/$s_!sDBe!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F72606ced-f563-44cd-9446-f2058fd3daa6_2880x2480.png 848w, https://substackcdn.com/image/fetch/$s_!sDBe!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F72606ced-f563-44cd-9446-f2058fd3daa6_2880x2480.png 1272w, https://substackcdn.com/image/fetch/$s_!sDBe!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F72606ced-f563-44cd-9446-f2058fd3daa6_2880x2480.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!sDBe!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F72606ced-f563-44cd-9446-f2058fd3daa6_2880x2480.png" width="1456" height="1254" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/72606ced-f563-44cd-9446-f2058fd3daa6_2880x2480.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1254,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:518185,&quot;alt&quot;:&quot;&quot;,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://prosaictimes.substack.com/i/199221715?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F72606ced-f563-44cd-9446-f2058fd3daa6_2880x2480.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" title="" srcset="https://substackcdn.com/image/fetch/$s_!sDBe!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F72606ced-f563-44cd-9446-f2058fd3daa6_2880x2480.png 424w, https://substackcdn.com/image/fetch/$s_!sDBe!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F72606ced-f563-44cd-9446-f2058fd3daa6_2880x2480.png 848w, https://substackcdn.com/image/fetch/$s_!sDBe!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F72606ced-f563-44cd-9446-f2058fd3daa6_2880x2480.png 1272w, https://substackcdn.com/image/fetch/$s_!sDBe!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F72606ced-f563-44cd-9446-f2058fd3daa6_2880x2480.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>This combination -- agents, knowledge graph, vector database -- removes the entropy from a painful business process. It reduces cost and improves transparency. Those of us on team cyborg (rather than team android) will note that it also empowers managers: less toil, better information.</p><p>Agentic systems -- with knowledge graphs and vector databases -- can be transformative. When I wrote that global business must move beyond <a href="https://prosaictimes.substack.com/p/prosaic-times-elevating-ai-from-tactics">organized factories and chaotic offices</a>, this is what I meant. The benefits are both economic and <a href="https://prosaictimes.substack.com/p/ai-enabled-software-engineering-is">humanistic</a>. Nobody grew up hoping to spend days pasting data from email to spreadsheets and back.</p><p>Precision matters here. Agents are not magic. Inferencing is expensive, latency is real, and new vulnerabilities arrive faster than we can grasp them. But the harder discipline is the one Weaver and Shannon left us: see your business as a system, find where the entropy sits, and choose where to process it. A flat, Cartesian grid won&#8217;t help.</p><p>Thanks for reading Prosaic Times &#8212; subscribe to receive every issue!</p><h3><strong>Footnotes</strong></h3><p>[1] This <a href="https://medium.com/@ikarosilva/entropy-a-simple-intuitive-explanation-6369ef4ab8ea">differs from standard deviation</a>, which measures the magnitude of the spread around a mean. Shannon entropy measures the unpredictability of a distribution. Relevant to us: you can measure the Shannon entropy over a set of non-quantitative values just as you can over a set of quantitative ones. In addition, there are more and less expansive definitions of entropy. I am using a relatively expansive one here.</p><p>[2] CityTime is a great example of <a href="https://arxiv.org/pdf/math/0406077">Kolmogorov complexity.</a> The shortest possible description of the rules governing what every city employee gets paid is approximately as long as the rules themselves &#8212; decades of negotiated union contracts, grandfathered provisions, and exceptions to exceptions, each one load-bearing. You cannot compress it further without losing something that will eventually matter. Automation doesn&#8217;t reduce this complexity; it just moves it from humans who held it in their heads to engineers who must encode it in systems.</p><p>[3] My interlocutor said I was over-complicating the situation and CISOs were probably just incompetent. Sigh.</p><p>[4] <a href="https://medium.com/@elmotto.joseph/simple-reflex-agents-an-ai-101-you-can-actually-use-9ec11ace6140">Agents predate widespread adoption of large language models and genAI</a>. By some definitions, the cruise control system in your car is an agent. You set a speed. It monitors the speed, accelerating when the car drops below that speed (because you are going up a hill) and easing off the throttle when you exceed it. Of course calling LLMs makes agents infinitely more capable than the cruise control in your car.</p><p>[5] The notion that relational databases might struggle with relationships among data elements might puzzle some. But only those who have never stared at a screen in the early morning trying to make sense of an outer join -- or who developed a better command of SQL than I ever had.</p><p>[6] I like the idea of <a href="https://www.youtube.com/watch?v=CgeyjTXXBhI">decision traces and context graphs</a>, but we should be realistic about which decision traces we can capture and which we cannot, unless we want to build a <a href="https://ethics.org.au/ethics-explainer-panopticon-what-is-the-panopticon-effect/">panopticon</a> for ourselves.</p><p>[7] I stared in disbelief the first time Zubin Ghafari showed me how he used GenAI to integrate messy CMDB data with other telemetry information. I had assumed this would have taken him weeks.</p><p>[8] The natural language front end to Prosaic Graff was a life-saver, but the latency sometimes made me want to put my fist through the screen. So I created Python scripts I could run (instantly) from the Terminal that told me how many members planned to attend or the status of any individual member.</p>]]></content:encoded></item></channel></rss>