The AI Model Built for What LLMs Can't Do
Most AI companies are racing to build bigger LLMs. Eve Bodnia thinks that's the wrong approach. Eve is the founder and CEO of Logical Intelligence, which is developing an alternative to the transformer-based models dominating the industry. Her argument: LLMs’ architecture makes them fundamentally unsuited for some mission-critical tasks. A system that generates output one token at a time, with no ability to inspect its own reasoning mid-process or guarantee its results, shouldn't be trusted to design chips, analyze financial data, or even fly a plane. Her alternative is the energy-based model (EBM), a form of AI rooted in the physics principle of energy minimization, not language prediction. Rather than guessing the next probable word, an EBM maps every possible outcome across a mathematical landscape, where likely states settle into valleys and improbable ones sit on peaks. Dan Shipper talked with Bodnia for AI & I about why she believes LLM progress is plateauing, what it means for AI to actually understand data rather than just pattern-match across it, and how her team is building toward formally verified code generated in plain English—no C++ required. If you found this episode interesting, please like, subscribe, comment, and share! Head to http://granola.ai/every and get 3 months free with the code EVERY To hear more from Dan Shipper: Subscribe to Every: https://every.to/subscribe Follow him on X: https://twitter.com/danshipper Timestamps: 00:00:51 - Introduction 00:02:09 - Why correctness and verifiability matter in AI 00:09:33 - What an energy-based model is
- Published
- Published Apr 15, 2026
- Uploaded
- Uploaded Jun 12, 2026
- File type
- POD
- Queried
- 00
- Source
- share.transistor.fm
Full transcript
Showing the full transcript for this episode.
AI-generated transcript with timestamped sections.
[00:00] Can you define EBM for us? EBMs are naturally non-autoregressive. [00:04] There are no sequences of tokens and that's what makes it fundamentally different. Like imagine you're trying to navigate the map and you have a left brain. To navigate you're sort of allowed to choose one direction at a time. [00:16] And sometimes you take [00:17] the wrong turns just because you hallucinate. [00:20] Like, there might be a hole in the road and you're just gonna fall. And you might see this hole, but you cannot [00:25] turn back. [00:26] because you're ultra-regressive LLM. EBM gonna have the bird view all the time. So if you see there's a hole, you're gonna choose a different route. [00:48] E, welcome to the show. [00:51] Hi, thanks for having me. [00:53] Great to have you on. For people who don't know, you are the founder and CEO of Logical Intelligence. Tell us what Logical Intelligence does. [01:01] So logical intelligence does a few things. First of all, we see ourselves as a foundational AI company. So we work in both with EBMs and LLMs. [01:12] So everything they built in-house, we prototyped on LLM initially and... [01:18] We're building EBM at the same time and [01:21] that sort of gets plugged in in the long term. [01:25] We focused on correctness of software and hardware.
[01:31] as a product. Because I believe there is a lot of issues with [01:36] AI. [01:38] being placed in machine critical systems today? Like, you know, can we do the code gen? Can we do the chip design? And the answer is yes. Yes, people use LLMs today. But very few actually questioning of like, [01:52] how this results are actually correct. Does it make sense what it produced? And it seems like there's a big gap on market today, having deterministic AI, verifiable AI. So we're trying to fill that gap. [02:07] Hmm. [02:09] The place my brain goes first. [02:13] is why does correctness or whether something makes sense [02:19] Why does that matter if it works? [02:22] Actually, let me ask you a question back. So speaking of correctness, [02:29] I don't know. Well, imagine there is AI driving a car and you are in that car and that car is an LLM. And someone tells you like, you know, 20% of the time it's going to hallucinate and you might end up like in like wrong place. How would you feel about it? Well, I think in my case, I'd be like, wow, that's kind of interesting. I'm curious where it takes me. Okay. But let me give you another example. Yeah, sure. How about the plane? [02:59] from SF to New York. And someone says, you know, like 20% of the time, it might just like the next word not going to match and it's going to go down. So how would you feel about it? Yeah, my feeling about that is planes are currently run very well by deterministic systems. So I don't know why I would need an AI for that.
[03:17] I feel like we just cannot avoid AI anywhere. Like next 10 years, people are going to try to place AI everywhere, automate systems with AI. And, you know, technically, you might not need we survived somewhat. [03:32] without AI up to this moment, but now it's just like a next step of evolution that people just want AI everywhere. [03:40] Like for the banking, you don't need AI initially, but we learn it's really helpful to automate [03:47] like certain processes in decision making. And it's going to save us a lot of time and allow a space to be creative instead of like debugging and fixing things. [03:58] So... [03:59] I just feel like it's an avoidable future. [04:03] I think maybe what I'm getting at is [04:06] Um... [04:07] What am I getting at? [04:11] It seems like... [04:13] If you want a guarantee of certainty using [04:16] Um. [04:17] The only way to sort of guarantee certainty is to use something that... [04:22] you can express in [04:24] code or logic. [04:26] Mm-hmm. [04:27] That's a part of it. So the certainty comes from internal verifiers and external verifiers, at least for us. So for example, if you take LLM, [04:39] Obviously, it's a language based model and architecture doesn't allow you to do internal verifiers. So you like it's like a black box for you. You don't have access to what's inside until it's all processed. But you have access to the output. And
[04:58] Many people and companies sort of take LLM, train it for certain tasks, and if it requires logic, they attach texturing verifiers to it, such as languages like Lean4, which is a proof of, I mean, machine verifiable language, proof language, which allows you to check this output using mathematical algorithms. [05:18] frameworks. However, you know, it doesn't solve the problem of things being [05:26] um [05:27] just... [05:28] so expensive because what expensive is your architecture, which is still playing a guessing game out here. And even if you attach external verifier, even you fine tune this LLM specifically for the task you're trying to create, you're still not solving the problems of tokens being expensive. It takes compute for you to play a guessing game. [05:49] So this problem is solved by the EBMs, but we're talking about LLMs for now. [05:55] So here we have the situation when there is [05:59] Right? Internal absence of verifier, but there's external one. So now about the EBMs. EBMs don't have tokens. It's token free model. There's no guessing game of this kind. So essentially, [06:12] Um, [06:13] you could oversee all the possible scenarios. Can you define EBM for us? Yeah, I'll define in a second. So for now, just think of it as something which doesn't play a guessing game and something which has architecture, which is essentially allow you to self-align itself as processing the information. And it's no longer a black box for you. So as it's performing, you can open it anytime during
[06:43] just nature of architecture is different. So you have for verification tasks, you have [06:49] this notion of [06:51] Self-alignment because of the EBM architecture and the absence of token makes it cheap, but also you have external verifier on top of it. So you have verification sort of on both sides, inside and outside. [07:05] Um, [07:06] Hopefully that makes sense. I think so. Let me play it back to you and you tell me if I'm getting you. So basically, I think what you're saying is we're living in this world, which is really cool with LLMs, which is we can generate lots of output with them. And the output is really useful for a lot of different things. But in order to tell if the output is right, [07:27] So the best we can do is sort of guess and check. We generate the output. And then, for example, if it's code, then we go and check the code with integration tests or manual tests or whatever, just to see if it works. And that totally works, but it is expensive and time consuming. [07:44] And one of the problems is it's very hard for us to know, okay, how did the LLM get to this answer? We can't go look inside of it. [07:55] And I think what you're saying is there are other types of models that are a little bit more inspectable. [08:03] And that give us a sense before we even try the output to understand, does this work? Does the output work? We can get a sense from the model by looking at its internals.
[08:16] sort of like, how good is this solution? How good does this model think the solution is? [08:21] Um... [08:22] And it's sort of like being able to ask someone like, are you sure about this? Like, how good is this? Before you like go check their work. And a language model can answer that question. But a language model's answers are working at a different level when it answers that question than these EMB models are working. And the answers from EMB models are more likely to be correct. [08:48] Mm-hmm. Yeah, so you always have... [08:51] An opportunity to see what's inside with the EBMs. [08:55] and you control the training. EBM, sorry. Yeah. So the EBMs, you control the training. It's no longer black box for you. You control sort of how the training goes. Well, you do some extent with the LLMs, but you need to wait until the training is done. You need to wait until the training is done. [09:13] before you actually go and see what's inside. In here, you could do like a real time. [09:20] Yeah, and also you can attach the same external verifiers which works for LLMs. So you have sort of double verification things. [09:29] Yeah, so you asked me what is an EBM. I just want to give like a [09:34] historical note because I feel like there's so many terms today and just people throwing those terms without defining it. So EBM just simply means energy-based model.
[09:46] What is energy? Energy-based... [09:49] It comes from [09:51] Physics? [09:53] it's a very popular term when they're trying to minimize the energy and [09:57] If you're doing theoretical physics, like your full time job is just to write Lagrangians, which sort of correspond to [10:05] terms associated with the energy in your system. Like, hey, this is my kinetic energy, this is my potential energy. And then you're trying to derive equations of motion of it. And the way you derive the equations of motions is you're doing the minimization. So that's pretty much how whole theoretical physics works. You just start with the energy terms, then you minimize this energy and you derive equations of motions. And equations of [10:35] what are your laws about your system? And this principle is fundamental principle. Like everything wants to minimize energy around us. Um, and, [10:46] Yeah. So like even as we talking to each other, we sitting on the chairs, we're not like jumping and running around because it's a natural state when we minimize the energy. [10:54] So, [10:56] We're just using this minimization energy principle [11:00] as AI is processing information in high-level terms. So the term [11:06] energy-based minimization doesn't really mean anything. [11:09] specifically to AI is just the whole idea of like, hey, let's take some energy and try to minimize it and discover what's the laws about it.
[11:19] So our model is called official name. [11:22] of that model [11:24] Even though we call it Kona, just because we're big fans of coffee culture, and Kona is one of our favorite kind. So we decided to start with that. The formal name of the model is called Energy-Based Reasoning Model with latent variables. And I'm going to describe exactly what this word means. So we already understand what the energy minimization is. Can I actually pause you? Because I want to make sure that we do understand what the energy-based minimization is. [11:48] Okay. [11:49] Yeah. It's just for now, think of it as just something which minimizes the energy. It means this AI architecture has a framework which allows you to construct the energy function of your system and minimize it. [12:02] I get it. I just want to make sure for people listening, they understand what it means to minimize energy, what energy is and what it means to minimize it. So I'm curious, tell me if this concrete example is close to what you're talking about. [12:23] So, if I'm going to, let's say, I'm going to go lie on the couch behind me. [12:31] and [12:32] And I'm trying to predict or understand how is my body going to be lying on that couch? [12:41] Um, [12:42] given the laws of gravity. [12:45] The couch is uneven, my body's uneven, and so I'm trying to understand the fit of how my body is going to end up settling onto that couch.
[12:53] Um, [12:55] I'm going to end up settling onto the couch in a way that minimizes energy. So there's going to be like a good fit between my body and the couch. [13:02] versus like me being sort of like jerky like this and having lots of different spaces. Is that the sort of energy minimization that you're talking about? [13:10] Yeah, yeah. It's all about your body finding... [13:14] the most comfortable configuration for you, which gonna correspond to [13:21] like the lowest potential of your body. I would even tell the like even more high level example of this. Like, you know, you Dan, you just like imagine you're tired. You're like done thousands of podcasts and you just came home and someone is asking like, okay, Dan is a variable here. Let's try to figure out what's his equations of motion in the house and where he's going to most [13:51] Probably going to end up in the couch. [13:55] With like a nice show and probably some drink. Yeah. [14:00] Yeah, so that's going to be a lot like, okay, when Dan is tired, he's going to go and sit on the couch and just relax. But to get there, we're going to look at all your possible states like you washing the dishes, you know, walking around the house. So those are going to be different states. [14:17] But your most probable scenario is going to be on the couch. [14:20] So essentially all of this picture can be mapped into something we call energy landscape. When
[14:27] it's gonna have like [14:29] It's going to look like a map, so you're going to have [14:32] highest points, you're gonna have lowest points, the highest points we can associate less probable scenarios. So probably if you're tired, you're not gonna dance around, although I don't know. But, [14:43] You know, typically people assume that if you're tired, you're probably going to want to relax. So that's going to be the lowest point. And as we're trying to figure out where you are during the training, we're going to observe you multiple times during different days. And [15:01] you know how much of the workload you have it's going to be variable your internal state is going to be very about how your body feels and eventually we're going to train this landscape to be you know based on what we see in real world right the lowest point is going to be you on the couch we've all been there you're sitting in an important meeting and you're trying to pay attention you're trying to stay present but you have this lingering underlying anxiety that you're going to forget [15:31] forget the decision, forget the action item, let something important slip through the cracks. That's why I love Granolay. It's an AI-powered notepad that works in the background while you're in your meetings. It takes notes on everything that gets said, transcribes action items, and helps get rid of that feeling. You don't have to worry about whether you're going to miss something because Granolay has you covered. [15:49] And that lets you stay present in meetings. I've been using Granola for a long time, almost since they came out, and it's amazing for this. It doesn't join the meeting like some of those other clunky meeting note takers. The UI is really fast and well considered, and it feels like it's sort of just transcribing all the important moments in my work life. And that gives me the confidence to get great work done.
[16:19] and how you can do better. It's really a power tool for anyone who cares about their meetings and also cares about how they show up in those meetings. It also has these things called recipes, which are pre-made prompts for common tasks like negotiating, coaching, or summarizing. I even have a recipe that I made that's in Granola that you should check out. Once you try it on one meeting, it's really, really hard to go back. The notes are always better than what you could do manually, and it helps me be much more present instead of frantically typing all the time. Head to [16:49] Okay, that makes total sense. Now I want to relate this to LLMs for a second, because you can imagine that there's an LLM that's trained to predict [17:05] where I end up after a long day of podcasts. [17:08] Um, [17:09] And you can imagine it probably would also end up predicting that I would end up on a couch. What are the differences in the ways that it makes those predictions? [17:17] that make energy-based models better for this scenario. [17:23] Okay, that's a good thought exercise. So, [17:28] Okay, now you are LLM. So, okay, let's talk about back to EBM because what we described is very natural about EBMs. EBMs are all about constructing energy landscapes and how we navigate those energy landscapes. And energy landscapes is sort of the maps of your states based on the data we observe. So in your case, we're just going to look at you in all possible scenarios. All of these possible scenarios are going to be mapped into energy landscape, highest point, less probable
[17:58] More probable. Very probable. I end up on the couch. Yeah, yeah, yeah. [18:06] There might be some other additional little points. Like sometimes you might go to gym. [18:13] So it's going to be, you know, lowest points compared to everything else, but some of them are going to be lower. Yeah. Yeah. So that's the situation. So this is how energy-based model actually we think. It just takes the data and map it directly to this energy landscape. And then we use certain algorithms to navigate this, but there are different kinds of energy-based models today. So I'm going to... [18:39] talk about it a little bit later but the whole idea is just hey let's map it [18:44] into the structure and navigate the structure. [18:47] And as you see, as we like map into this, there are no tokens. We don't predict any tokens and so on. So that's already a crucial difference. How would LLM think? [18:59] LLM. [19:00] Yes, it's going to rely on the training data and there's going to be a lot of training data, like a lot of observations of how you behave and. [19:10] to figure out where you would end up [19:13] it's going to be attached to [19:16] probabilities of your next token. [19:20] if that makes sense. And those tokens gonna come from words. And what usually bothers me about LLMs [19:27] It's intelligence, which is language dependent, like our brains, we are.
[19:33] intelligent, I'm relatively intelligent. So like, I speak different languages and none of my thoughts, processes really depend on any language. Like I could just think in an abstract way, and then I speak different languages and decode the information and the channels. And with the LLMs is like, if you're searching for the next token in certain words, like, [19:56] intelligent [19:57] process, I would say the information processes in French are going to be different from [20:03] what's in English just because like words naturally gonna be end up next to each other. So see what I'm saying? It's like and then we have so many languages in the entire world and you have so many LLMs trained on different languages so you're gonna end up [20:18] reasoning [20:19] you're going to end up having reasoning processes different for each of the language, which feels really wrong. So in this case, [20:27] observing you walking around the house, [20:30] has nothing to do with language then. [20:33] It's a pure visual spatial reasoning task, just looking at your body navigating the space-time. [20:40] and geometry of your house. [20:43] So we need to map that information in the language space, find the right words and embeddings, [20:50] and then we start [20:52] associating those tokens with the probabilities based on what the data we see from you. So we're trying to map something absolutely has nothing to do with language into language space,
[21:03] and think about it in that space, which feels really wrong. And [21:10] I don't know, I just realizing that [21:13] For many people, [21:15] It's counterintuitive just because LMS is the first form of AI we sort of know, and it's the most popular form of AI today. [21:25] For many people, it's by default like, oh yeah, we're just going to use language to navigate the world, to drive a car. But, and I'm like, every time I'm speaking, I'm like, well, let's wake up. Let's like actually see when you drive a car, when you walk around your house, how much language you actually use. Are you trying to predict next word as you navigate yourself around the house? Probably not. You just use your visual data, your state of the body, and you know, you just move your body, right? Without speaking. [21:54] There's a lot here. I'm really into this conversation. So I want to start with [21:59] A, it seems absolutely right to me that... [22:04] there are many different ways in which we [22:07] Um, [22:09] process information or many different ways in which intelligence can occur and only a few of them are verbal. [22:15] but there's [22:18] There's certain things that come up for me [22:22] when I think of this. One is... [22:25] Language models happen to work with languages as their primary [22:31] way of working, but really they just work with sequences of tokens that have weak correlations, many thousands of weak correlations between each token that helps us to know which comes next. So even though it might be unintuitive to model my behavior inside of my apartment with like specifically with language, although I think there is some interesting things there that might be related to language, we could model it as just like a sequence of movements, right?
[23:01] where one movement is weakly correlated to the next one that we sort of [23:07] have a trajectory of movements that tell us where where i'm going why is that not [23:13] a good way to model things. [23:15] It's a good way to model things and you don't need LLM for it. You need, [23:20] a form of AI which is not attached to language, but [23:25] it can be compatible with language if you want it to. And that's what [23:28] our model is about. [23:30] Right. I guess what I'm saying is forgetting about the language part of it, just like modeling my movements as this string of... [23:41] uh correlated events like an event stream where each token is like one next thing i do [23:46] Yeah, you can do it and people do it today, right? People even do image recognition using language models. [23:52] You could be really creative, but it's like, that's what makes it expensive and super slow, because you're trying to play a guessing game what my next token could be. And this is what makes it extremely expensive. So... [24:04] Like you could do it, but you don't have to do it. You just can use different architecture, which is more suitable for non-language related tasks, such as spatial reasoning or applied engineering is another example of spatial reasoning. Like when you build a bridge, you don't go to literature department. You go to engineering school and learn formal methods, right? So here we are trying to use literature department everywhere. And I'm like, hey, we don't have to. There are EBMs.
[24:34] and you don't have to do everything through language. [24:39] It's a matter of like, it's right. It's like energy based minimization principle when it comes to your resources. If you have infinite money, and you don't care about the timescale show you can do everything you can attach it to language, you can attach it to I don't know your cat movement around the house and [24:56] connected to the cat movement and you know where cat goes and your next token goes and we decide where you're gonna go you can be really creative but [25:06] if you want to minimize your resources and [25:10] you don't have... [25:12] Opportunity to wait. [25:14] Like for example, if your AI controls the circuits, you probably cannot wait even a second. It's all milliseconds, microseconds. So it's just this form of AI is not suitable for those tasks. So basically, if I'm understanding this right, if I'm spending tons and tons of tokens... [25:32] And I'm looking for a more efficient, more direct way to... [25:37] predict some of these solutions to these problems. An energy-based model is going to get me there faster than modeling it with tokens. Is it also able to do with less training data? [25:50] Um, yes, actually the beauty of... [25:53] of the EBMs is it's really good at working with sparse data because like you know there's evolutions of like traditional EBMs which were applied for the LLMs then there was diffusion models and diffusion models came from the fact that sometimes you don't have enough data to train the models or your data is just data set is incomplete so
[26:13] There are ways to reconstruct those energy landscapes by injecting certain noise and changing the navigation strategies. [26:22] So that's what the diffusion models were about. And the EBRM with latent variables is just like, hey, on top of the diffusion stuff, we also... [26:31] understand the data. We're not just taking any data, but we also understand why the data looks the way they are. So that understanding goes to the latent variables, just like latent space in your brain sort of understands the world around you and keeping you on top of your tasks and allows you to like predict and plan. So it was the same idea here. So now we got to the latent variable part of it. So I would love when you use the word [27:01] that must mean something very specific to you can you help me understand that and how it relates to latent variables and what those are [27:07] Yeah, so that's also back to your question was that like how LLMs are different from the those kind of EBMs we're creating. LLMs don't understand the data. It's just you feed a lot of data into it and it's sort of like, hey, [27:22] I got it. Like, okay, I know what's the most probable scenario here and here we are. [27:27] And [27:27] However, here, [27:29] IBM. [27:30] you can feed a lot of data. It's not just going to look at like, hey, I see the biggest pattern here. It's going to try to understand the pattern and that understanding that knowledge is going to go to latent variables. [27:43] So what is understanding about data? Like it's just basic knowledge about the world, basic rules about the world. Like if there is a couch behind Dan,
[27:53] it's probably because he likes to sit in it or because he likes it on the background so [27:59] There are little rules you can guess. [28:01] about [28:03] you being as a data point and you got to be in data point. And [28:08] Then you can try to create those kind of rules for everything, right? For you navigating your apartment, there are little rules like, you know, there's a kitchen for cooking. There's, I don't know, bathroom. There's sofa. There's your bed. [28:23] So that. [28:24] that understanding [28:26] allows you to have your own mental [28:30] world model, [28:31] for your brain. [28:34] which helps you to understand your environment and if something changes in your environment you understand the rules like if somebody brings you a different couch different shape you're still gonna know what to do with it so that's [28:47] An example of how you can infer what to do with something new based on what you already know. [28:54] So with people, it kind of comes natural because of the evolution and so on. But with AI, we need to teach it. So we need to like mimic that evolution. And what latent variables allow you to have here is like, hey, let's look at the data, but let's also try to understand the data. Let's look at. [29:13] you know if you deal with numerical analysis we're going to look at all possible correlation functions and the model is going to be creative it's going to try to figure out what's the total [29:22] state of the energy and minimize and figure out the laws about your data.
[29:27] But there are so many creative ways how you can infer those roles. [29:32] What is... [29:33] Is a latent variable equivalent to a rule in this scenario? Like if there's a couch in my apartment, I sit in it. [29:40] It's not equivalent to a role, but it's equivalent to a role. [29:44] to something which holds the knowledge about the rules of your data. [29:50] Thank you. [29:51] It's like a knowledge storage. [29:54] So it has many rules in it. [29:57] Yeah, you could have many rules. You could have so many rules about the data. So one latent variable has many different rules. [30:02] Yeah. [30:02] It's just like a knowledge data set. [30:06] essentially. [30:07] about your data. [30:08] Is it an explicit data set? [30:11] As in, does it have key value pairs of rules or is it a- It's in the form of energy landscape. It's just another energy landscape you're going to navigate. So essentially, we take the data. [30:24] We look at the data, [30:26] we construct some sort of [30:29] structure for AI to deal with the data so it can start learning the rules about the data. And once it understands the rules, it stores its knowledge in the latent variables in the form of energy landscape. And then we navigate that energy landscape later. [30:44] Interesting. And like, could it, for example... [30:49] explicitly write out for me, theoretically, explicitly write out for me, here are all the rules that I know. [30:55] or [30:56] Uh...
[30:57] Is it [30:59] Thank you. [31:00] It stores all of them in this energy landscape. But yeah, we can access that. We can access that. And that's what makes it. [31:08] That's what like EBM potentially makes it powerful for data analysis because data analysis is all about searching for patterns and rules about your data. So, [31:19] And it's something... [31:20] where language is not going to be helpful to you. If you try to attach the rules about your data, and those data is like numbers and some relationships and functions to like American English and words in American English, and then you try to search for the next word, it kind of like you're losing a lot of information. So in this case, you're [31:39] You have an opportunity to just directly work with the data and understand the data. [31:43] I think one of the things I'm trying to understand is when I hear... [31:49] rules about the world and how things relate to each other, I think of symbolic AI. [31:55] And [31:57] I'm wondering, and obviously... [32:00] And those approaches ended up being pretty brittle and requiring too much compute and stuff like that. Um, [32:08] And I'm wondering how an energy landscape that acts as a... [32:14] that stores a bunch of rules about the world doesn't fall into the same problems. [32:20] Well, because I guess we avoid tokenization in this case, we just map it directly into different data structure. So see, EBMs are naturally non-autoregressive, like there are no sequences of tokens and that's what makes it fundamentally different. So essentially...
[32:38] I don't know if it helps. There could be another analogy, like you're trying to navigate... [32:43] uh, the maze and you are LLM. [32:47] person so you'll have a little embrace um well maybe maze is not a good example like imagine you're trying to navigate i don't know the map of san francisco [32:57] So, and you have a left brain. So you're like, okay, I'm in Mission Bay. Let me turn to Embarcadera. So you cannot... [33:06] you cannot choose [33:08] So essentially you were just forced to choose one direction at a time. So you like, [33:15] choose to walk in Barcadera and you're just gonna keep walking and walking and [33:21] You can... [33:22] If you want to turn, you just need to choose one direction at a time. And imagine you like trying to get to the Bay Bridge. [33:30] from like, I don't know, King Street. Like, you know, it's typically 20 minutes walk, but depending how you walk. [33:37] So to navigate there, [33:40] you're sort of allowed to choose one direction of the time. You don't see any other options. You like have tunnel vision and you just, [33:48] Kind of keep walking, walking, one decision at a time. And sometimes you take the wrong turns just because you hallucinate, you know, some words just naturally next to each other and it doesn't allow you to turn right when you want to turn you left. And then you just keep wandering and wandering until you try to reach the Bay Bridge. And the roads you take in might never take you there. Like there might be a hole in the road and you're just going to fall, but you...
[34:15] And you might see this hole, but you cannot... [34:18] turn back because you're out of regressive LLM. You have to go into that home and that's like, sometimes you run out. So this is the reason why sometimes we prompt it and it doesn't give you an answer. Just because it's searching and searching and searching, it's spending more and more compute and it doesn't have a bird vision. It just doesn't have ability to turn as it performs the tasks. It doesn't know what's right and what's wrong anymore. It just like randomly chooses one [34:48] time and keep walking until you try to read it so you might never reach that destination. [34:53] And that's why you need a lot of training. So how is it different from the EBM? EBM gonna have the bird view all the time. [35:00] And [35:01] you allowed to take different routes so if you see there's a hole [35:05] You're going to [35:06] choose a different route. It may not look like it, but Dan Shipper is currently hard at work testing the latest Kodak and Opus models. Working looks pretty different in this new world. [35:22] We call this hammock mode. [35:26] *sad music* [35:29] Oop, hammock mode's over. Looks like Dan has to jump in. [35:33] *whistling* [35:35] Hammock Mode, an idea by Every. Every, the only subscription you need to stay at the edge of AI. [35:45] That's really interesting. It basically
[35:48] I've been doing a lot of [35:50] coding with language models recently to sort of test the limits of vibe coding. [35:56] And [35:57] One of the things that I find with... [36:00] or have found with big production apps. [36:03] is in particular if you have vibe coded something [36:09] you, over the course of vibe coding it, [36:13] you may have slightly changed exactly what is this project even supposed to be about? [36:20] And what is the... [36:22] What are the problems that I'm trying to solve with it? And [36:27] If you then go look at the code base... [36:31] It feels like [36:33] all of the code is locally correct, but it [36:36] forms this sort of like patchwork of like hot fixes and solutions where if you [36:41] zoomed out, you'd be like, actually, there's a much simpler... We should just throw all this out. And there's a much simpler way to think about how to do all this stuff. But it has a trouble... [36:53] It has trouble when it's presented with a lot of context, [36:56] then zooming down into... [36:59] okay, I need to create a unified solution here that is not a patchwork of different things, but like carries one concept throughout the entire system. [37:08] and it ends up being distracted a lot by... [37:12] whatever it's looking at at the current moment. Is that the sort of problem that you think this type of system can help with?
[37:20] Mm-hmm. [37:21] There's actually a lot of problems in what you're describing. So... [37:27] Yeah, so... [37:28] Solving the problems with ripe coding is one of our use case. [37:32] We dreaming about generating formally verified code and automate [37:38] the coding entirely. So moving you from Vype coding in one specific language to coding in natural language. So you can call the natural English, for example, and no more C++ or Python needs to be involved in there. So that's an idea. And with the coding is like, [37:54] At the state it is today, [37:56] Yes, we prompt LLMs. [37:59] and it gives us something back, but it's still on you as an engineer to figure out what's right and what's wrong. [38:06] So, [38:07] There's going to be set of rules LLM can try to help you. And even if it has external verifier, which just going to check whether your old logic in your GitHub space is sort of [38:21] compatible, compliant to what you're trying to create. And if the new logic is compatible with your old logic. So this thing's... [38:30] External verifiers can check. They could just say, hey, we know the old logic, we know the new logic, [38:37] We're going to see how it's merged together. We're going to write mathematical proof, making sure that, you know, this logic is compatible with what you already have and provide you a certificate [38:47] It's all like you don't have to review any of it. It's machine verifiable. It's all happening on compiling level. So all it's going to say is going to send you a message, a natural language like, hey, look,
[38:58] This part of your code is not compatible by logic. [39:02] This is potentially how you fix it. And this is the things we cannot fix for you. So we're moving you from vibe coding to vibe code specifications, those rules and information about your code is called [39:17] code specification. So, [39:20] Once you... [39:22] understand [39:24] like this is the first problem right we're trying to solve it's just logic and [39:28] being compatible with what you already have. The second problem is, [39:33] Is this code actually doing what you want it to be doing? And this is what AI cannot solve for you. Because AI cannot look in your brain and know what you want. [39:44] example would be like imagine you're coding, web coding autopilot. So you have specifications from the hardware perspective, you have specifications from your logic perspective, like, hey, make it, and there's also instructions, right, how the car is supposed to behave. So there's behavior, [40:03] parameters for your code. So. [40:06] Code being able to be compiled is one problem. The second problem is, is this code doing what you want it to be doing? So, [40:16] For example, how fast it is on the hardware and so on. And if the answer is yes, another set of questions is like, okay, [40:24] Is it gonna hit the pedestrian by chance? [40:27] Is it actually going to navigate the map of, I don't know, San Francisco?
[40:32] And the answer is, I don't know, right? So in here, you need to write a bunch of tests and test your entire system you created. Like, oh, is it overall behaves the way it was meant to be? [40:46] End. [40:47] So this is another form of specifications, right? And [40:53] Essentially, the behavior part [40:55] Sometimes we can guess it. Like if we have a lot of data, we could have another LLM or EBM proposing you like, okay, people who try to do the autopilot of this kind, this is what they're looking at. [41:06] But you might be doing something absolutely new and we just don't have data about it. So it's going to be on you to tell the behavior. And this is where the big... [41:17] the big thing starts for me personally. [41:21] If you have LLM as a form of AI driving something important where people trust their lives like a car or plane or similar, [41:31] LLM can misbehave based because you cannot constrain it. It just hallucinates. And EBM can be constrained. You can come up with a set of constraints and EBM just forced to follow it. So it's on you as a human. [41:47] to make sure [41:49] you know what you want for AI to be doing. And then from our end, from the technical point, we make sure AI always obeys the rules by given by human. [42:00] So, [42:02] and it can go really far right we're talking about the cars and planes but
[42:06] look back to the language. Sometimes model can say something super sensitive to [42:12] mental [42:13] person like struggling with depression and it can go really wrong so [42:19] Even the language can be dangerous. [42:21] So... [42:23] Here we like [42:25] what would I also like feel like we're solving [42:29] is this problem of AI, just sometimes we don't know how it's going to behave at different environments. But we do know how EBM will behave, like at least architecture is designed to be constrained. And there are ways formally to force those constraints. [42:48] to be compliant. [42:50] So it seems like you have a really promising architecture and a model you built or several models you built. [42:56] and [42:58] it's very different from the predominant paradigm right now where companies are pouring like hundreds and hundreds of billions of dollars into building data centers and training new LLMs and all that kind of stuff. What do you think about the... [43:09] current state of the industry and [43:13] investment in LLM versus other models. Opinions about that. Yeah, tell us. [43:20] It's an ecosystem, right? Silicon Valley, especially, it's an ecosystem. And there are lots of... [43:26] micro versions of those ecosystems around the world. So, [43:31] LLM's historically the first form of AI which gave us a hot effect, like 2021, 2023, when they just started appearing, people were like, oh my god, this is the new future. It's amazing.
[43:48] So this is why like... [43:51] people start believing that okay if it's really good at talking to me eventually it's gonna be good at [43:57] doing data analysis, my taxes and other stuff. So, [44:02] All the investment communities start pouring money into LLMs. [44:06] And there were a lot of money to be put in that back then. [44:11] And right now people see that, okay, we grow the compute system. [44:17] we're trying to change the architecture a little bit and it's sort of reaching out plateau [44:23] And there's so much money already put in there. Like, what do you do with this? [44:29] um it's like billions of dollars literally you can just like forget it and like okay you know let's dismiss it let's pour money into something new nobody thinks this way and we don't have probably enough money in this entire economy to like just make decisions like that billions dollars there billions are there for the ai specifically um [44:49] So this is why... [44:51] it's so hard just for investment community just like [44:55] Take the... [44:55] step understanding like okay this is not working maybe i invest into something radically new and i'm not saying people don't do it like people do it just [45:06] percentage wise, it's a lot smaller. What people feel comfortable is [45:12] to take [45:13] something LLM based, which is changed a little bit. So it has a little bit of elements of novelty, but it's also LLM based. So they can still use the portfolio companies and so on. So they pour money into that.
[45:29] And I understand because like, [45:32] If I were an investor, I would just... [45:35] always looked at what variables would give me risks and how can I reuse what I already have. So it's naturally for you to keep investing into LLMs like architecture, just because you already invested a lot in the past. You already committed to this and maybe start investing a little bit into something new. [45:56] And there's a lot of big tech companies who are a part of this ecosystem, right? So there's a lot of circular deals happening, like those companies who create the LLMs, [46:07] They create a system for companies who create in data centers and those who create in data centers, they have dependencies with the hardware industry. So it becomes like a one giant thing, which is impossible to break. And when we came. [46:25] with alternative architecture, we're like, okay, let's not just try to put it as something out there, radically different, which you have to abandon LLM for. We are very much compatible with LLMs. Like you could put LLM on top of us. ABM is compatible with Transformers. Transformers can, you know, work with any LLMs. [46:45] We can be that layer. We're still all your LLM [46:50] investments valued you want to make them cheaper everyone wants you can outsource the task to us related to spatial reasoning like if somebody comes to big tech llm and say hey can you try to do my taxes llm not gonna solve this but if it's attached to ebm we could take care of that and you can take care of anything language related so we could actually
[47:12] Try experiments to reduce the cost for your LLM portfolio companies and be a part of the ecosystem which is already out there while we're creating a new ecosystem on the side for alternative forms of AI. [47:25] Hm. [47:25] I think that's really smart. It's a great strategy. I'm really curious about something you said a little earlier that progress is plateauing. [47:36] In LLMs. That's, that's news to me. Like, I feel like every month or two, I'm testing a new model where I'm like, holy shit, this is actually way better. And it does feel like if you look at the top model companies, if you're, you know, talking, talking to OpenAI or Anthropic or Google there, they feel like there's a lot of more room in the LLM paradigm. [47:55] What do you think I'm missing or the big model companies are missing? [48:00] um personally you know when i'm saying plateauing it doesn't mean it's like reaching out flat it's like you incrementally better and better [48:07] But is there going to be another phase transition, like another breakthrough? [48:11] I don't anticipate that just because we already reached so much complexity of those networks using billions parameters, so much compute, so much... [48:22] of frameworks like creatively paralleling this [48:26] reasoning processes and it still doesn't phase transition you. [48:33] So the reason why I figured out [48:36] it's not going to work in the long term for some tasks like applied engineering is when I just start speaking to different companies in that space. Like we speak into.
[48:49] like digital assets companies like banks trading firms where a lot of data analysis is needed also drug discoveries essentially just people who look in at a bunch of data not just [49:03] patients talking like language set of data but also like the blood markers the genes and so on um so a lot of this is data analysis which is still done by people today um [49:17] They're also like... [49:20] decision-making pipelines. Like sometimes you just need to distribute the energy on your energy grid and you need to know how much energy to pump in your system. So what it means is you need to analyze the data in the short term, in the long term, construct a prediction how much data [49:37] I mean, how much power you actually need to put into your system next, in the next millisecond or second or an hour. And all of this is still done by people or a combination of people in some programs which are controlled by people. [49:52] So LLMs are relatively new and AI is like, you know, not relatively new. It's been like few years for us and [50:01] all of this mission critical industry is still not automated by AI. And even like, [50:07] I'm just asking like, oh, how much of your data analysis LLM is doing today? And the answer is zero. And I'm like, why? What's the issue? And the issue is the big tech LLMs, they're mainly like B2C. So it works for you, for your coding and for your personal needs sometimes. But for businesses, they don't want to share their data with them. They don't want to share data in that big brain for all. They want to have...
[50:35] privacy and they want to have their own custom AI, like custom version of AI specifically designed for their tasks. [50:44] And this is what LLMs cannot do for you in the form we have it today. [50:50] So there's no B2B model. There are B2B model for like cogenerational tools, right? Do you have an enterprise package for the cogen for, I don't know, businesses, but... [51:02] It's still done by people. Even coding is still done by people. [51:06] So it's like... [51:08] It's interesting to see that there's still a huge gap, especially in applied engineering data analysis. Anything which requires a layer of verification, like LLMs are not there. [51:19] I totally agree with you that there are definitely still a lot of gaps in LLMs. I'm curious... [51:26] Given this and given what you're seeing in the customers you work with, the companies you work with, do you think the big model companies are sensitive to this? Are they working on energy-based models? Are you working with them? If they're not going to get to the next paradigm, do you suspect that they'll start to adopt stuff like this? [51:43] I do know that some big tech LM models, I mean, the companies have EBM models in house. [51:49] Thank you. [51:50] So, which is a positive signal for us, right? So, you know, the leaders who were there before we came, they started with LLMs and now if they started building the EBMs, after we started building the EBM, it's a positive signal, right?
[52:07] Fascinating. [52:09] Eve, this is an incredible conversation. I feel like I learned a lot. Thank you so much for coming on the show. [52:13] Appreciate you. Thank you, Dan. Of course. If people are interested in following you or following your company and maybe using some of your products, where can they find you? [52:23] I'm mostly on X. [52:26] Yeah, we have Logical Intelligence account and my personal account on X. I'm still learning to be more active on social media. [52:37] We also have LinkedIn page, so we're trying to update it. [52:41] Cool. Awesome. Well, thanks for joining. [52:44] Thank you so much, Dan. [52:45] Bye. [52:53] Oh my gosh, folks. You absolutely, positively have to smash that like button and subscribe to AI&I. Why? Because this show is the epitome of awesomeness. It's like finding a treasure chest in your backyard. But instead of gold, it's filled with pure, unadulterated knowledge bombs about chat GPT. [53:16] on the edge of your seat, craving for more. It's not just a show, it's a journey into the future, with Dan Shipper as the captain of the spaceship. So do yourself a favor, hit like, smash subscribe, and strap in for the ride of your life. [53:30] And now, without any further ado, let me just say, Dan, I'm absolutely hopelessly in love with you.
Want to learn more?
Ask about this episode